Q: Why is the card addition failing?
Answer:
The issue may be due to the AReq message for a Non-Payment Authentication (NPA) transaction contains an incorrect value in the field "threeDSRequestorAuthenticationInd."
Q: How do I check if this is due to merchant’s AReq message?
Answer:
Before escalating, review recent transactions from the same merchant:
- Look for multiple transactions with the same outcome.
- Check if these transactions involve different Visa cardholders.
- Check "threeDSRequestorAuthenticationInd" value in the AReq message
Q: What are the correct values in AReq message?
Answer:
For NPA transactions (where messageCategory = "02"), the value of the field "threeDSRequestorAuthenticationInd" in the AReq message should be either 04, 05, or 06 as per the EMVCo standard.
Values like 01, 02, or 03 are for payment transactions and will cause NPA requests to fail.
Q: What are typical NPA use cases?
Answer:
- Adding a card to a merchant’s app or website (e.g., wallet onboarding).
- Updating stored card details (e.g., expiry date, reissued card).
- Issuer ID&V during token provisioning (e.g., enabling a card for a digital wallet).
Q: What should the bank do if it’s confirmed due to merchant’s AReq message?
Answer:
Please advise the merchant to ensure that the AReq message for NPA transactions includes the correct threeDSRequestorAuthenticationInd value: 04, 05, or 06.