Skip to main content
KakaoPay is a mobile wallet in South Korea, built into the KakaoTalk messaging app. Customers pay with their KakaoPay account and confirm each payment in the KakaoPay app or on the KakaoPay web page. Payrails processes KakaoPay through Checkout.com. Pick the PSP below for its setup steps and request examples.

​
How a KakaoPay payment works

KakaoPay is a wallet redirect payment method:
  1. The customer selects KakaoPay at checkout.
  2. Payrails returns a redirect URL from the PSP, and the customer goes to KakaoPay.
  3. The customer confirms the payment in the KakaoPay app or on the KakaoPay web page.
  4. The customer returns to your returnInfo URL.
  5. Payrails receives the final result from the PSP and updates the payment.
Each payment is single-use: the customer confirms every payment on its own. Payrails captures KakaoPay payments immediately, so a successful payment is final. To return funds, refund the payment.

​
Supported currencies and countries

KakaoPay supports these presentment currencies through Checkout.com — KRW (South Korean won), HKD (Hong Kong dollar), and SGD (Singapore dollar). KRW has no decimal places, so send KRW amounts such as "10000". KakaoPay is available to customers based in:
RegionsCountries
Asia Pacific🇰🇷 South Korea

​
Integrate KakaoPay

Choose the PSP that processes KakaoPay for you. The guide covers the PSP-side setup, the Payrails configuration and the request fields that PSP requires.

Checkout.com

KakaoPay via Checkout.com

​
Check PSPs

WorkflowCheckout.com
Payrails SDK✔
Payrails API✔
Delayed / Manual Capture✖
Instant Capture✔
Cancel / Void✖
Refund / Reverse✔
Save Instruments✖
Merchant Initiated Transaction (MIT)✖

​
Ways to integrate KakaoPay

  • Payrails SDK: the Web SDK shows KakaoPay when your workflow returns it as a payment option, and redirects the customer to KakaoPay. To control how the redirect opens, listen for the actionRequired event.
  • Payrails API: call lookup payment options, then authorize with kakaoPay as the paymentMethodCode. The PSP guide lists the meta fields that PSP requires.
In both cases, confirm the final result through webhook notifications or the execution status. Don’t treat the customer’s return to your success URL as proof of payment.
Last modified on October 16, 2026