FinWiki
日EN中

PSP merchant settlement risk

Confidence: Likely Updated 2026-05-21 Review by 2026-11-21 Sources 4 Machine-translated Original (JA)
#payments#PSP#acquiring#settlement-risk#merchant-risk
On this page

Overview

Merchant PSP risk is the risk that sits between checkout success and final money movement: merchant onboarding, card-number handling, fraud monitoring, chargebacks, reserves, settlement timing, refunds, and platform or wallet failures. In Japan, the analysis must combine METI’s card-number handling / merchant-contracting route, FSA funds-transfer registration, prepaid value rules, and payment-brand / network contracts.

Read this page with Japan card acquiring stack, funds-transfer registry, and code-payment competitive map. Company pages such as GMO-PG, SBPS, DGFT, and Netstars links here when merchant risk is the real topic.

Risk Stack

LayerRiskTypical control
Merchant onboardingFraudulent merchant, prohibited goods, poor fulfillment, chargeback-prone business modelKYC / KYB, merchant screening, category controls, ongoing monitoring
Card-number handlingCard data leakage, tokenization failure, PCI DSS noncomplianceNon-retention, tokenization, PCI DSS, security audits
Authorization / fraudStolen card, account takeover, mule transactions, friendly fraud3-D Secure, velocity checks, device / behavior monitoring
Settlement timingPSP pays merchant before final network / wallet settlement is certainReserves, delayed settlement, exposure limits, rolling balances
Refund / cancellationRefund spike after merchant failure or event cancellationContractual holdbacks, refund monitoring, merchant concentration controls
Wallet / code-payment routingMultiple brands and funding sources create operational and reconciliation complexityBrand reconciliation, exception handling, SLA monitoring
Funds transferWithdrawable or transferable balances create statutory safeguarding and AML concernsFSA funds-transfer controls, AML/CFT monitoring, safeguarding arrangements

Japan Regulatory Routes

RoutePublic relevance
METI credit-card-number handling contract concluding operatorsDetermines who has merchant-contracting / card-number handling responsibility under the Installment Sales Act.
FSA funds-transfer service providersApplies when PSP / wallet functions include transfer capability beyond pure card processing.
FSA prepaid issuer registryApplies when non-withdrawable stored value is issued for third-party use.
Card networks and PCI DSSOperationally critical even when not the public legal registry.
Cashless Promotion Council publicationsUseful for tracking code-payment use, merchant acceptance trends, and industry standardization work.

Company Lens

Operator typeExamplesMain question
Listed card / PSP infrastructure[[payment-firms/gmo-payment-gatewayGMO-PG]]
Telecom / group PSP[[payment-firms/sb-payment-serviceSBPS]]
Legacy / enterprise PSP[[payment-firms/dg-financial-technologyDGFT]]
QR gateway[[payment-firms/netstarsNetstars]]
Wallet / funds-transfer operator[[payment-firms/paypayPayPay]], [[payment-firms/merpay

Practical Reading Rules

  • Do not infer profitability from transaction volume alone; merchant mix, fraud losses, subsidies, and settlement timing matter.
  • Do not infer risk ownership from brand display alone; the legal acquirer, registered merchant-contracting party, PSP, and wallet can be different entities.
  • Treat high-risk merchant categories, cross-border transactions, subscriptions, digital goods, and event tickets as riskier than low-ticket daily retail.
  • Use credit purchase / card registry for card and merchant-contracting routes, then layer FSA registrations only when value transfer or prepaid value is involved.

Sources