Step 1: Registration Check
Integrators use the Data Exchange API’s /Encrypted/GetInfo endpoint to check a user’s Visa Payment Passkey enrollment and supported authentication programs, providing real-time transaction insights prior to authentication.
JSON
{
"Algorithm": "SHA-256",
"Identifier": "582e0a2033fadd1260f990f6",
"OrgUnitId": "582be9deda52932a946c45c4",
"Payload": {
"AccountNumber": "4761120010000492",
"AcquirerCountryCode": "840",
"CardBrand": "Visa",
"Email": "test.user@example.com",
"LanguagePreference": [
"en"
],
"Payment": {
"Amount": "12.34",
"CurrencyCode": "USD",
"MerchantName": "Test Merchant"
},
"ReferenceId": "87f635a1-287e-487d-aa8e-8085c2061f01"
},
"Signature": "EJ5TdXS+enaQGEA23EupHOMFCmgVk1iFW3msP4yjo+Q=",
"Timestamp": 1794883255675,
"TransactionId": "1d39ff4c-cfac-49ee-84a7-e0ac098e1e8d"
}
Step 2: Data Exchange Results
This is the complete JWT token that will be sent to Cardinal Commerce:
API Response
{
"ErrorNumber": 0,
"ErrorDescription": "Success",
"RequestId": "0d0736ad-18c3-423e-bac8-b97c541697b5",
"Payload": {
"Account": {
"CardBrand": "Visa",
"LastFour": "0492"
},
"Issuer": {
"SupportedVersions": [
{
"Version": "2.2.0",
"Capabilities": [
"VisaPaymentPasskeyEnabled"
],
"MethodURLPresent": true
}
]
},
"ReferenceId": "87f635a1-287e-487d-aa8e-8085c2061f01"
}
}
Step 3: Post JWT to Device Data Collection
When using DDC with FIDO, the ReferenceId in the DDC call must match the ReferenceId returned by the Data Exchange API in step 2.
JWT
eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJqdGkiOiIxZDM5ZmY0Yy1jZmFjLTQ5ZWUtODRhNy1lMGFjMDk4ZTFlOGQiLCJpYXQiOjE3OTQ4ODMyNTYsImlzcyI6IjU4MmUwYTIwMzNmYWRkMTI2MGY5OTBmNiIsIk9yZ1VuaXRJZCI6IjU4MmJlOWRlZGE1MjkzMmE5NDZjNDVjNCIsIlJlZmVyZW5jZUlkIjoiODdmNjM1YTEtMjg3ZS00ODdkLWFhOGUtODA4NWMyMDYxZjAxIiwiUGF5bG9hZCI6eyJPcmRlckRldGFpbHMiOnsiQW1vdW50IjoiMTIuMzQiLCJDdXJyZW5jeUNvZGUiOiJVU0QifX19.1BwH-K10o1Wh4U6DY_SII9m046SwrK1eMsahpRZvfIU
Device Data Collection in progress...