Create an authenticated customer checkout order
Customer-authenticated storefront endpoint. Create an order from direct items, from a customer cart referenced by cart_id, or from direct items while clearing the referenced cart after successful order creation. Carts must belong to the authenticated customer and current store.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Store unique_id.
Body
Customer checkout payment method code selected by the buyer.
"bank_transfer"
Optional direct item source. If supplied, direct items create the order. If cart_id is also supplied, the referenced cart is cleared after successful order creation.
1 - 50 elements- Option 1
- Option 2
Authenticated customer cart ID. Used as the order source when items is omitted. When items is also supplied, the cart is only cleared after successful order creation.
Response
Customer checkout order
Canonical UUIDv7 order primary key returned by the partitioned orders table.
Buyer-facing payment gateway payload. Manual methods such as bank_transfer and cod can return an empty object. Virtual account methods expose provider reference and account details under the provider's payment_method object. QRIS responses expose QR data or a QR image payload. E-wallet, card, and invoice methods may expose provider actions or hosted provider URLs. SingaPay payments use normalized keys such as payment_url, deeplink_url, qr_string, qr_image_url, va_number, and va_name.
"bank_transfer"
E-payment provider. Possible values include xendit, duitku, midtrans, ipaymu, and singapay.

