Option 3 allows you to post the BIN to full Card number as a POST parameter along with the Transactional JWT. When the Device Data Collection URL is invoked, the Transactional JWT and the BIN will be posted over to the URL. This option allows the integrator to pass the Card BIN directly from the web front end to the Device Data Collection URL instead of the JWT. However, a JWT is still required to authenticate the session. The example below shows the ReturnURL being populated in the Transactional JWT along with a POST parameter.
Integration Steps:
POST Transactional JWT and the Card BIN to the full Card number to the Device Data Collection URL.
Handle the Response from the Device Data Collection URL on the ReturnUrl provided within the Transactional JWT
Option 3 Example
NOTE : This example shows the ReturnUrl being populated in the Transactional JWT along with a POST parameter.
<iFrame height | <iframe name='collectionFrame' height=" |
|
1 width1 style="display: none;">
<form id="collectionForm" name style="visibility: hidden; position: absolute; top: -1000px; left: -1000px;"></iframe>
<form id="collectionForm" target='collectionFrame' name="devicedata" |
|
method actioncentinelapisboxcentinelapistag.cardinalcommerce.com |
|
:50486V1V2/Cruise/Collect">
<!--
POST Parameters: Bin=First 6 digits to full pan of the payment card number. For merchants unable to utilize the First 6 of the Cardnumber, optional Rest API is
|
|
available available to generate a session identifier representing the session. JWT=JWT generated per merchant spec
-->
<input |
|
<input type name value410000 <input type name value value="JWT generated per merchant spec" |
|
/>
</form>
<script>window.onload = function () {
|
|
// Auto submit form on page load
|
|
document document.getElementById('collectionForm').submit();
}
</script> |
|
| Info |
|---|
Click here to review how to handle the Device Data Collection responses. |