RDP Direct API

Amendment

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

Initial release.

2 1.1 May 15, 2017

Adding in Wallet aggregator functions

  • wallet_id, wallet_id_sc_01
  • signature for wallet-mode
  • pending status for response
  • Query result API
  • Renaming Message Data into Payment Process field
3 1.2 May 22, 2017
  • notify_url
  • Add in Push Notification Result
4 1.3 September 19, 2017

Add response code list under Appendix B

5 1.4 September 20, 2017

Add new parameter ‘bin_filter_code’ in 4.2.2 (Transaction Request Parameter)

6 1.5 September 22, 2017
  • Update the DAPI process flow figure (chapter 3.2)
  • Add back the chapter 3.3 (Online Documentation URL)
  • For chapter 4.2.2 (Transaction request parameters):
    • Add new parameter ‘payer_id’, ‘token_mod’ and ‘token_mod_id’.
    • Modify the length of ‘payer_email’ parameter.
    • Edit or modify the description of ‘bin_filter_code’ parameter.
  • For chapter 4.3.1 (Transaction response parameters):
    • Add new parameter ‘payer_id’.
  • Modify the chapter number for ‘Best Practices’.
  • Modify Appendix A on signature calculation code.
  • Add Appendix C (Payment Mode List)
7 1.6 October 5, 2017

Add response code item “-100”

8 1.7 October 25, 2017
  • For chapter 4.3.1 (Transaction response parameters):
    • Add parameter ‘request_mid’.
    • Add parameter ‘request_timestamp’.
    • Add parameter ‘payment_mode’.
    • Modify the pending response code information.
    • Add sample message.
  • For chapter 5.2 (Push notification result parameters):
    • Add parameter ‘request_timestamp’.
  • For chapter 6.5 (Query result response parameters):
    • Add parameter ‘request_timestamp’.
    • Modify the pending response code information.
  • For Appendix B (Response Code):
    • Add response code “-1” and “-01”
9 1.8 November 16, 2017
  • 4.3.1. Transaction Response Parameters
    • Add parameter ‘response_status’.
  • Appendix C (Response Code List)
    • Adding new response codes.
    • Updating response code description.
10 1.9 November 29, 2017
  • 3.1. Description and Requirements
    • Add requirement about PCI-DSS compliance need.
11 1.10 December 20, 2017
  • 4.2.3. Transaction Request Signature
    • Correction on line “Example: 4026000002 (from 4026000000000002)”
12 1.11 January 9, 2018
  • 4.2.3 (Transaction Request Signature)
    • Rectify the example on the step 2: for tokenization mode (token id and payer id).
  • 4.3.1 (Transaction Response Parameters)
    • Edit the status and description of parameter ‘signature’.
  • 4.3.2 (Transaction Response Signature)
    • Add a ‘Note’ section.
  • 5.2 (Push Notification Result Parameters)
    • Edit the status and description of parameter ‘signature’.
  • 6.5 (Query Result Response Parameter)
    • Edit the status and description of parameter ‘signature’.
13 1.12 February 2, 2018
  • 4.2.3 (Transaction Request Signature)
    • Rectify the detail on step 2: for tokenization mode on payer_id.
14 1.13 February 7, 2018
  • 4.2.3 (Transaction Request Signature)
    • Rectify and edit the detail on step 2 onwards.
15 1.14 March 12, 2018
  • 4.2.2 (Transaction Request Parameters)
    • Add billing information parameters
16 1.15 March 15, 2018
  • 6.5 (Query Result Response Parameter)
    • Add new parameter ‘fds’.
  • APPENDIX B (Response Code)
    • Modify the description for response code: -1400.
  • New ‘APPENDIX D (‘fds’ Query Result Response Parameter)’ section.
17 1.16 March 23, 2018
  • 4.2.2 (Transaction Request Parameter)
    • Modify the ‘payment_type’ parameter description (adding note).
  • APPENDIX C (Payment Mode List)
    • Updating and adding 2 new more payment modes inside the list (WeChat and Konbini).
18 1.17 December 18, 2018
  • 4.2.2 (Transaction Request Parameter)
    • Modify the value type and description of ‘amount’ parameter.