Skip to main content
POST
Create v2

Authorizations

Authorization
string
header
required

JWT issued by POST /api/v1.1/access-token/b2b. Send Authorization: Bearer <token>.

X-PARTNER-ID
string
header
required

Merchant API key (Credential.api_key). Required on every request.

Body

application/json
account_id
string
required

Account identifier in ULID format (provided in request body, not path).

Example:

"01K946KF851RK7FX075GJHBVKF"

amount
number
required

Payment amount. Minimum and maximum limits depend on merchant configuration and selected e-wallet vendor.

Example:

100000

ewallet_vendor
string
required

E-wallet vendor code. Must be an active vendor in the e-wallet payment group.

Example:

"EWALLET_DANA"

expired_at
string<date-time> | null

Optional expiration datetime. When provided, must be later than the current time.

Example:

"2026-04-02T23:59:59+07:00"

customer_name
string | null

Customer name for the checkout.

Example:

"John Doe"

customer_email
string<email> | null

Customer email for the checkout.

Example:

"john.doe@example.com"

customer_phone
string | null

Customer phone number. Required for some vendors (for example OVO push-to-pay).

Example:

"081234567890"

merchant_redirect_url
string<uri> | null

Optional URL to redirect the customer after payment flow completion.

Example:

"https://merchant.example.com/payment/return"

merchant_reff_no
string | null

Optional merchant reference number for this transaction.

Example:

"INV-2026-001"

Response

Success

V2 API response envelope for e-wallet native create-order (ApiResponseTrait).

response_code
string
required

Application response code (for example SP000 for success).

Example:

"SP000"

response_message
string
required

Human-readable response message.

Example:

"Successfully"

data
object | null

E-wallet transaction resource payload on success.