Route Library

Country-to-Country Payment Route Maps

Start with the payer country and destination, then identify the route that actually exists: merchant card checkout, PayPal or wallet handoff, a domestic rail explicitly exposed by the merchant, a verified recipient transfer, or closed store balance. Each route map separates the live entry point, funding and profile gates, authentication, currency money trail, payment state, renewals, refunds, and recovery.

Start With the Corridor

Open the Payer → Destination Route

Choose the corridor first. The merchant or recipient decides which doors exist; the payer-side card, account, wallet, bank, or local rail then has to fit that exact door. A method that works domestically but is absent from the live foreign checkout is not available for that payment.

🇯🇵 → 🇺🇸

Japan to United States

Compare Japan-issued cards, J/Secure, PayPal, Wise, JPY/USD conversion, recurring billing, prepaid or virtual cards, gift cards, and verified-recipient routes.

🇯🇵 → 🇬🇧

Japan to United Kingdom

Compare Japan-issued cards, J/Secure, PayPal, Wise, JPY/GBP conversion, recurring billing, UK merchant support, and verified-recipient routes.

🇺🇸 → 🇯🇵

United States to Japan

Compare US-issued cards, J/Secure, PayPal, Wise, USD/JPY conversion, Japanese account-region rules, local-payment access, travel bookings, and verified-recipient routes.

🇮🇳 → 🇺🇸

India to United States

Compare India-issued cards, UPI Global Acceptance, e-mandates, Wise Travel Card, INR/USD conversion, subscriptions, authentication, and verified-recipient routes.

🇧🇷 → 🇺🇸

Brazil to United States

Compare Brazil-issued cards, merchant-integrated Pix collection, PayPal, Wise, BRL/USD conversion, installments, recurring billing, and verified-recipient routes.

🇩🇪 → 🇺🇸

Germany to United States

Compare Germany-issued cards, PayPal, Wise, Klarna, compatible SEPA or EUR transfer flows, EUR/USD conversion, recurring billing, and verified-recipient routes.

🇨🇦 → 🇺🇸

Canada to United States

Compare Canada-issued cards, Interac-supported flows, PayPal, Wise, wallets, CAD/USD conversion, recurring billing, authentication, and verified-recipient routes.

🇦🇺 → 🇺🇸

Australia to United States

Compare Australia-issued cards, PayPal, Wise, wallets, AUD/USD conversion, subscriptions, BPAY or PayID limitations, and verified-recipient routes.

Route Anatomy

One Country Pair Can Contain Several Different Routes

A payment route is the full path from the payer-side product to the merchant or verified recipient and back through the refund or recovery path. The same country pair can contain direct card checkout, PayPal or wallet layers, recurring billing, account-to-account collection, invoices, bank transfers, store balance, and separate refund routes.

Payer Side

Start with the payer country, then name the actual product: card, PayPal account, wallet, bank account, domestic rail, transfer provider, or store balance. Country availability alone does not prove that the foreign merchant exposes that route.

Merchant / Recipient Side

The destination side may be a merchant checkout, subscription billing entity, platform store, invoice, bank recipient, or collection provider. That side decides which entry points, countries, currencies, products, and refund paths exist.

Payment Job

A one-time purchase, subscription signup, renewal, free trial, app-store purchase, gaming balance, travel deposit, invoice, and recipient transfer can use different authorization, funding, payment-state, and recovery rules even for the same country pair.

Route Gates

Read the Gates in Order

A route can fail before authorization, during authentication, at the country or profile gate, after currency conversion, or later at renewal or refund. Reading the gates in order is more useful than switching brands at random.

Factor Why It Matters
Funding / issuer gate A valid method can still fail here because of account or card status, available balance or credit, funding source, controls, merchant category, country, currency, recurring setup, limits, or provider risk checks.
Profile / country gate Billing country, card country, payer account country, postal format, shipping country, platform or store region, and merchant-supported countries can change route eligibility. Correct profile data still does not guarantee authorization.
Authentication gate 3D Secure, OTP, issuer apps, provider logins, device confirmation, or another challenge can authenticate the payer. Record whether the challenge never appeared, failed, expired, or completed; authentication is a separate stage from final approval.
Live merchant / recipient door The live merchant, recipient, or collection flow must explicitly expose the route. A network, wallet, or domestic-rail logo elsewhere does not prove this merchant accepts the exact product, country, funding source, recurring flow, or transaction type.
Money trail Trace the original merchant currency through any DCC or wallet conversion, authorization, posted amount, issuer or provider fees, transfer delivery, and later refund. Different stages can use different rates, dates, and fee rules.
Payment state / recovery After the attempt, match the merchant order with declined, pending, completed, reversed, refunded, returned, or transfer-reconciliation states. Recovery follows the original route: issuer, PayPal, wallet, transfer provider, gift-card platform, or merchant.

Find the Next Door

Choose the Corridor, Then Open the Right Layer

Use Payment Finder to choose the payer country and published corridor. Once inside the route, open the method or issue layer that actually failed: card profile, authentication, billing or country profile, money trail, payment state, renewal, transfer, or refund.