Overview
Visa/Mastercard is listed as card acquiring in the LocalPayMap public directory. Use this page to prepare due-diligence questions; product availability and terms must be verified directly.
This is a market-specific Visa record, not a duplicate of the brand overview and not the only official onboarding or pricing route. The brand page aggregates related countries and PSP contact leads; this page keeps the local payment scenario visible.
Role in the payment stack
Card network
This is a card network or acceptance context, not a merchant onboarding provider by itself. Most merchants accept it through an acquirer, PSP, payment facilitator, or commerce platform.
Merchant usage and connection route
Visa in the payment stack
Visa matters when merchants evaluate card acceptance, but the merchant decision is about the local acquiring route, checkout experience, authorization performance, disputes, tokenization, fraud controls, and costs through providers. Use Visa as a scheme lens, not as proof that a given PSP can onboard a merchant in every market.
Connection route
Merchants usually access Visa through an acquirer, bank merchant-services provider, PSP, payment facilitator, gateway, ecommerce platform, terminal provider, or wallet tokenization route. Confirm who is the merchant of record or acquirer-facing party, who settles, and who manages authorization, refunds, disputes, and reporting.
Verification questions
- Which countries, currencies, card-present or card-not-present channels, and merchant categories require Visa acceptance?
- Is the route through a direct acquirer, PSP, payment facilitator, platform, wallet, or gateway-only integration?
- Who handles authorization, 3DS, tokenization, chargebacks, refunds, fraud tools, settlement, and reporting?
- What entity, bank account, documentation, risk-review, reserve, and scheme-compliance requirements must be confirmed?
- How will Visa transactions reconcile with local payment methods, subscriptions, tax, and customer support systems?
Merchant caveats
- A Visa logo does not identify the acquirer, processor, dispute owner, or settlement terms.
- Scheme acceptance can differ by country, card type, merchant category, and provider setup.
- Pricing, reserves, authorization performance, and disputes must be verified with the provider.
- Provider examples are discovery examples only, not recommendations or support evidence.
Provider examples to verify
Related markets
Keep researching
This explanation separates payment methods, PSPs/aggregators, acquirers/banks, wallets, and networks/schemes. It does not publish coverage, eligibility, pricing, settlement timing, or onboarding guarantees.
Sources
What merchants should confirm
- Whether the product is available to merchants incorporated outside the target country.
- Whether a local entity, local bank account, licence, or local tax registration is required.
- Supported checkout flows, currencies, refunds, disputes, reconciliation fields, and payout options.
- Industry restrictions, reserve policies, onboarding documents, and implementation support.
Merchant eligibility
Merchant eligibility and entity requirements must be confirmed with the provider.
Pricing and settlement
Published pricing is suitable for initial screening only. Actual pricing can vary by country, industry, volume, settlement currency, integration model, and contract terms. Confirm the official pricing page or a provider quote before going live.
Settlement timing, payout currency, foreign exchange, reserves, and withdrawal rules must be confirmed with the provider.
Capability verification checklist
Use this public checklist before you ask for a quote or implementation access. Treat unknown fields as questions to verify, not as unsupported features.
- Confirm who owns onboarding, KYB review, pricing, settlement, refunds, disputes, reconciliation, reserves, and support for the route you will use.
- Open the official pricing, developer, support, or website links where available, then verify the exact production terms with the provider or PSP.
- Do not treat public notes as final approval, final pricing, settlement timing, or a guarantee that your merchant entity can go live.
Official links to open
Commercial terms to confirm
| Pricing model | card acquiring or network priced |
|---|---|
| Pricing basis | official public pricing or terms |
Fields still to confirm
- Fee range: confirm with the provider, acquirer, PSP, or official documentation before launch.
- FX markup: confirm with the provider, acquirer, PSP, or official documentation before launch.
- Chargeback fee: confirm with the provider, acquirer, PSP, or official documentation before launch.
- Payout fee: confirm with the provider, acquirer, PSP, or official documentation before launch.
- Reserve policy: confirm with the provider, acquirer, PSP, or official documentation before launch.
Integration route to confirm
| PCI scope | confirm hosted checkout tokenization or direct card handling |
|---|
Fields still to confirm
- API / checkout route: confirm with the provider, acquirer, PSP, or official documentation before launch.
- SDK languages: confirm with the provider, acquirer, PSP, or official documentation before launch.
- Sandbox: confirm with the provider, acquirer, PSP, or official documentation before launch.
- Webhooks: confirm with the provider, acquirer, PSP, or official documentation before launch.
- Idempotency: confirm with the provider, acquirer, PSP, or official documentation before launch.
- 3-D Secure: confirm with the provider, acquirer, PSP, or official documentation before launch.
Operational features to confirm
No public field in this group is complete enough to treat as confirmed. Use it as a due-diligence prompt.
Fields still to confirm
- Recurring billing: confirm with the provider, acquirer, PSP, or official documentation before launch.
- Marketplace split: confirm with the provider, acquirer, PSP, or official documentation before launch.
- Partial refund: confirm with the provider, acquirer, PSP, or official documentation before launch.
- Preauth / capture: confirm with the provider, acquirer, PSP, or official documentation before launch.
Public pricing signals are for initial screening only. Actual quotes can vary by country, industry, transaction volume, settlement currency, integration route, and contract terms.