South Korea
Local payment methods in KRW
Before you start
Authorization
How to sign your requests with the API token.
Create payment
The base order request that this page extends.
This payment method is not enabled for all merchants. Check availability with your manager.
Overview
| Currency | Payment method |
|---|---|
KRW | Local bank and wallet methods |
The payer is redirected to paymentLink and chooses a method on the provider page.
What is different from a regular order
The order is created through the standard POST /v1/orders endpoint. The base fields (amount, currency, successUrl, failUrl, callbackUrl, etc.) are the same as for a regular order; on top of them you pass the customer object with payer details.
| Field | Type | Description |
|---|---|---|
customer | object | Payer details. The required set is listed below |
The externalUserId field is required for this payment method.
Customer fields
| Field | Type | Required | Description |
|---|---|---|---|
phone | string | ✅ Yes | Phone number: 11 digits starting with 0, without country code (e.g. 01012345678) |
email | string | ✅ Yes | Payer email |
firstName | string | ✅ Yes | First name, must match the phone number owner |
lastName | string | ✅ Yes | Last name, must match the phone number owner |
ip | string | ✅ Yes | Payer IP address (real) |
birthday | string | Virtual account | Date of birth, YYYY-MM-DD. Required for virtual account payments only |
Pass the payer's real data. Names and phone numbers are checked against the phone number owner on the provider side; mismatches lead to declined payments.
Request example
{
"purpose": "Payment for order #1234",
"amount": "5000",
"currency": "KRW",
"externalId": "23456789",
"externalUserId": "437568",
"successUrl": "https://example.com/success",
"failUrl": "https://example.com/fail",
"callbackUrl": "https://example.com/webhooks/payments",
"customer": {
"lastName": "Kim",
"firstName": "Minsu",
"email": "minsu.kim@example.com",
"phone": "01012459077",
"ip": "192.168.0.1",
"birthday": "1992-08-15"
}
}Response
The response is a standard order object. The order is created with the CREATED status; redirect the payer to paymentLink to complete the payment.