OptionalamountAmount to be charged to the payer, expressed in major units.
Optionalcheckout_Merchant-defined reference for the checkout. Use it to correlate the SumUp checkout with your own order, cart, subscription, or payment attempt in your systems.
OptionalcurrencyOptionalcustomer_Merchant-scoped identifier of the customer associated with the checkout. Use it when storing payment instruments or reusing saved customer context for recurring and returning-payer flows.
OptionaldateDate and time of the creation of the payment checkout. Response format expressed according to ISO8601 code.
OptionaldescriptionShort merchant-defined description shown in SumUp tools and reporting. Use it to make the checkout easier to recognize in dashboards, support workflows, and reconciliation.
Optional ReadonlyidUnique SumUp identifier of the checkout resource.
OptionalmandateOptionalmerchant_Merchant account that receives the payment.
Optionalreturn_Optional backend callback URL used by SumUp to notify your platform about processing updates for the checkout.
OptionalstatusCurrent high-level state of the checkout. PENDING means the checkout exists but is not yet completed, PAID means a payment succeeded, FAILED means the latest processing attempt failed, and EXPIRED means the checkout can no longer be processed.
OptionaltransactionsPayment attempts and resulting transaction records linked to this checkout. Use the Transactions endpoints when you need the authoritative payment result and event history.
Optionalvalid_Optional expiration timestamp. The checkout must be processed before this moment, otherwise it becomes unusable. If omitted, the checkout does not have an explicit expiry time.
Checkout
Core checkout resource returned by the Checkouts API. A checkout is created before payment processing and then updated as payment attempts, redirects, and resulting transactions are attached to it.