0% found this document useful (0 votes)
28 views7 pages

RDL Technical Documentation 1.0.2

Uploaded by

leocrys
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
28 views7 pages

RDL Technical Documentation 1.0.2

Uploaded by

leocrys
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 7

1|Page

Document Sign-Off
Version 1.0.0
Author Zola 08 Februari 2019
Reviewer
Approver

Document Change Control


Version Implementation Date Authors Summary of changes
V 1.0.0 21 june 2019 Rizki Kurniawan
V 1.0.1 4 August 2020 Febriana M Chapter 5: Update link encryption library
V 1.0.2 9 February 2021 William Chapter 4: Update link encryption library
Correction Numbering Contents

2|Page
Table of Contents
Document Sign-Off.................................................................................................................................. 2
Document Change Control...................................................................................................................... 2
Table of Contents .................................................................................................................................... 3
1. Biller Client Integration ................................................................................................................... 4
1.1 Biller Client Detail................................................................................................................ 4
1.2 Data Security System .......................................................................................................... 4
2. RDL Notification (BNI eCollection system to Biller Client POST JSON) ........................................... 5
3. Parameter Information ................................................................................................................... 7
4. Encyption Library ............................................................................................................................ 7

3|Page
1. Biller Client Integration
1.1 Biller Client Detail

Biller client should be able to provide technical data for the integration purpose, which
consist:

• A RDL callback URL Credit and Debit

1.2 Data Security System

For security purpose, all messages that sent from and to BNI eCollection will be encrypted
with a library (provided, see Appendix E). The encryption algorithm needs a secret key
which will be provided by BNI eCollection. The secret key is a regular 32 hexadecimal
characters.

Sample of a secret key: 8621e5f22c583c3b7997d75b65be420b

The encryption also uses time to validate the request. Biller client should be able to make
sure the time on the machine which making a request is set properly, though there is a 5
(five) minutes tolerance.

4|Page
2. RDL Notification (BNI eCollection system to Biller Client POST
JSON)

Parameters of payment notification (for more information about each parameter, please
refer to section 2).

Parameter Notes
p2p_id string(40)
account_number varchar(15)
payment_amount decimal(17,3)
accounting_flag char(1)
journal_number varchar(6)
datetime_payment datetime

Notes:
• Callback RDL Credit URL : provided by Biller client,
• Callback RDL Debit URL : provided by Biller client,
• If payment notification failed, our system will send another request to callback URL
until succeed or at maximum 5 times retry,
• A notification is considered as success if and only if response from the callback URL
indicated status = 000 with JSON format (see example on the next page),

5|Page
Example of payment notification :
{
"account_number": "12312301",
"payment_amount": "1000.000",
"accounting_flag": "C",
"journal_number": "751690",
"datetime_payment": "2019-01-03 13:35:50"
}
-------------------------------------------------------------------
{
"p2p_id":" SANDBOX",
"data":"FUdFFUMcHh0WE0QNA1dVXEdQegggOEcZSBFFGRJBQxkFQjNWfVpcX0N
NdnNDR1JYV1s3IQhNRxdFEkUYE0FCGRNFQhBECxQLRlYJB09QSVVHVn
CxQLR0IKeFRMUUhHWHZfVHoEXDYbOBoSQ0cVFEs-EkkIGh0cEkZMERM
FYQ"
}

Response should be like this (otherwise it is considered as a failed request):


{
"status" : "000"
}

6|Page
3. Parameter Information
Parameters of payment notification (for more information about each parameter, please
refer to section 3).

Parameter Data Types Notes

p2p_id varchar(40) P2P ID is given by BNI along with the Secret Key.
account_number varchar(15) This parameter presents account number of lender
payment_amount decimal(17,3) Amount transaction
accounting_flag char(1) This parameter presents only C (credit) or D (debit)
journal_number varchar(6) Journal number, also known as reference number.
Example:
058305
datetime_payment datetime This parameter presents datetime of transaction

Format:
<date> <time>

4. Encyption Library
a. ASP.NET
https://drive.google.com/drive/folders/1FVeMXrulIFYD4wSMu9VZyHBta_u67GmV
b. Java
https://drive.google.com/drive/folders/1HV0ID6kDlhE9wEwyjrIRZKl7rsot-3Ut
c. PHP
https://drive.google.com/drive/folders/1i83VTz8aKM7JreQuxDbUlD0AR5JGb4Zu
d. Python
https://drive.google.com/drive/folders/1f_JSTugu93IsRh2VkypW-3fkZQTPx2sT
e. Node.Js
https://drive.google.com/drive/folders/1zriWgdhvkDrtYSsFse_AK5ygV0uZhMo2
f. Golang
https://drive.google.com/drive/folders/1n1pjMTEmxrrnkQnWZK5iXobCo-a3LDdU

7|Page

You might also like