Curated market guide
Japan PSP routes to verify first
Which PSPs, convenience-store payment routes, wallets, cards, and BNPL options should a merchant ask first for Japan?
Japanese PSP / gateway shortlist
Use when you need cards, konbini, bank transfer, PayPay, carrier billing, or localized checkout in Japan.
Treat local-entity access as a verification item. Ask each provider whether your current merchant entity can onboard, whether a local company or local bank account is required, and which settlement currencies are supported.
- Confirm whether your merchant entity can onboard directly or whether a local entity, local bank account, licensed partner, or sponsor merchant is required.
- Confirm KYB documents, beneficial-owner checks, website/app review requirements, prohibited categories, reserve policy, and production support path.
- Confirm supported payment methods, refund/dispute handling, reconciliation fields, FX treatment, payout currency, and settlement timing before integration.
Card and platform route
Use when Japanese card acquiring, enterprise processing, platform payments, or developer-led card acceptance is central.
Treat local-entity access as a verification item. Ask each provider whether your current merchant entity can onboard, whether a local company or local bank account is required, and which settlement currencies are supported.
- Confirm whether your merchant entity can onboard directly or whether a local entity, local bank account, licensed partner, or sponsor merchant is required.
- Confirm KYB documents, beneficial-owner checks, website/app review requirements, prohibited categories, reserve policy, and production support path.
- Confirm supported payment methods, refund/dispute handling, reconciliation fields, FX treatment, payout currency, and settlement timing before integration.
Wallet, konbini, and BNPL route
Use when wallet checkout, convenience-store payment, or BNPL is expected by local shoppers.
Treat local-entity access as a verification item. Ask each provider whether your current merchant entity can onboard, whether a local company or local bank account is required, and which settlement currencies are supported.
- Confirm whether your merchant entity can onboard directly or whether a local entity, local bank account, licensed partner, or sponsor merchant is required.
- Confirm KYB documents, beneficial-owner checks, website/app review requirements, prohibited categories, reserve policy, and production support path.
- Confirm supported payment methods, refund/dispute handling, reconciliation fields, FX treatment, payout currency, and settlement timing before integration.
Documents to prepare
- Company registration certificate and operating entity details.
- Beneficial-owner, director, and signatory identity documents.
- Business website/app URLs, product description, refund policy, terms of service, and restricted-category explanation where relevant.
- Bank account, settlement currency, tax/VAT/GST information, and expected processing volume.
Questions to ask
- Can my current merchant entity onboard, or is a local company or bank account required?
- Which local payment methods are live for my business category and customer flow?
- What documents are required for KYB, technical review, and production approval?
- How are refunds, chargebacks, reconciliation files, reserves, FX, and payout currencies handled?
- Which public email, form, dashboard, or partner manager should be used for merchant onboarding?
If the official contact route is unclear
If public sources do not confirm eligibility for your entity, ask LocalPayMap to help verify Japan PSP contact routes, onboarding requirements, and method coverage before you commit engineering work.
- Which local payment methods are live for my business category and customer flow?
- What documents are required for KYB, technical review, and production approval?
- How are refunds, chargebacks, reconciliation files, reserves, FX, and payout currencies handled?
- Which public email, form, dashboard, or partner manager should be used for merchant onboarding?
Route comparisons
How local customers usually pay
Japan has cards, convenience-store payments, bank transfers, PayPay, Rakuten Pay, LINE Pay-like wallets and carrier billing in some digital categories. Customers often value trusted local brands and clear payment instructions. A foreign merchant can usually start with cards through a global PSP, but full local conversion may require konbini, PayPay or bank-transfer support through a Japan-capable provider. Refunds can differ sharply by method, so do not design one refund process for all payments. Ask providers about Japanese-language checkout, local receipts, recurring billing, chargebacks, settlement currency and whether a Japanese entity is required for local methods.
- Cards with Apple Pay and Google Pay where supported. Confirm customer experience, failed-payment handling, refund path and settlement impact before launch.
- Convenience-store payment and bank transfer for customers avoiding cards. Confirm customer experience, failed-payment handling, refund path and settlement impact before launch.
- PayPay, Rakuten Pay or other wallets for local consumer conversion. Confirm customer experience, failed-payment handling, refund path and settlement impact before launch.
Payment methods to check first
For Japan, begin with the methods that match real customer behavior, then map each one to a provider that can actually onboard your merchant. Current public records point to Digital wallet, General commerce, Card acquiring and Buy now, pay later, but availability can vary by PSP, entity type and industry.
- Start with the payment method customers already recognize, not the provider with the longest logo wall.
- Check whether the method supports online checkout, payment links, QR, app redirects, refunds and clear transaction references.
- Keep one fallback method for buyers who cannot or will not use cards.
- Document which method is mandatory for launch and which can wait for phase two.
What to do if you do not have a local company
Do not assume a foreign company can use the same route as a local merchant in Japan. Some PSPs can onboard overseas entities, some require a local company and local bank account, and some support only selected industries. The cleanest first email states your incorporation country, product, website, expected volume, average order value, customer location, settlement currency and refund model.
- Ask whether foreign entities are accepted directly or only through a local subsidiary, distributor or merchant-of-record arrangement.
- Confirm local company, tax ID, local bank account, local director, licence and proof-of-address requirements.
- Ask which settlement currencies and payout countries are supported for your entity.
- Get the onboarding answer in writing before promising a local method to customers.
PSP and four-party provider screening
Use provider discovery to separate customer-facing payment brands from the companies that can legally process and settle funds. Public PSP/contact leads for Japan currently include local PSPs, banks, gateways and aggregators. Compare them by eligibility, method coverage, operational support and documentation quality rather than headline pricing alone.
- Ask regional PSPs and local banks which Japan methods are live for your merchant category.
- Request links to official onboarding, developer documentation, support and pricing pages.
- Do not rely on marketplace claims unless the provider confirms your entity and industry in writing.
Settlement, currency, refunds and disputes
Treat all pricing and settlement information for Japan as preliminary until confirmed by the official provider or contract. Fees, payout timing, rolling reserves, FX, chargeback costs and refund rules can change by industry, volume, risk review, settlement currency and integration route.
- Ask for transaction fee, fixed fee, refund fee, chargeback fee, payout fee, FX spread, reserve policy and minimum monthly or setup charges.
- Confirm payout timing, settlement currency, settlement account country, failed-payout handling and reconciliation file fields.
- Check whether refunds must return through the original method and whether partial refunds are supported.
- For cards, confirm dispute workflow, evidence deadlines, chargeback fees and fraud-monitoring rules.
Compliance and operating checks
Before launch in Japan, prepare KYB and risk material as if the provider will ask for it. Most delays for new merchants come from unclear ownership, unsupported industries, missing licences, incomplete websites, weak refund policies or settlement accounts that do not match the merchant record.
- Prepare company registration, ownership, director ID, website/app URL, product description, terms, privacy policy and refund policy.
- Disclose regulated products, digital content, subscriptions, marketplace activity, high-risk categories and cross-border fulfilment.
- Ask how the provider screens sanctions, fraud, AML risk, chargebacks and customer complaints.
- Keep sensitive or restricted markets at compliance-review level; do not use unofficial workarounds.
Questions to ask service providers
Send a concise written checklist to every Japan PSP or aggregator so responses can be compared side by side. The goal is to expose hidden entity, settlement, support and technical gaps before engineering work begins.
- Which payment methods are live today for my exact merchant entity, industry and customer geography?
- Do you support hosted checkout, API, plugin, payment links, webhooks, sandbox, refunds and reconciliation exports?
- Who is the merchant of record, who handles chargebacks and who owns customer support for failed payments?
- What documents are requested, how is approval reviewed, and what would cause rejection?
- Can you provide official links for pricing, settlement terms, developer docs and support escalation?
Common beginner mistakes
The most common mistake in Japan is treating payment acceptance as a logo checklist. Local conversion depends on customer habit, provider eligibility, settlement flow, refund support and operational reliability. A cheaper-looking route can become expensive if it cannot settle where you need, cannot refund cleanly or cannot support the methods buyers expect.
- Choosing cards only when wallets, mobile money, bank transfer, QR or cash-style routes are normal for local buyers.
- Building against an API before KYB, entity and settlement eligibility are confirmed.
- Ignoring refund and dispute flows until the first customer complaint arrives.
- Comparing providers without asking the same written questions of each one.
Questions merchants ask
Which payment methods should a new merchant check first in Japan?
Start with Digital wallet, General commerce, Card acquiring and Buy now, pay later. Then confirm which provider can support your entity, industry, customer geography, settlement currency and refund model.
Can a foreign merchant accept local payments in Japan without a local company?
Sometimes, but it must be verified provider by provider. Ask whether a local entity, local bank account, tax ID, licence, local director or merchant-of-record route is required.
Which PSPs or aggregators are worth screening for Japan?
Public leads include local PSPs, banks, gateways and aggregators. Treat them as a shortlist for outreach, not as confirmed eligibility or complete market coverage.
Can I use public fee pages as a final quote?
No. Public fees are screening context only. Final pricing can vary by country, industry, volume, risk review, settlement currency, FX, reserves and contract terms.
What operational questions should I ask before integration?
Ask about onboarding documents, restricted industries, live payment methods, checkout flow, webhooks, sandbox, refunds, disputes, chargebacks, reconciliation files, settlement timing and support escalation.
What should I do if the provider has no public sales email?
Use the official contact form, support page or developer contact route, and send a short brief with your entity country, product, volume, currencies and required payment methods.