Payments
A Payment represents a single charge, refund, or balance
movement attached to an Order — the record of money owed,
taken, returned, or moved between credit buckets for a given
purchase.
Payments don't live in isolation: they're always created,
listed, charged and refunded against an Order. The
operations that produce + manage payments are documented in
the Orders section, alongside the rest of
the order lifecycle. This page is the canonical reference for
the Payment object's shape — what fields you'll see on a
payment.complete webhook, on a list-order-payments response,
or on the per-order detail view.
The most-used flow is createOrderPayment (record an intent
to pay) → actionChargeOrderPayment (capture the money) →
payment.complete webhook (delivery-side confirmation). See
Build a basket and check out
for the end-to-end walkthrough.
The Payment object
Attributes
The ID of the item to be added.
The amount of the payment, in the lowest denomination
At what point the payment amount will be captured
currencyrequiredThe currency code for the amount
How the payment method will be provided
If present, provides a human-readable explanation for the failure.
The time and date that the payment was paid.
The payment processor to be used for the payment
A dictionary of processor-specific data
The amount of the payment that may be refunded.
The current status of the payment
Possible values:cancelledexpiredfailedpaidpayment_method_chargedpayment_method_storedpendingready_for_capturerequires_actioncreated_atrequiredThe time and date that the payment was created.