A payment gateway for South Korea: bank transfers and Kakao Pay

Korea has two pay-in methods, each on its own rail. Pick one per order with paymentMethod: kor_bank for a bank transfer, kakao_pay for Kakao Pay. The field is required in this market, and amounts are whole won; a fractional amount is rejected rather than rounded.

Bank transfer

The order returns an account number, the bank and the account holder. The buyer opens their own bank app and sends the amount to that account.

Kakao Pay

Kakao Pay is a Korean mobile wallet. A kakao_pay order returns the receiving Kakao Pay QR, which the buyer scans in Kakao Pay. When the QR holds a kakaopay.com link, the buyer can also open Kakao Pay straight from a button on their phone.

Neither rail carries a transaction reference, so a Korean pay-in confirms without one. The method pages explain each rail, including how a deposit is matched: Korean bank transfer and Kakao Pay. For the pay-in flow across all markets, see pay-ins.

South Korea is the second market, after India, where the hosted pay page works. It covers both Korean methods on orders served by the ATLAS network.

• Payment link: create the pay-in with a checkout object and send the buyer to checkout.url. One page handles kor_bank and kakao_pay and adapts to the method.
• Embedded checkout: the same page inside your checkout. Mount checkout.embedUrl with Atlas.mount, and the window opens only on the domains you allow.
• H2H API: show the account details or the Kakao Pay QR in your own interface, then wait for pay_in.completed or poll GET /api/merchant/pay-in/{payInId}/status. There is no reference to collect. Request and response samples are on the Korean bank transfer and Kakao Pay pages.

The pay page speaks Korean or English. Send locale: "ko" and it opens in Korean, with the amount written the way Korean buyers expect, such as ₩128,000.

A bank transfer order shows the account number, the bank and the account holder under the bank transfer details, each with a copy button, and a line asking the buyer to send exactly that amount in one transfer. A Kakao Pay order shows the QR, which the buyer can save to the phone. On a phone, the hosted page tries to open Kakao Pay as soon as it loads; if the browser blocks that, the Open Kakao Pay button is the first thing on the card.

The buyer is never asked for a reference. They tap "I have paid" when they're done. While a countdown runs, the page checks the status on its own, switches to success once the payment is confirmed and sends the buyer back to your returnUrl. A buyer who leaves early doesn't stop the order from completing.