Scheme compliance
The data the card schemes require, what Ginger forwards for you, and what you and your merchants must send.
The card schemes set rules on the data in each payment: who the merchant is, who the customer is, and how payments relate to each other. Ginger forwards this data to the processor when the merchant supplies it. Who is responsible depends on your setup:
- Acquirers on Silverflow own the scheme compliance of their merchants. Mastercard and Visa monitor you, for example through Mastercard's Data Integrity programme.
- PayFacs and ISOs process under the acquiring of their processor, which owns the scheme compliance. Follow the rules your processor gives you.
What Ginger forwards through Silverflow
| Requirement | What Ginger sends | Since |
|---|---|---|
| Mastercard 3DS data | The customer's email address or phone number, the billing and shipping address, the cardholder name and the IP address, in every 3DS request. See Mastercard 3DS AReq data | October 2026 |
| Mastercard Transaction Link ID (TLID) | The TLID that links the transactions of one payment | October 2026 |
| Account Funding Transactions | The sender and receiver data the schemes require, including the state for receivers in the US, Canada and Australia, and the birthdate. See Account Funding Transactions | November 2025, June 2026 |
| Recurring payments | The network transaction ID of the first payment, to link the subsequent ones | December 2025 |
| References | The network transaction ID, the retrieval reference number and the approval code in the payment method details; the Payment Account Reference (PAR) for Apple Pay | December 2025, October 2026 |
See the changelog for every change.
What you set
- Merchant category code (MCC). Set the right MCC on each project: the schemes use it for interchange, for the rules that apply (AFTs are required for some MCCs), and for monitoring. See Board merchants on Silverflow.
- Trade name and description. The project's trade name is what the cardholder sees on their statement. A recognisable name prevents disputes.
- 3-D Secure. Decide when to authenticate: see 3-D Secure and SCA.
What your merchants send
Ginger can only forward what the merchant supplies. Tell your merchants to send complete customer details on every order, as described in Send complete customer details in the payment acceptance docs.