Endpoints
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 |
Prerequisites
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
Implementation Options
Overview of each Device Data Collection option.
Option 1 - Data Exchange API plus JWT [Recommended]
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.
Option 2 - JWT - Card BIN in JWT
This option allows the integrator to pass the Card BIN in the JWT. As part of the JWT generation add the card bin to full card number in the Payload within the Transactional JWT. When the Device Data Collection URL is invoked, the Transactional JWT will be posted over to the URL.
Integration Steps:
Card BIN goes into the Transactional JWT
POST Transactional JWT to the Device Data Collection URL
Handle the Response from the Device Data Collection URL on the ReturnUrl provided within the TransactionalJWT
Return URL Example -
Code Block |
---|
<iframe name='collectionFrame' height="10" width="10" style="visibility: hidden; position: absolute; top: -1000px; left: -1000px;"></iframe>
<form id="collectionForm" target="collectionFrame" name="devicedata" method="POST" action="https://centinelapistag.cardinalcommerce.com/V2/Cruise/Collect">
<input type="hidden" name="JWT" value="Transactional JWT generated per specification" />
</form>
<script>window.onload = function () {
// Auto submit form on page load
document.getElementById('collectionForm').submit();
}
</script> |
NOTE: This example shows the ReturnUrl being populated in the Transactional JWT instead of a POST parameter.
Device Data Collection Response Options
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 -
Option 1 - Using a ReturnUrl
Option 2 - Using postMessage
Info |
---|
V2 Endpoint provides additional context related to Cardinal Data Collection and MethodUrl Collection when compared to the V1 Endpoint. |