Agent-readable docs index: /llms.txt. Full docs in one file: /llms-full.txt. Download /docs.zip to grep all markdown files locally.

Transaction references, duplicates and safe retries

Every request that moves money takes a reference you create: tranx_id for bills, transfers and KYC, and invoice_id for collections. The reference is how you prevent double charges and how you look the transaction up later.

Rules

  • Unique per transaction. At least 10 characters for tranx_id, 5 to 50 for invoice_id. A reused tranx_id is rejected with duplicate transaction detected.... and nothing is charged.
  • Store it before you call. Save the reference in your database first, then call the API. If your process crashes mid-request, you still know what to verify.
  • Make it readable. A prefix, a date and a counter works well, for example ACME-20261121-000185.
References are scoped to your business, so two businesses can use the same value without conflict.

Retry safely

Network timeouts and HTTP 401 / 5xx responses do not mean the money did not move. Never fire a second purchase with a new reference until you know the first one failed.
send request (tranx_id = A) │ ├──> 200 success ─────────────────────────────────> done │ ├──> 417 failed and reversed ─────────────────────> retry with a new tranx_id │ └──> timeout / 401 / 5xx / queued ──> verify A ──┬──> successful ──> done ├──> pending ─────> verify later └──> failed ──────> new tranx_id
ProductVerify endpointReference
BillsGET /bills/verify_transactiontranx_id
TransfersGET /payment/verify_transfertranx_id
CollectionsGET /payment/verify_transactioninvoice_id
CryptoGET /crypto/get_transaction_by_idtransaction ID
Send crypto has no reference field. If a crypto withdrawal times out, list your crypto transactions before trying again.