calculate-loan

01 Loan payments

Card Payment Network Mandates Explained

Guide 01-18672 · Updated · Step by step

Card payment network mandates are rules and technical requirements set by payment networks for participants such as issuing banks, acquiring banks, processors, and merchants. They govern how card transactions are accepted, routed, secured, and reported; the exact requirements depend on the network, transaction type, location, and participant’s role.

What a network mandate means

A payment network—often called a card scheme—connects institutions that issue cards with institutions that provide merchants access to card payments. It publishes operating rules, technical specifications, and deadlines. A mandate is a required change or obligation within that framework, rather than an optional recommendation.

For example, a network may require a particular data field in authorization messages, a new method for authenticating online payments, or changes to how a transaction is identified. The network may set the rule, but a merchant usually receives the practical instructions through its acquiring bank, payment processor, or gateway.

“Card payment network” can refer to networks operating credit, debit, or prepaid transactions. Requirements are not necessarily identical across networks, and a rule can apply only to certain countries, card products, channels, or transaction categories.

Who must comply

Responsibility is distributed across the payment chain. The network specifies its rules, but each participant has its own implementation duties. A merchant may not communicate directly with a network at all, yet still have to change checkout software or staff procedures because its processor needs the merchant’s systems to send required information.

  • Issuers provide cards and authorize or decline transactions. They may need to update card credentials, authentication, or authorization systems.
  • Acquirers and processors connect merchants to networks and handle transaction messages. They commonly translate network requirements into implementation instructions and deadlines for merchants.
  • Gateways and payment facilitators provide technology or services that route transactions and may need to update integrations, message formats, or account processes.
  • Merchants may need to update terminals, online checkout, stored-payment arrangements, receipts, or operating practices, depending on the mandate and their provider’s instructions.

The contract and operating relationship matter: a merchant should not assume that a processor’s technical update removes every merchant responsibility, nor assume that every network rule applies directly to every merchant.

What mandates can cover

Mandates commonly concern the information and procedures needed to complete a payment reliably and securely. Examples include:

  • Message and data requirements: adding or changing transaction fields, account indicators, or other information used in authorization, clearing, or dispute handling.
  • Card security: requirements related to chip transactions, contactless acceptance, authentication, or handling sensitive payment data. Network rules complement, but are not the same as, broader security standards.
  • Online and stored-card payments: changes affecting recurring transactions, credential-on-file transactions, or authentication flows.
  • Acceptance and routing: rules affecting supported transaction types, device capabilities, or how payment transactions are identified and passed through the system.
  • Operational processes: updates to dispute, refund, reporting, or settlement procedures.

These are examples of subject areas, not a universal list of current obligations. The details and timelines are published and updated by each network and communicated through participating providers.

How a mandate reaches a merchant

Implementation usually involves several stages. A network announces or publishes a requirement; an acquirer, processor, or technology provider assesses its impact; and affected customers receive instructions. The merchant may then need to update software, hardware, data collection, or staff workflows before the stated effective date.

  1. Read the provider’s notice and identify the exact requirement, affected payment channels, and deadline.
  2. Ask which systems or transaction types are in scope, including terminals, ecommerce, recurring payments, and third-party integrations.
  3. Confirm whether the provider will make the change automatically or whether the merchant must configure, install, test, or supply something.
  4. Test the change in the available test environment or through the provider’s stated process, and keep records of completion.
  5. Check for follow-up notices, since implementation details and deadlines can be revised.

Because a merchant’s provider may implement some changes centrally, the notice may require no action. It is still useful to confirm that point rather than treating silence as proof that the business is unaffected.

Deadlines, costs, and consequences

Deadlines vary. A mandate may have a formal effective date, an earlier testing window, or phased dates for different regions or transaction types. A processor may set an operational cutoff to allow time for testing, so its customer deadline can precede the network’s effective date.

Costs also vary and cannot be inferred from the word “mandate.” A change may be included in an existing service, require a software or terminal update, or involve project work by a vendor. Review the provider’s notice and contract for any stated charges; do not assume that a network announcement itself creates a fixed fee for every merchant.

Failure to comply can lead to declined or incorrectly processed transactions, disruption, disputes, or consequences under the relevant network and provider rules. The specific result depends on the requirement and the participant’s role. Ask the acquirer or processor to explain the applicable consequence rather than relying on a generic claim that every missed mandate leads to a fine.

Mandates versus laws and security standards

A network mandate is not automatically a law. It is a requirement within the network’s operating framework, which participating institutions and their customers may be contractually expected to follow. Laws and regulations are separate sources of obligations, and their applicability depends on the relevant jurisdiction and circumstances.

Likewise, a card-network mandate is not synonymous with the Payment Card Industry Data Security Standard (PCI DSS). PCI DSS is an industry security standard maintained by the PCI Security Standards Council; networks and payment providers may require compliance with it through their rules or agreements. A network mandate can address a narrower technical or operational change without replacing broader security responsibilities.

A common misconception is that “the processor handles it” means the merchant has no role. Providers often manage network connectivity and core message changes, but they may still require a merchant to update a terminal, provide accurate transaction details, or change checkout procedures.

Frequently Asked Questions

Are card payment network mandates mandatory?
They are requirements under the relevant network’s rules for the participants and transactions in scope. Whether a particular merchant must take action depends on its provider, payment setup, and the mandate’s terms.

How do I know whether a mandate affects my business?
Check notices from your acquirer, processor, gateway, or terminal provider. Ask which channels and transaction types are affected, what action is required, and the applicable deadline.

Can a card network mandate change transaction fees?
A mandate does not necessarily change a merchant’s fees. Any charge depends on the provider’s pricing and agreements; review the notice and ask for a written explanation of any proposed fee.

What happens if a merchant misses a mandate deadline?
Possible effects depend on the rule and the provider. Transactions could be disrupted or processed incorrectly, and other consequences may apply under the relevant agreements. Contact the provider promptly to confirm remediation steps.

Are network mandates the same as PCI DSS?
No. Network mandates are requirements issued within a card network’s rules. PCI DSS is a separate payment-card security standard, although network or provider rules may require participants to meet it.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this section

The whole Loan payments section →