Skip to main content

Card Scheme vs. Product Mapping (e.g., VPAY / Maestro)

Updated today

Overview This article explains what card data Softpay provides per transaction, why certain card products may appear under a parent scheme name, and how to use AID values for product-level differentiation.


What card data does Softpay provide?

For each transaction, Softpay provides:

  • Card scheme β€” the payment network (e.g. Visa or Mastercard)

  • AID β€” the EMV Application Identifier used in the transaction

Product-level labels (e.g. specific card variants or sub-products) are not exposed as separate fields.


Why might a card product appear under the parent scheme name?

Many card products are sub-variants that operate under a parent scheme. At the EMV level, the transaction is processed based on the AID, which identifies the scheme and application β€” but not the commercial product label. Softpay passes this data as-is and does not apply any additional product mapping.

For example, a card that belongs to a Visa sub-product will appear as Visa, and a Mastercard sub-product will appear as Mastercard. This is standard EMV behaviour, not a limitation specific to Softpay.


Differentiating products using the AID

If your reporting or accounting requires product-level detail, this can be derived downstream by mapping the AID from the transaction data. Below are common AID values for reference.

Visa

AID

A0000000031010 Visa Credit

A0000000032010 Visa Electron

A0000000032020 Visa Debit (VSDC)

A0000000034010 VPay

A0000003101001 Visa Contactless (qVSDC)

Mastercard

AID

A0000000041010 Mastercard Credit / M/Chip

A0000000043060 Maestro

A0000000042203 Mastercard Debit

Did this answer your question?