POST
/payment/zibapay/card/: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: XMLHttpRequestRequest Parameters
| Field | Type | Required | Description |
|---|---|---|---|
reference | string | Required | transactionReferenceId from the collect response, or the order reference. |
Response fields
| Field | Type | Presence | Description |
|---|---|---|---|
status | string | Always returned | Payment status: COMPLETED, PENDING, or FAILED. |
reference | string | Always returned | Order reference identifier. |
transactionId | string | Always returned | TransactPay transaction identifier. |
amount | number | Always returned | Amount charged. |
currency | string | Always returned | Currency charged. |
redirectUrl | string | Optional | Provider return URL when the checkout flow supplies one. 3-D Secure is not confirmed. |
message | string | Optional | Gateway status or confirmation message. |
Status codes
| HTTP Status | Meaning |
|---|---|
| 200 | Card payment processed. |
| 401 | No merchant session. |
Notes
- HTTP 200 returns the provider payment confirmation payload. Illustrative example.