Connection Endpoints for Staging and Production -
Version | Environment | Endpoint | Description |
---|---|---|---|
V2 (NEW) | Staging | https://centinelapistag.cardinalcommerce.com/V2/Cruise/Collect | Merchants integrating to the v2 endpoint will receive additional information regarding the Cardinal Data Collection and MethodUrl Collection. |
Production | |||
V1 | Staging | https://centinelapistag.cardinalcommerce.com/V1/Cruise/Collect | N/A |
Production |
To support Device Data Collection, you must complete one of these Options below
The Integrator must have access to the card BIN or full card number of cardholder
The Integrator must create an iframe on their website and post to the Device Data Collection URL
Overview of each Device Data Collection option.
This option allows the integrator to not pass the full Card Number in the JWT, but allows you to pass the full Card Number in an API Call to setup the Device Data Collection session and in response obtain a ReferenceId to pass up to the web frontend instead of the Card BIN. In addition to ReferenceId, you will receive additional data points for the given Card Number that can be leveraged during authentication.
This option allows the integrator to pass the Card BIN in the JWT
The merchant needs to handle the Response that they get from Device Data Collection Url.
This can be achieved by using either of the following options -
V2 Endpoint provides additional context related to Cardinal Data Collection and MethodUrl Collection when compared to the V1 Endpoint. |