Mastercard processing
Payment operations teams manage Mastercard processing volume through a unified orchestration platform that routes transactions to regulated acquirer partners. Merchants gain granular control over MDES tokenisation, Identity Check authentications and transaction retries to optimise approval rates.
- Category
- Methods
- Capabilities
- 10
- Available on
- All plans
Cardflo provides robust Mastercard processing capabilities for high-risk and enterprise merchants. Our platform ensures efficient transaction handling, from authorisation to settlement, across diverse business models.
We focus on optimising approval rates and maintaining compliance with Mastercard's network requirements.
Cardflo’s extended acquiring network ensures faster transaction speeds and better success rates for Mastercard payments, regardless of origin. Our multi-acquirer routing capabilities, with dynamic failover support, improve authorisation rates and enhance the customer experience.
Mastercard processing overview
Mastercard processing remains a fundamental requirement for merchants operating in both high-risk and enterprise sectors. In the current payments landscape, this involves more than simply accepting a card number; it requires a deep technical integration with the Mastercard Network Exchange to manage complex authorisation flows.
Transactions must be categorised correctly using appropriate Merchant Category Codes to ensure compliance with specific scheme rules. For businesses operating internationally, the processing stack must handle Cross-Border transactions while managing currency conversion and regional interchange caps.
The mechanics of a Mastercard transaction involve several stages, including the initial request at the gateway, the routing to the acquirer, and the final communication with the issuer via the Mastercard network. Ensuring that these steps are handled with low latency is critical for maintaining transaction success rates.
Advanced configurations, such as the use of network tokens, help to reduce friction while adhering to the security standards set by the Payment Card Industry Data Security Standard.
How mastercard processing works
Authorisation and data validation
When a customer initiates a transaction, the gateway captures the card data and transmits an authorisation request to the acquirer. This request includes the Merchant Identification Number and relevant transaction details. The acquirer forwards this to Mastercard, which then communicates with the issuer to verify funds and assess the risk of the transaction.
SCA and 3DS verification
For transactions falling under the scope of PSD2 or other regional regulations, Strong Customer Authentication is triggered. Using 3D Secure protocols, the merchant confirms the cardholder's identity. Mastercard’s specific 3DS requirements ensure that liability shift is correctly applied, protecting the merchant from certain types of fraudulent chargeback claims.
Clearing and financial settlement
Daily transaction batches are sent to the network for clearing. Mastercard calculates the net settlement amount, subtracting interchange fees and scheme fees. These funds are then moved from the issuing bank to the merchant’s acquiring account, typically within a fixed window such as T+2 or T+3 business days.
Dispute and chargeback lifecycle
If a transaction is disputed, the merchant receives a notification through the acquirer. The process involves multiple stages, including the initial retrieval request and the formal chargeback. Merchants must provide compelling evidence, such as proof of delivery or signed contracts, to proceed with representment and attempt to recover the funds.
Why mastercard processing matters
Authorisation Rate Optimisation
Mastercard maintains one of the largest global issuer networks. Processing efficacy is often tied to how data is formatted in the authorisation request. By correctly identifying transactions as Merchant Initiated Transactions or Customer Initiated Transactions, merchants can minimise soft declines. This technical precision ensures that domestic and international Mastercard payments are processed with the lowest possible refusal rates, directly impacting the net revenue of the business.
Risk Mitigation and Compliance
Compliance with Mastercard network rules is non-negotiable for high-risk merchants. This involves monitoring chargeback ratios to remain below the thresholds of programmes like the Global Merchant Risk Management Program. Proper transaction tagging, including the use of correct flags for recurring billing or one-click checkouts, ensures that the merchant remains in good standing with the acquirer while reducing the likelihood of heavy scheme fines.
Mastercard processing use cases
MDES credential lifecycle handling
Merchants using MDES network tokens must manage token status changes, cryptogram requirements and replacement credentials when Mastercard cards expire or are reissued. Cardflo supports token-aware gateway orchestration and passes lifecycle updates through configured integrations, helping payment operators retain valid credentials while avoiding retries against obsolete account details.
Cross-border Mastercard retail volumes
Payment operators applying Mastercard Identity Check must distinguish frictionless authentication, issuer challenges, exemptions and soft declines within PSD2 SCA flows. Cardflo configures 3DS2 decision rules and routes authentication outcomes to compatible acquirer partners, enabling merchants to retry with the required challenge data and preserve accurate liability records.
Mastercard flows for regulated gaming
Merchants retrying declined Mastercard transactions must interpret issuer response codes and avoid repeated attempts that breach scheme retry requirements or attract additional fees. Cardflo applies response-specific retry controls, suppresses non-retryable declines and routes permitted follow-up attempts with consistent transaction references through the acquirer partner network.
Mastercard scheme fee analysis
Finance teams handling substantial Mastercard volume need to identify fee drivers across transaction types, authentication outcomes, authorisation behaviour and clearing records. Cardflo consolidates gateway and acquirer partner reporting, analyses Mastercard cost categories and supports routing or message-quality adjustments intended to reduce avoidable scheme fees without obscuring settlement reconciliation.
Mastercard processing by the numbers
Typical industry performance for Mastercard gateways ranges between 1.5 and 2.5 seconds, depending on the number of hops between the merchant and the issuer.
Under current EU regulations, Mastercard interchange for consumer debit is typically capped at 0.20%, while consumer credit is capped at 0.30%.
Mastercard generally considers a chargeback-to-transaction ratio above 1% as a breach of standard policy, though high-risk programmes may have different monitoring levels.
Methodology: these figures are illustrative ranges drawn from published industry data and observed merchant cohorts, not guarantees. Actual results depend on your risk profile, card mix, geography and acquiring setup, and are confirmed only in your own pricing and approval terms.
Related terms
Talk to our team about a live rollout across our acquirer partners' rails.
What you get with Mastercard processing
- Integration with Tier 1 acquirers specialising in Mastercard network infrastructure and protocol requirements.
- Global capability for Mastercard transaction routing across European, North American, and Asian markets.
- Support for 3D Secure version 2.2 to facilitate PSD2 compliance and liability shift.
- Dynamic descriptor support to improve merchant recognition and reduce accidental friendly fraud incidents.
- Automated Account Updater services to keep stored Mastercard credentials current for recurring billing.
- Full support for Mastercard Identity Check to enhance security during the checkout process.
- Detailed reconciliation reports categorising interchange fees and scheme fees for transparent financial auditing.
- Real-time monitoring of chargeback-to-sales ratios to ensure compliance with Mastercard scheme thresholds.
- Processing of credit, debit, and prepaid Mastercard products through a single technical interface.
- Access to network tokenisation to replace sensitive primary account numbers and improve security.
A short scoping call, then a written plan for your MIDs.
Questions about Mastercard processing
How are Mastercard MDES token lifecycle events handled for recurring transactions?
Cardflo can receive and apply MDES lifecycle events so recurring payment references remain aligned with the token status held by Mastercard. Suspended, resumed or deleted tokens can be reflected in subsequent transaction handling, while token-related events remain visible for operational review.
Merchants should retain the original credential-on-file context and recurring indicators required by their acquirer partner.
Which Mastercard Identity Check data should operators monitor by issuer?
Operators should analyse authentication outcomes, issuer response codes, directory server results and the relationship between Identity Check completion and subsequent authorisation. Reporting can segment these fields by issuer BIN, market, device channel and transaction type to identify inconsistent outcomes.
Cardflo preserves relevant authentication references in the authorisation flow and helps merchants investigate data-quality or configuration issues with acquirer partners.
How can Mastercard retry activity be controlled to limit scheme fees?
Cardflo can enforce Mastercard-specific retry policies using the original response, transaction history and credential-on-file context. Rules can suppress repeated attempts that conflict with scheme requirements, apply waiting periods where appropriate and preserve links between the original transaction and later submissions.
Reporting gives operators a view of retry counts, outcomes and fee-related indicators, supporting policy changes without treating every unsuccessful authorisation identically.
Does Mastercard processing support Level 2 and Level 3 data?
Yes, for B2B transactions involving corporate or purchasing cards, Mastercard allows the submission of additional data fields. Level 2 data includes tax amounts and customer codes, while Level 3 data includes detailed line-item information such as product descriptions and quantities.
Submitting this extra information can often lead to a lower interchange rate, as the issuer views these transactions as having a lower risk profile compared to standard retail transactions.
How are Mastercard scheme fees different from interchange fees?
Interchange fees are paid by the acquirer to the issuer and are generally the largest component of transaction costs. Scheme fees are paid directly to Mastercard for the use of their network and brand services.
While interchange is often regulated in regions like the EU, scheme fees are set by Mastercard and can vary based on volume, transaction type, and whether the transaction is domestic or cross-border.
Both are typically passed through to the merchant under an Interchange Plus pricing model.
How do I handle recurring Mastercard payments for customers with expired cards?
The Mastercard Automatic Billing Updater is a service that allows merchants to receive updated card information when an expiry date changes or a card is replaced. By integrating this service, the merchant's vault is updated automatically before the next billing cycle.
This reduces the number of declines caused by outdated card information, ensuring that subscription services remain active without requiring the cardholder to manually update their details in the checkout centre.
Related features.
Related guides.
See how Cardflo compares.
Ready to improve your payments setup?
Tell us about your business. We'll match you with the right acquiring partners and the right route, typically inside a week.