Skip to content

Mastercard 3DS AReq data

The customer data your merchants send so the 3DS authentication requests of your platform meet Mastercard's data requirements.

For acquirers on Silverflow. Mastercard requires every 3-D Secure (3DS) authentication request (AReq) to carry data from three categories. This page explains which order fields of the Ginger API carry that data, so you can tell your merchants what to send.

What changes

To fight card-not-present fraud, Mastercard requires at least one field from each of these categories in every 3DS AReq:

CategoryMastercard fields
Cardholder identifierEmail address, phone number or cardholder name
AddressBilling address line 1 or shipping address line 1
TechnicalIP address of the browser or device

Mastercard monitors acquirers that fall short through its Data Integrity programme.

Since October 2026, Ginger sends this data to Silverflow in the 3DS authentication request of every Mastercard payment, when the order has it. You don't need to change anything on your side. See the changelog entry of 26 October 2026.

Ginger forwards what the merchant supplies. When an order has no data for a category, there is nothing to send. Meeting the requirement is mainly about what your merchants collect at checkout.

Fields per data category

Merchants set these fields in the customer object when they create the order. See Create an order in the payment acceptance docs for the fields, and Send complete customer details for what your merchants read about it.

Cardholder identifier

DataWhere it comes from
Email addresscustomer.email_address
Phone numberThe first entry of customer.phone_numbers, with the country code, such as +31612345678
Cardholder nameCollected on the hosted payment page. In their own checkout, merchants send it as name when they store the card in the vault

Address

Ginger takes the billing address from:

  1. The first address with address_type billing in customer.additional_addresses.
  2. Otherwise, the address on the customer object, when it has address_type billing.

Ginger takes the delivery address the same way, with address_type delivery.

Each address has the country, postal code, street and house number, city, and the state where it applies.

Technical

DataWhere it comes from
IP addresscustomer.ip_address. On the hosted payment page, Ginger collects the IP address of the browser. In server-to-server integrations, the merchant sends it.

What your merchants do

Pass this guidance on to your merchants:

  • Cardholder identifier: send an email address or a phone number on every order, in case there's no cardholder name.
  • Address: one address meets the requirement. Send the billing address: every order has one, also for digital goods and services that aren't shipped. Send the delivery address as well for physical goods.
  • IP address: in a server-to-server integration, send the IP address of the customer, not the IP address of their own server. A server IP fills the field, but weakens the authentication and the risk assessment.

Next steps