RDP Hosted and Direct Tokenization API

Amendment

No. Version Date of Release Amendment Details
1 1.0 May 2, 2017

Initial release.

2 1.1 May 8, 2017
  • Some new parameters under first phase request message.
3 1.2 May 18, 2017
  • Add direct tokenization API flow
  • Split the messaging detail between hosted and direct tokenization API.
4 1.3 May 22, 2017
  • wallet_id in DITAPI request
  • notify_url in DITAPI request
  • pending status at response_code DITAPI
  • pending status at Query Phase
  • DITAPI Process Flow
5 1.4 August 16, 2017
  • Add payer_email field in direct and re-direction
6 1.5 September 11, 2017
  • Modify ‘payer_email’ parameter to be a mandatory field under chapter 5.3 (first phase request parameter) and 8.2 (DITAPI request parameter)
  • Merge chapter 3.3 and 8.2 about the DITAPI process flow to be put into chapter 3.3.
7 1.6 September 19, 2017
  • Add Appendix A (Response Code)
8 1.7 October 25, 2017
  • For chapter 3.3 (Direct Tokenization API (DITAPI) Process Flow):
    • Modify the steps 6, for the pending status.
  • For chapter 6.2 (Push Notification Result Parameters):
    • Modify the pending response code information.
  • For chapter 7.5 (Redirection Result – Query Response Parameter):
    • Modify the pending response code information.
  • For chapter 8.3 (Response Parameters):
    • Modify the pending response code information.
  • For Appendix A (Response Code):
    • Add response code ‘-1’ and ‘-01’.
9 1.8 January 12, 2018
  • 4 (Signature)
    • Add a ‘Note’ section.
  • 5.4 (First Phase Response Parameters)
    • Edit the status and description of parameter ‘signature’.
  • 6.2 (Push Notification Result Parameters)
    • Edit the status and description of parameter ‘signature’.
  • 7.5 (Redirection Result – Query Response Parameter)
    • Edit the status and description of parameter ‘signature’.
  • 8.3 (Response Parameters)
    • Edit the status and description of parameter ‘signature’.
10 1.9 March 6, 2018
  • 5.3 (First Phase Request Parameters)
    • Add new parameter ‘payer_name’ and ‘ccy’.
    • Modify the ‘payer_email’ parameter status.
  • 6.2 (Push Notification Result Parameters)
    • Modify the ‘first_6’, ‘last_4’, ‘exp_date’, and ‘payer_name’ parameter status.
  • 7.5 (Redirection Result – Query Response Parameter)
    • Add new parameter ‘ccy’.
    • Modify the ‘first_6’, ‘last_4’, ‘exp_date’, and ‘payer_name’ parameter status.
  • 8.2 (Request Parameters)
    • Add new parameter ‘payer_name’ and ‘ccy’.
    • Delete parameter ‘notify_url’.
  • 8.3 (Response Parameters)
    • Add new parameter ‘ccy’.
    • Modify the ‘first_6’, ‘last_4’, ‘exp_date’, and ‘payer_name’ parameter status.
11 1.10 March 23, 2018
  • 5.3 (First Phase Request Parameters)
    • Add new parameter ‘type’.
  • 6.2 (Push Notification Result Parameters)
    • Add new parameter ‘ccy’.
  • 8.2 (Request Parameters)
    • Add new parameter ‘type’.