POST
/payment/zibapay/order/verify/:referenceAPIAuthentication:Bearer token
Authorization: Bearer <token>Security requirement: 403 CSRF Protection
Direct server-to-server calls authenticated via Bearer tokens do not require CSRF headers. If you instead invoke mutation endpoints from a web browser using cookie-based sessions, you must include the following header:
X-Requested-With: XMLHttpRequestPath params
| Field | Type | Required | Description |
|---|---|---|---|
reference | string | Required | transactionReferenceId from the collect response, or the order reference. |
Response fields
| Field | Type | Presence | Description |
|---|---|---|---|
verified | boolean | Always returned | True if order payment was successfully verified with TransactPay. |
orderId | string | Always returned | Order reference identifier. |
status | string | Always returned | Verified order status (COMPLETED, FAILED, PENDING). |
amount | number | Always returned | Verified settlement amount. |
Status codes
| HTTP Status | Meaning |
|---|---|
| 200 | Provider verify confirmation. |
| 401 | No merchant session. |
Notes
- HTTP 200 returns the provider verify JSON (response.data). No request body.