Korean payments, KakaoTalk and Naver, connected to your product
Serving users in Korea usually takes integrations a global stack does not cover: a Korean payment gateway, KakaoTalk Channel and AlimTalk messages, Kakao or Naver login, and registration in Naver Search Advisor. NQ Solution, a two-person development studio in South Korea, builds these into websites and web apps. This page explains what each involves.
What this page covers
These integrations are selectable items in our estimate tool and are scoped per project. Of our published work, Chungha Interior's KakaoTalk inquiry intake is the case that touches them, so this page describes the work itself, based on each provider's official documentation, rather than presenting a track record. Provider terms change; we re-check them with the provider at the start of each project.
Korean payment gateways (PG)
Korean customers mostly pay with domestic cards and easy-pay wallets such as Kakao Pay, Naver Pay and Toss Pay, usually through a Korean payment gateway (PG) such as Toss Payments, KG Inicis or NicePay. Which payment methods appear depends on the gateway and your contract with it.
The gateway contracts with the business that receives the money, and each gateway sets its own eligibility and document requirements. If you do not have a Korean entity, confirm eligibility with the gateway before any build starts. Stripe can accept South Korean local cards for businesses located in its supported countries, including the US, Japan, Singapore, the UK and several EU countries, with prices in KRW; South Korea itself is not on that list.
Taking Toss Payments as an example, its documentation describes this flow: development starts with test keys, and live keys become available after the payment-service contract. The customer pays in the payment window; on success Toss Payments redirects to your site with a payment key, order ID and amount. Your server checks that the amount matches the order, so a tampered amount cannot go through, then calls the payment confirmation API with your secret key. That confirmation must happen within 10 minutes of the payment request, after which the payment can no longer be confirmed. Webhooks report status changes in real time.
- What we build: the checkout flow, server-side amount check and confirmation, order records, webhook handling, refunds and cancellations, and an admin view of payments.
- What you arrange: the gateway contract and settlement account. Payment fees are charged by the gateway and billed at cost.
KakaoTalk Channel and AlimTalk
A KakaoTalk Channel is your business profile inside KakaoTalk, opened from Kakao's channel admin centre. Customers can add it and chat with you; this site's own consultation channel works that way.
AlimTalk is different: it sends informational messages, such as an order confirmation, payment receipt, booking notice or shipping update, to a customer's phone number through KakaoTalk, even if they have not added your channel. According to Kakao Business, only informational messages are allowed, and only through templates that pass Kakao's review; advertising content is not. Before sending, the channel must be converted to a business channel, its home set to public and customer-service contact details entered. AlimTalk is sent through Kakao's official dealers, whose service scope and per-message prices differ, and only to phone numbers collected lawfully.
- What we build: the events that trigger messages (inquiry received, booking confirmed, order shipped), the dealer API connection, template variables and a fallback such as email where agreed.
- What you arrange: the business channel, the dealer account and the template wording we draft together. Messages are billed at cost.
Kakao and Naver login
Many Korean users would rather sign in with Kakao or Naver than create another password. Kakao Login starts with an app in Kakao Developers: Kakao Login is switched on, a redirect URI is registered for the REST API or JavaScript SDK, and the client secret is used when requesting tokens. Consent items define what the user is asked to share. Kakao's documentation notes that personal-information items such as email, phone number and name require converting the app to a Biz app and passing a business-information review. OpenID Connect can be enabled to issue an ID token alongside the access token, and apps that transfer personal information overseas register that transfer.
Naver Login works on the same OAuth pattern: an application is registered in Naver Developers with the service URL and callback URL, and the profile fields to request are chosen there.
- What we build: the sign-in buttons and callback handling, account linking with existing email accounts, sessions and the consent wording on your side.
- What you arrange: the developer apps under your company's account, so you keep ownership of the keys.
Stripe or a Korean PG?
Teams that already use Stripe ask whether they need a Korean gateway at all. The answer depends on where your business is based and which payment methods your Korean customers expect.
- Stripe
- Accepts South Korean cards for businesses located in its supported countries, with prices in KRW. Korea itself is not a supported business location.
- Korean PG
- Domestic cards plus easy-pay wallets such as Kakao Pay, Naver Pay and Toss Pay; contracts with the business that receives the money.
- Both
- Common when a global product keeps Stripe for overseas customers and adds a Korean gateway for Korean ones.
Identity verification (PASS and mobile carriers)
Some Korean services must confirm who a user is: age-restricted content, certain payments and sign-ups. In Korea this is usually done through mobile-carrier verification, often in the PASS app run by the three carriers, via a licensed identity-verification provider. The user confirms their name, date of birth and phone number, and your service receives a verification result it can store against the account.
We build the verification popup or redirect, the callback that receives the result, and the account logic around it. Users without a Korean mobile number cannot complete carrier verification, so services with overseas users need an alternative path, which we design with you. The provider contract is in your company's name.
Korean address search
Korean addresses come in road-name and lot-number forms with a five-digit postal code, and users expect to search for them rather than type them. Checkout and shipping forms usually use the government Juso address API, which needs an approval key, or Kakao's keyless postcode service (formerly Daum Postcode). We add the search to your forms, store the address in a consistent format and, where overseas staff need it, the English form of the address.
Korean e-tax invoices
Businesses in Korea issue electronic tax invoices that are reported to the National Tax Service, either through Hometax or through a provider's API. We connect your billing or ERP to a provider so invoices are issued from the records you already keep. Which invoices you must issue, and when, is decided with your accountant.
Naver Search Advisor
Naver runs its own crawler and index, so a site that only looks after Google can be thin on Naver. Naver Search Advisor registers sites per host and verifies ownership with a meta tag or an uploaded HTML file. Naver asks that robots.txt allow its crawler and that you submit an XML sitemap and an RSS feed carrying the full text of recent posts; it also accepts IndexNow update notices.
Naver states that crawl requests are handled by priority and can take from a day to several weeks, and that a successful crawl does not guarantee exposure. This site carries Naver's ownership tag, allows Naver's crawler and publishes a sitemap and RSS feed in the same way.
What we handle on the Korean side
Applications to payment gateways, Kakao and Naver are in Korean and often go back and forth. We prepare them with you, fill in the technical details and handle the communication in Korean, and our founder explains each step in English. Your company remains the contracting party; we do not sign on your behalf or give legal or tax advice.
What we need from you
Accounts that hold money, customer data or keys stay in your company's name. We build and connect; you own the contracts.
- Payments
- A contract with a Korean payment gateway and a settlement account, or confirmation that your current provider covers Korean cards
- KakaoTalk
- A KakaoTalk business channel and an account with one of Kakao's official AlimTalk dealers
- Social login
- Kakao Developers and Naver Developers apps registered to your company, plus Biz app review where personal data is requested
- Naver search
- Access to add a verification tag or file to the site, or permission for us to do it
- Identity verification
- A contract with an identity-verification provider, where your service requires it
- Privacy wording
- Your privacy notice and consent text, reviewed by your own advisor
How these integrations are priced
Each integration is a line item in the quote, sized by what it has to do: one payment gateway or several, which events send KakaoTalk messages, which login providers. The estimate tool lists them as options. Quotes are in KRW, VAT (10%) is not included, and payment fees, SMS and KakaoTalk messages are billed at cost.
Related work
Published projects that touch these integrations or the Korean/English setup around them.
- Chungha Interior
A portfolio-centric responsive site with its own admin (CMS) and KakaoTalk inquiry intake.
Completed · 2026 - EMECS
A Korean/English technical website for overseas buyers, with bilingual SEO built on hreflang and structured data.
Completed · 2025 - NQ Solution website
Our own Korean/English site: server-rendered pages, structured data, sitemap, RSS, llms.txt and Naver verification.
Completed · 2024
How an integration project runs
The same six steps run for every project, whether you are in Seoul or overseas. Remote collaboration is the default; visits are agreed separately in advance and are not included by default.
- 01 Brief
Send a written brief through the project request form, or write to us from the contact page. A rough idea is enough to start; reference sites and files help.
- 02 Consultation and scope
We read the brief, ask what we need to know, and agree the features, integrations and timeline. If our schedule is full, we tell you the next possible start date.
- 03 Quote
You receive a formal quote in KRW that lists the deliverables. It is based on features and integrations, not page count.
- 04 Contract and payments
The contract splits payment into a deposit, interim and final payments. The ratio for your project is written into the contract.
- 05 Design and build
We design and build in stages. The quote, contract, schedule and shared documents sit in one client portal (Korean interface), so you can see where the project stands.
- 06 Review and launch
You review the work before launch, then we deploy. Hosting and maintenance after launch are a separate contract, agreed when you need them.
Questions
- Can I accept Korean cards with Stripe?
- Stripe accepts South Korean local cards for businesses located in its supported countries, including the US, Japan, Singapore, the UK and several EU countries, with prices in KRW. South Korea is not a supported business location, so a business based in Korea usually contracts a Korean payment gateway.
- Can my customers pay with Kakao Pay or Naver Pay?
- Usually through your payment gateway. Korean gateways offer easy-pay wallets alongside cards; which wallets appear depends on the gateway and your contract with it.
- Can a foreign company send AlimTalk messages?
- AlimTalk needs a KakaoTalk business channel and an account with one of Kakao's official dealers, and only informational templates approved by Kakao can be sent. Kakao and the dealer decide eligibility, so we confirm it with them before building.
- Do we need a business review to get users' email from Kakao Login?
- Yes. Kakao's documentation lists email, phone number and name as items that require converting the app to a Biz app and passing a business-information review.
- Can foreigners use PASS identity verification?
- Only users with a Korean mobile number in their own name can complete carrier verification. If your service has overseas users, we design an alternative path for them.
- How long does a Toss Payments confirmation have?
- Toss Payments asks merchants to confirm a payment within 10 minutes of the payment request; after that the payment data is lost and it cannot be confirmed. Your server should check the amount before confirming.
- Does registering with Naver Search Advisor guarantee my site appears on Naver?
- No. Naver says a successful crawl does not guarantee exposure. Registration, a sitemap and RSS make the site easier for Naver to find and read.
Tell us which integrations you need
List the payment methods, messages and logins your users expect, and the provider accounts you already have. We will scope the build from there.
Prefer email? Write to dwkim@nqsolution.kr — the founder replies directly.

