Create an HTML Mode public order
Page-scoped public endpoint for HTML Mode Scalev.checkout.createOrder. This route accepts HTML Mode order payloads with customer, destination, items, and shipping_option, requires X-Scalev-Page-Api-Key, and does not accept storefront public API keys. The page and store are resolved from the path and page API key; any page_unique_id or store_unique_id values supplied in the JSON body are ignored.
Header
Publishable page public API key for the page_unique_id path page. Storefront public API keys are not accepted on page-scoped public routes.
Parameter Path
Public page unique ID.
"page_540f48019f525f41"
Body
HTML Mode public order payload. Use customer, destination, and one combined items list for checkout details. Pass the chosen option returned by shippingOptions as shipping_option. The API ignores any supplied page_unique_id or store_unique_id and uses the path page plus the authenticated page API key instead.
Buyer contact details submitted by an HTML Mode page.
Buyer destination submitted by an HTML Mode page.
1Public order payment method code.
"bank_transfer"
"BCA"
Runtime-generated form reCAPTCHA token.
Respons
Flat HTML Mode public order object.
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.

