Authorizations
Bearer authentication header of the form Bearer <secret_key>, where <secret_key> is your secret_key.
Path Parameters
ID of the payment.
"payment id, uuid format"
Body
Amount refunded. Allows to send up to 2 decimals for AED and SAR, up to 3 decimals for KWD.
Idempotency key. Used to avoid similar refund requests.
"refund idempotency key"
Reason for the refund.
"Reason for the refund"
Array of objects representing the order items being refunded.
Response
Success. Payment object is returned.
Payment object.
Total payment amount, including tax, shipping and any discounts. Allows to send up to 2 decimals for AED and SAR, up to 3 decimals for KWD.
"100"
ISO 4217 currency code for the payment amount. Currently there are 3 possible currency options - depending on the country where the store is located:
AED- United Arab Emirates DirhamSAR- Saudi RiyalKWD- Kuwaiti Dinar
AED, SAR, KWD "AED"
Customer information
Customer information. registered_since (as a date of the customer's registration in the App), loyalty_level (as a number of successful orders) and wishlist_count (paid amount by a customer previously, e.g. 500) must be sent for Monthly Billing. is_social_networks_connected is also required for Monthly Billing.
Array of objects, should contain information on 5-10 previously placed via any payment method orders in any status, current order excluded.
Unique identifier for the payment (UUID), assigned by Tabby. Save it on your side!
"payment id, uuid format"
Date and time the payment was created, in UTC, and displayed in ISO 8601 datetime format.
Date and time the payment expires, in UTC, and displayed in ISO 8601 datetime format.
Status of the current payment:
CREATEDmeans that the payment is created successfully, but not finished yet;AUTHORIZEDandCLOSEDmark the successfully approved and captured payments accordingly;REJECTEDis returned when a customer is rejected during Tabby Checkout;EXPIREDis used when a customer cancels a payment or when Tabby doesn't receive a successfully paid transaction after timeout.
CREATED, AUTHORIZED, CLOSED, REJECTED, EXPIRED "CLOSED"
Indicates whether this is a test payment (created using the Test API keys or Production API Keys).
"description"
Merchant-defined data about the payment. This field is a key-value map. The example properties provided below.
Extra data (booking info, insurance, flight reservations, ...) as serialized JSON