Animica Pay docs 2.00% per successful payment

Start here

Animica Pay documentation

What Animica Pay is, what it costs, and the two limitations to read before integrating.

Animica Pay lets a merchant accept ANM — the native coin of the Animica chain — and receive it directly at their own address. No custody, no chargebacks, no monthly fee.

If you have ten minutes, start with the Quickstart. If you are evaluating, read The 2% fee and The splitting limitation first: they are the two things most likely to change your mind, so they are on the front page rather than in an appendix.

What it costs #

Animica Pay charges 2.00% of every successful payment. 98% of the gross is yours, 2% goes to the Animica treasury. Full worked numbers are on The 2% fee.

Two things that are unusual, stated up front #

How a payment flows #

  1. Your server creates a PaymentIntent with a secret API key.
  2. You redirect the customer to the hosted checkout, or open it in the widget modal.
  3. The customer sends one ANM TRANSFER to the payment address with an ANMPAY1 reference in data.
  4. Our indexer matches that transfer by reference plus recipient — never by amount — and counts confirmations against the canonical chain height.
  5. At 12 confirmations with a successful receipt, the intent becomes PAID, the 98%/2% split is booked in a double-entry ledger, and you get a signed webhook.
  6. Your webhook handler marks the order paid. It must be idempotent, because retries are normal.

The pages #

PageWhat it covers
QuickstartAccept your first ANM payment in about ten minutes.
Core conceptsThe 11-state lifecycle, the ANMPAY1 reference, confirmations and reorgs.
The 2% feeThe protocol fee, the rounding rule, and a worked example in exact numbers.
The splitting limitationWhy there is no atomic 98/2 transaction on this chain, and what we do instead.
RefundsA refund is a new transaction, not a reversal — and what follows from that.
API referenceEvery endpoint, its parameters, examples and errors — labelled live or planned.
WebhooksEvent types, the signature scheme, verification in Node and PHP, replay window and retries.
Testing and test modeWhat test mode guarantees, what you can exercise offline, and a pre-launch checklist.
Going liveThe switch to live keys, the operational duties, and the failure modes to design for.
WooCommerce pluginInstall, settings, what the plugin does, refunds and troubleshooting.
SecurityWhat we never store, why keys are hashed, and what must never reach browser code.

Conventions used throughout #