Process Flow for Hybrid Integration

Call Setup service.

Add the JavaScript tag to your checkout page.

Call Cardinal.setup (init).

Run BIN detection. If the BIN is eligible for 3-D Secure 2.x, it gathers the proper Method URL JavaScript required by the issuer to collect additional device data.

User selects the

Submit Payment

button.

You request the Enrollment Check service, passing in transaction details and the

payerAuthEnrollService_referenceID

request field.

If the issuing bank does not require authentication, you receive this information in the Enrollment Check response:

E-commerce indicator
CAVV (all card types except Mastercard)
AAV (Mastercard only)
Transaction ID
3-D Secure version
Directory server transaction ID

If the issuing bank requires authentication, you receive a response with the ACS URL of the issuing bank, the payload, and the transaction ID that you include in the

Cardinal.continue

JavaScript call.

The JavaScript displays the authentication window, and the customer enters the authentication information.

The bank validates the customer credentials, and a JWT is returned that the merchant is required to validate server-side for security reasons.

You request the Validate Authentication service, extracting the processor transaction ID value from the JWT and sending it in the

payerAuthValidateService_authenticationTransactionID

request field. You receive the e-commerce indicator, CAVV or AAV, transaction ID, 3-D Secure version, and directory server transaction ID.