Create an authenticated customer checkout order

Optional cit_ write capability from checkout-intent capture. A valid matching token completes the intent when the order commits. Invalid, expired, mismatched or consumed tokens never block order creation.

Customer checkout payment method code selected by the buyer. Required for normal checkout. May be omitted when the store uses strict two-step Payment Link checkout; Scalev resolves it to payment_link. Virtual Accounts use flat method codes such as va_bca.

Present only when this accepted order owns the frozen server form-submission selections under server_v1, including explicit empty selections. A runtime that received the matching public capability may omit its direct Meta, TikTok and SnackVideo server form sends. Absence requires the compatible direct path. This acknowledges delivery ownership, not provider acceptance or attribution, and does not change browser or Purchase delivery.

Canonical UUIDv7 order primary key returned by the partitioned orders table.

Deprecated for checkout navigation. Retained for compatibility and scoped to the payment step. Always use redirect_url to navigate the buyer after checkout; do not use this field to infer the destination.

Canonical destination the buyer opens after checkout. Always prefer this field over the deprecated payment_url. The server resolves the destination from the payment method and After Checkout setting, including the payment page, order page, WhatsApp, another page, or a custom URL. When a destination cannot be resolved because the configuration is missing or unsupported, or a required phone number, page, or URL is unavailable, it falls back to Scalev's hosted payment instructions page (Halaman Instruksi Pembayaran) at /o/{secret_slug}/success, not the Thank You Page. This fallback requires a valid order identity and host. Storefront checkout records the normalized request Origin header, never body-supplied metadata.origin. Hosted order and Scalev PayLink URLs use HTTPS on that host only while it is a verified custom domain of the same business, connected to Scalev hosting. Otherwise links use the store's configured default domain if verified and owned by the same business, then the business's default Scalev domain if no eligible store domain exists. A CORS allowlist entry alone is insufficient. The same validation applies when generating later order responses and follow-up chat or WABA links. External provider URLs and configured custom destinations retain their existing behavior. Retained attribution parameters are forwarded onto a configured page or custom URL only while it stays on the currently validated checkout host or a Scalev-owned one. Null only when required order identity or host data is unavailable.

Buyer-facing payment status. A settled payment is exposed as paid; this field never returns settled.

Canonical post-payment destination exposed only after a buyer-paid outcome (internal payment status paid or settled) when a valid redirect snapshot exists. Omitted before payment and when Scalev's hosted success flow applies.

Other Income label. For payment_link, the winning concrete Payment Request's frozen Store label is reconciled after payment.

E-payment provider. xendit is the current/managed Xendit provider; xendit_legacy is the owned legacy Xendit provider. Other possible values include duitku, midtrans, durianpay, and singapay.