- Introducing Payer Authentication
- Implementing Cardinal Cruise Direct Connection API Payer Authentication
- Implementing SDK Payer Authentication
- API Fields
- Testing Payer Authentication
- 3-D Secure 1.0 Testing
On This Page
REST API
Receiving the Authentication Results
Next,
payments.validated
launches, and returns the authentication results and
response JWT along with the processor transaction ID as shown in the following
example.Decoded Response JWT
{ "iss": "5a4504be6fe3d1127cdfd94e", "iat": 1555075930, "exp": 1555083130, "jti": "cc532159-636d-4fa8-931d-d4b0f4c83b99", "ConsumerSessionId": "0_9a16b7f5-8b94-480d-bf92-09cd302c9230", "aud": "d0cf3392-62c5-4107-bf6a-8fc3bb49922b", "Payload": { "Payment": { "Type": "CCA", "ProcessorTransactionId": "YGSaOBivyG0dzCFs2Zv0" }, "ErrorNumber": 0, "ErrorDescription": "Success" } }