Langsung ke konten utama
POST
/
v3
/
orders
/
{id}
/
payment
Create a payment for an order
curl --request POST \
  --url https://api.scalev.com/v3/orders/{id}/payment \
  --header 'Authorization: Bearer <token>'
{
  "pg_payment_info": {},
  "public_order_url": "https://demo.scalev.shop/o/order-secret",
  "payment_url": "https://demo.scalev.shop/o/order-secret/success",
  "payment_method": "bank_transfer",
  "sub_payment_method": null
}

Otorisasi

​
Authorization
string
header
wajib

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Parameter Path

​
id
string
wajib

Canonical UUIDv7 order primary key. For migrated orders, legacy numeric core_order.id values remain accepted for compatibility.

Respons

Payment created successfully

​
pg_payment_info
object

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_url
string<uri> | null

Buyer-facing public order status URL.

​
payment_url
string<uri> | null

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

​
payment_method
string
Contoh:

"bank_transfer"

​
sub_payment_method
string | null

Provider channel such as a virtual-account bank code when applicable.