‘Hosted’ and ‘Direct’ tokenization API provide the capability to safely replace or substitute sensitive card detail information or data with a unique random number or identification or token that cannot be mathematically reversed. In return merchants can provide smoother payment flow to customers, with less number of steps to get successful payment. One of the other big benefits that merchant might have is the fact that they do not need to store and handle sensitive data such as card details which it might require them to do special and tight security setup; nonetheless the rigorous process of having to be compliant.
So below are the benefits of using ‘Hosted’ and ‘Direct’ tokenization API:
Beside those benefits previously mentioned, the following are those benefits for using hosted tokenization API:
While, below are those benefits or advantages for using direct tokenization API:
Some requirements for hosted and direct tokenization API:
Hosted tokenization API consisted of some several steps, as mentioned below:
By the end of a successful first request a merchant shall received a tokenization URL.
Fig 3-1. Merchant sends request for tokenization page URL construction.
Fig 3-2. Merchant’s customer is redirected to RDP hosted tokenization page URL.
Fig 3-3. RDP process and send the complete information to respective bank or acquirer tokenization system.
Fig 3-4. RDP payment gateway sends ‘Push Notification’ to merchant’s notification URL.
Fig 3-5. Merchant do transaction query to RDP payment gateway.
For ‘Direct Tokenization API’, it consists of some several steps flow, as explained below:
Fig 3-6. Customers enter their credit card details in merchant’s page.
Fig 3-7. Merchant send request message to RDP to tokenize customer’s card detail.
In sending the transaction request, merchant sends the corresponding transactions request
to RDP’s service end-point by allocating the JSON formatted transaction request inside the
BODY of its HTTP(S) request.
After merchants send the transaction request to RDP’s service end point, they will need to
wait for a direct response from RDP payment gateway.
Fig 3-8. RDP process and send the complete Information to respective bank or acquirer system.
Fig 3-9. DITAPI transaction process flow summary.