v2

latestOpenAPI 3.0.3Proprietary2026-07-263483431.1 MB

Orders

Create a payment for an order

Requires the order:update scope. Create a payment request / intent for an order.

post/v3/orders/{id}/payment

Response

Payment created successfully

pg_payment_infoobject

Payment gateway payload. Manual methods such as bank_transfer and cod can return an empty object while the public order contains the buyer-facing instructions to render. 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. Storefronts should render their own payment page from these fields and use payment_url only as a hosted fallback. SingaPay payments use normalized keys such as payment_url, deeplink_url, qr_string, qr_image_url, va_number, and va_name.

public_order_urlstring uri nullable

Buyer-facing public order status URL.

payment_urlstring uri nullable

Buyer-facing payment or instruction URL. Redirect or open this URL for hosted payment methods.

payment_methodstring

Example response

{
  "payment_method": "bank_transfer"
}