- 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 Step-Up Results
After the customer interacts with the issuing bank, the user is redirected back to the
consumerAuthenticationInformation.returnUrl
within the iframe as specified
in Step 3: Payer Authentication Check Enrollment Service. The payload sent to the returnURL
is URL-encoded and Base64-encoded (see the example below). The merchant hosting the
returnURL can then close the iframe after redirection.The response sent back to the return URL contains the following:
- Transaction ID: (consumerAuthenticationInformation.authenticationTransactionIdresponse field). This is used in Step 5: Payer Authentication Validation Service.
- MD: merchant data returned if present in the POST to step-up URL; otherwise, null.
POST to Return URL
TransactionId=BwNsDeDPsQV4q8uy1Kq1&MD=null