POST

Get Payment Status

Retrieves the current status and full details of a payment by its UUID. The same value is also pushed to your callbackUri whenever the state changes — polling this endpoint is a fallback / reconciliation tool. See the Lifecycle States section below for the full set of values and what each one means.

https://axiron.io/v2/payments/status

Authenticate every request

Include your Bearer token and HMAC-SHA256 signature. Authentication guide →

Body parameters#

Required only

merchantIdstringrequired

Your merchant ID. The request will return 400 if omitted — the status lookup is always scoped to the merchant that owns the payment.

Example MERCHANT_ID

paymentIdstring (uuid)required

The payment UUID returned in the create payment response

Example 477374d1-e7f5-4ab7-b3b1-e86

Payment lifecycle#

Read the state field to determine the payment outcome. The same states are delivered through callbacks.

pending

Initial state. The payment was created and the customer can now transfer funds to the displayed CBU / scan the QR. The payment stays here until funds arrive, the 60-minute window expires, or it is canceled.

expired

The 60-minute payment window elapsed without a matching transfer being received. The link is no longer payable — create a new payment if the customer still wants to pay. No funds were credited.

canceled

Canceled before completion (typically by an operator or by automated anti-fraud rules). No funds were credited. Treat the order as not paid.

dispute

Funds arrived but a mismatch (wrong amount, sender mismatch, anti-fraud flag, refund request) is being reviewed. The state will eventually transition to completed or canceled — do not release the order / credits until then.

completedTerminal

Terminal success state. Funds were received, matched, and credited to your merchant balance. It is safe to release the order / credits to the customer. The callback fires exactly once on this transition.

Need help with your integration?Contact the team