On This Page
Recent Revisions to This Document
26.09.01
- E-commerce indicator value for mada co-badged transactions
- madais no longer documented as a valid value for theprocessingInformation.commerceIndicatorfield. For a transaction on a mada co-badged Mastercard or a mada co-badged Visa card, the value isspa. See these topics:
- UCAF fields for mada co-badged transactions
- For merchant decryption of mada co-badged Mastercard and mada co-badged Visa transactions onVisa Platform Connect, theconsumerAuthenticationInformation.ucafAuthenticationDataandconsumerAuthenticationInformation.ucafCollectionIndicatorfields are required.consumerAuthenticationInformation.ucafAuthenticationDatais set to the same value aspaymentInformation.tokenizedCard.cryptogram, andconsumerAuthenticationInformation.ucafCollectionIndicatoris set to2. The REST API code examples for mada include both fields. See these topics:
26.08.01
Added support for the
Chase Tandem
processor. See Processors and Cards Supported with Apple Pay.26.07.01
Added a supported processors and card types list. See Processors and Cards Supported with Apple Pay.
26.03.01
This revision contains only editorial changes and no technical updates.
25.09.01
- XXXXXXXXX VAS CHANGE TITLE XXXXXXXXX
- xxxxx [ Conditionalize all card-specific fields for cards supported by VAS ] xxxxx
- XXXXXXXXX VAS CHANGE TITLE XXXXXXXXX
- xxxxx [ Conditionalize all card-specific fields for cards supported by VAS ] xxxxx
25.04.01
- Initial Release