Create a payment for an order
Changed onRequires the order:update scope. Create a payment request / intent for an order. The response body is the payment gateway payload (pg_payment_info); order-level URLs and status live on the order responses.
Request
- Base URLhttps://api.scalev.com
- URLhttps://api.scalev.com/v3/orders/{id}/payment
- Auth
- HTTP bearer
- or API key in header authorization
Response
Payment created successfully
The payment gateway payload for the order, returned as the response body itself — the same object the order responses expose as pg_payment_info. Manual methods such as bank_transfer and cod 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_gateway, payment_url, deeplink_url, qr_string, qr_image_url, va_number, and va_name. Order-level fields (public_order_url, payment_url, redirect_url, payment_method) are not part of this body; read them from the order responses.
Changes
- warning
removed the optional property
from the response with the status - warning
removed the optional property
from the response with the status - warning
removed the optional property
from the response with the status - warning
removed the optional property
from the response with the status
- warning
- warning
removed the optional property
from the response with the status
- warning