← Back to the directory

Payment channel profile

Mastercard

Card network · China

ChinaPrimary marketMain service market
Card networkRole / typeOther
Medium, verify entity and documentsEntity requirementOnboarding conditions
T+1SettlementPayout timing

Overview

Mastercard is listed as other 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 Mastercard 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

Mastercard in the payment stack

Mastercard is a card-network lens for merchants comparing acceptance routes, but the practical decision depends on acquirer or PSP onboarding, authorization quality, fraud tools, chargeback operations, settlement reporting, tokenization, and local cardholder behavior. It should be evaluated alongside domestic schemes, wallets, and bank payments.

Connection route

Merchants typically access Mastercard through an acquirer, bank merchant-services route, PSP, payment facilitator, gateway, platform, terminal provider, or wallet-tokenized checkout. Confirm whether the provider is acquiring directly, reselling an acquiring route, or only supplying a gateway layer over another processor.

Verification questions

  • Which markets, currencies, channels, card types, recurring needs, and merchant categories require Mastercard acceptance?
  • Is the route direct acquiring, PSP aggregation, payment facilitation, platform-managed, wallet-tokenized, or gateway-only?
  • Who handles authorization, 3DS, tokenization, fraud controls, chargebacks, refunds, settlement, and reconciliation?
  • What entity, bank account, documentation, risk review, reserve, and compliance steps must be verified?
  • How will Mastercard reporting align with local payment methods, subscriptions, tax, and order management?

Merchant caveats

  • Mastercard acceptance does not define the acquiring model or settlement responsibilities.
  • Coverage can vary by market, merchant category, card type, and provider configuration.
  • Chargeback handling, tokenization, recurring support, and reporting should be checked directly.
  • Provider examples are discovery examples only, not recommendations or support evidence.

Provider examples to verify

AdiqBraspag (Cielo)AFSKNETPayFastTelr

Related markets

BrazilChinaFranceUnited KingdomUnited States

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 modelprovider quote required
Pricing basisprovider quote required
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

No public field in this group is complete enough to treat as confirmed. Use it as a due-diligence prompt.

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.
  • PCI scope: 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.

Visit the official website