POST
/payment/zibapay/order/refund/: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 | Refund status: COMPLETED. |
refundId | string | Always returned | Unique refund transaction reference. |
reference | string | Always returned | Original order reference refunded. |
amount | number | Always returned | Monetary amount refunded. |
reason | string | Always returned | Reason provided for refund. |
refundedAt | string | Always returned | ISO 8601 refund confirmation timestamp. |
Status codes
| HTTP Status | Meaning |
|---|---|
| 200 | Refund executed successfully. |
| 401 | No merchant session. |
| 500 | { message: "Internal server error" }. |
Notes
- HTTP 200 returns the provider refund JSON (response.data).