API Opening Account RDN v2.0
API Information
Title |
Opening Account RDN v2.0 |
---|---|
Version |
v2.0 |
URL Sandbox |
|
URL Production |
Version Control
*fill in with version API and changes description
Example:
API Version |
Date |
Link to document |
Description |
---|---|---|---|
v2.0 |
18 Maret 2021 |
this pages |
Baseline version. |
v2.0 |
31 Maret 2021 |
this pages |
Penambahan Header "BRI-External-ID" |
v2.0 |
1 April 2021 |
this page |
Penambahan List Response Code |
v2.0 |
8 Agustus 2021 |
this page |
Penambahan flow Opening Account RDN |
Product Description
Product Overview
The following services are used to apply for the opening of a Customer Fund Account (RDN) from a Securities Company to BRI.
Endpoint
A. Request OTP
Endpoint Description
The following service is used to request an OTP code and validate the account number and cellphone number of the customer from the Securities Company to BRI prior to the submission of the opening of the Customer Fund Account (RDN).
General Information
HTTP Method | POST |
---|---|
Path | /v2.0/rdn/RequestOTPOpeningAccountRDN |
Type Format | JSON |
Authentication | OAuth 2.0 with Access Token |
Header Structure
Key |
Value |
Mandatory |
Length |
Description |
Example |
---|---|---|---|---|---|
Authorization |
Bearer {token} |
M |
N/A |
Access Token |
|
BRI-Timestamp |
|
M |
- |
ISO 8601 format. Timestamp must be in UTC or GMT +0 timezone. |
2021-03-18T02:51:48.624Z |
BRI-Signature |
|
M |
64 |
- |
|
Content-Type |
application/json |
M |
- |
- |
|
BRI-External-ID |
Numeric |
M |
9 |
Unique |
|
Request Structure
Field |
Data Type |
Mandatory |
Length |
Description |
Example |
---|---|---|---|---|---|
acctNo |
String |
M |
15 |
BRI account number that the customer had before |
020601003892509 |
phoneNo |
String |
M |
20 |
Cell phone number registered with BRI |
08180792xxxx |
partnerID |
String |
M |
5 |
Unique code for each Securities Company |
0D001 |
Response Structure
Field |
Data Type |
Mandatory |
Length |
Description |
Example |
---|---|---|---|---|---|
responseCode |
String |
M |
2 |
Response code |
14 |
responseDescription |
String |
M |
- |
Response description |
OTP requested succesfully |
data |
Object |
M |
- |
JSON Object |
- |
errorMessage |
String |
M |
6 |
Error Message |
RD-200 |
otp |
String |
C |
6 |
One Time Password |
123456 |
registrationID |
String |
M |
12 |
Unique ID for each submission |
123456789012 |
Request and Response Payload Sample
Request :
{ "acctNo":"020601003892509", "phoneNo":"085772333293", "partnerID":"0D001" }
Normal Response :
{ "responseCode":"00", "responseDescription":"OTP requested succesfully", "data":{ "errorMessage":"RD-200", "otp":"489253", "registrationID":"023693307517" } }
Erorr Response :
{ "responseCode":"53", "responseDescription":"Nomor Rekening Tidak Dikenal", "data":{ "errorMessage":"RD-053" } }
List of Error/Response Code
HTTP Status |
Error Message |
Response Code |
Status |
Response Description |
Description |
---|---|---|---|---|---|
200 |
RD-200 |
00 |
Success |
OTP requested succesfully |
OTP request is successful if it gets response RC 00 |
200 |
RD-053 |
53 |
Failed |
Unknown Account Number |
OTP request failed |
200 |
RD-005 |
05 |
Failed |
Phone number not matched with account |
OTP request failed |
200 |
RD-014 |
14 |
Failed |
Phone number not found |
OTP request failed |
200 |
RD-028 |
14 |
Failed |
Partner ID or Branch not found |
OTP request failed |
200 |
RD-999 |
99 |
Failed |
General error |
OTP request failed |
200 |
RD-099 |
99 |
Failed |
data cannot be null or blank |
OTP request failed |
B. Opening Account
Endpoint Description
The following service is used to apply for the opening of a Customer Fund Account (RDN) from the Securities Company to BRI which previously had CIF data at BRI.
General Information
HTTP Method |
POST |
---|---|
Path |
/v2.0/rdn/OpeningAccountRDN |
Tipe Format |
JSON |
Authentication |
OAuth 2.0 with Access Token |
Header Structure
Key |
Value |
Mandatory |
Length |
Description |
Example |
---|---|---|---|---|---|
Authorization |
Bearer {token} |
M |
N/A |
Access Token |
|
BRI-Timestamp |
|
M |
- |
ISO 8601 format. Timestamp must be in UTC or GMT +0 timezone. |
2021-03-18T02:51:48.624Z |
BRI-Signature |
|
M |
64 |
- |
|
Content-Type |
application/json |
M |
- |
- |
|
BRI-External-ID |
Numeric |
M |
9 |
Unique |
|
Request Structure
Field |
Data Type |
Mandatory |
Length |
Description |
Example |
---|---|---|---|---|---|
registrationID |
String |
M |
12 |
Unique ID for each submission |
123456789012 |
partnerID |
String |
M |
5 |
Unique code for each Securities Company |
0D001 |
acctNo |
String |
M |
5 |
BRI account number that the customer had before |
02060100000xxxx |
otp |
String |
M |
15 |
One Time Password upon request |
123456 |
sid |
String |
M |
6 |
SID number from KSEI |
IDD2707TY390527 |
sre |
String |
M |
15 |
Securities sub account number from KSEI |
OD001108A00151 |
branch |
String |
M |
4 |
BRI branch office managing funds |
0206 |
timestamp |
String |
M |
|
TnC approval timestamp in the format: yyyy-MM-dd HH:mm:ss |
2021-02-14 23:30:40 |
Response Structure
Field |
Data Type |
Mandatory |
Length |
Description |
Example |
---|---|---|---|---|---|
responseCode |
String |
M |
2 |
Response code |
14 |
responseDescription |
String |
M |
- |
Response description |
OTP requested succesfully |
data |
Object |
M |
- |
JSON Object |
- |
errorMessage |
String |
M |
6 |
Error Message |
RD-200 |
registrationID |
String |
M |
12 |
Unique ID for each submission |
123456789012 |
Request and Response Payload Sample
Request :
{ "registrationID":"543112023666", "partnerID":"0D001", "acctNo":"020601003892509", "otp":"648246", "sid":"123456789012387", "sre":"12345678901239", "branch":"0206", "timestamp":"2021-02-1423:30:40" }
Normal Response :
{ "responseCode":"01", "responseDescription":"InvestorValidationdalamproses", "data":{ "errorMessage":"RD-201", "registrationID":"123456789012" } }
Erorr Response :
{ "responsecode": "07", "responseDescription": "OTP tidak sesuai", "data": { "errorMessage": "RD-201" } }
List of Error/Response Code
HTTP Status |
Error Message |
Response Code |
Status |
Response Description |
Description |
---|---|---|---|---|---|
200 |
RD-201 |
01 |
Success |
Investor Validation in the process |
Response success if you get RC 01 |
200 |
RD-006 |
06 |
Failed |
OTP does not match |
Account opening request failed |
200 |
RD-028 |
14 |
Failed |
Partner ID or Branch not found |
Account opening request failed |
200 |
RD-007 |
14 |
Failed |
Registration ID not registered or being processed |
Account opening request failed |
200 |
RD-999 |
99 |
Failed |
General error |
Account opening request failed |
C. Upload Doc
Endpoint Description
The following service is used to send application documents for opening a Customer Fund Account (RDN) by the Securities Company to BRI. Mandatory documents are KTP and Signature in jpg format and optional documents are NPWP.
General Information
HTTP Method |
POST |
---|---|
Path |
/v2.0/rdn/UploadDoc |
Tipe Format |
JSON |
Authentication |
OAuth 2.0 with Access Token |
Header Structure
Key |
Value |
Mandatory |
Length |
Description |
Example |
---|---|---|---|---|---|
Authorization |
Bearer {token} |
M |
N/A |
Access Token |
|
BRI-Timestamp |
|
M |
- |
ISO 8601 format. Timestamp must be in UTC or GMT +0 timezone. |
2021-03-18T02:51:48.624Z |
BRI-Signature |
|
M |
64 |
- |
|
Content-Type |
application/json |
M |
- |
- |
|
BRI-External-ID |
Numeric |
M |
9 |
Unique |
|
Request Structure
Field |
Data Type |
Mandatory |
Length |
Description |
Example |
---|---|---|---|---|---|
registrationID |
String |
M |
12 |
Unique ID for each submission |
123456789012 |
partnerID |
String |
M |
5 |
Unique code for each Securities Company |
0D001 |
sid |
String |
M |
15 |
SID number from KSEI |
IDD2707TY390527 |
sre |
String |
M |
14 |
Securities sub account number from KSEI |
123456789112342 |
ktp |
String |
M |
Max: 250KB |
Customer ID card (.jpg) |
Encrypted Base64 |
npwp |
String |
O |
Max: 250KB |
NPWP nasabah ( .jpg) |
Encrypted Base64 |
signature |
String |
M |
Max: 250KB |
Customer signature (.jpg) |
Encrypted Base64 |
formData |
String |
M |
Max: 250KB |
AR01 data in file form (.txt) |
Encrypted Base64 |
form |
String |
M |
Max: 250KB |
File AR01 dalam format pdf |
Encrypted Base64 |
Response Structure
Field |
Data Type |
Mandatory |
Length |
Description |
Example |
---|---|---|---|---|---|
responseCode |
String |
M |
2 |
Response code |
14 |
responseDescription |
String |
M |
- |
Response description |
OTP requested succesfully |
data |
Object |
M |
- |
JSON Object |
- |
errorMessage |
String |
M |
6 |
Error Message |
RD-203 |
Request and Response Payload Sample
Request :
{ "registrationID":"113765099643", "partnerID":"0D001", "sid":"IDD2707TY390527", "sre":"OD001108A00151", "ktp":"data:image/jpeg;base64,/9j/4AAQSkZJRgABAQAAAQABAAD/", "npwp":"data:image/jpeg;base64,/9j/4AAQSkZJRgABAQAAAQABAAD/", "signature":"data:image/jpeg;base64,/9j/4AAQSkZJRgABAQAAAQABAAD/", "formData":"data:file/txt;base64,/9j/4AAQSkZJRgABAQAAAQABAAD/", "form":"data:file/pdf;base64,/9j/4AAQSkZJRgABAQAAAQABAAD/" }
Normal Response :
{ "responseCode": "00", "responseDescription": "Doc accepted", "data": { "errorMessage": "RD-203" } }
Erorr Response :
{ "responseCode": "14", "responseDescription": "Registration ID tidak terdaftar", "data": { "errorMessage": "RD-007" } }
List of Error/Response Code
HTTP Status |
Error Message |
Response Code |
Status |
Response Description |
Description |
---|---|---|---|---|---|
200 |
RD-203 |
00 |
Success |
Doc accepted |
Successful response is RC 00 |
200 |
RD-007 |
14 |
Failed |
Registration ID is not registered or documents are complete |
Upload doc failed |
200 |
RD-999 |
99 |
Failed |
General error |
Upload doc failed |
200 |
RD-099 |
99 |
Failed |
data cannot be null or blank |
Upload doc failed |
D. Push Notification Approval
Endpoint Description
The following service is used to send information on the application for opening a Customer Fund Account (RDN) from BRI to the Securities Company.
General Information
HTTP Method |
POST |
---|---|
Path |
Provide by PE |
Tipe Format |
JSON |
Authentication |
OAuth 2.0 with Access Token |
Header Structure
Key |
Value |
Mandatory |
Length |
Description |
Example |
---|---|---|---|---|---|
Content-Type |
application/json |
M |
- |
- |
|
Request Structure
Field |
Data Type |
Mandatory |
Length |
Description |
Example |
---|---|---|---|---|---|
registrationID |
String |
M |
12 |
Unique ID for each submission |
123456789012 |
sid |
String |
M |
15 |
SID number from KSEI |
IDD2707TY390527 |
sre |
String |
M |
14 |
Securities sub account number from KSEI |
123456789112342 |
partnerID |
String |
M |
5 |
Unique code for each Securities Company |
0D001 |
regStatus |
String |
M |
4 |
Registration status code |
0000 |
regDescription |
String |
O |
- |
Description of registration status code |
RDN berhasil diproses |
accountRDN |
String |
C |
15 |
Customer fund account |
067101000039317 |
accountName |
String |
C |
20 |
RDN owner name |
ABHIYASA SUTA BHUMIKAPALA |
Response Structure
Field |
Data Type |
Mandatory |
Length |
Description |
Example |
---|---|---|---|---|---|
responseCode |
String |
M |
2 |
Response code |
14 |
responseDescription |
String |
M |
- |
Response description |
OTP requested succesfully |
data |
Object |
M |
- |
JSON Object |
- |
registrationID |
String |
M |
12 |
Unique ID for each submission |
123456789012 |
partnerID |
String |
M |
5 |
Unique code for each Securities Company |
0D001 |
List of Registration Status
Error Code |
Response Description |
---|---|
0001 |
Investor validation in process |
1001 |
Invalid SID and SRE |
0002 |
Document Incomplete |
0003 |
RDN opening is being done |
0004 |
Crosslink in process |
0000 |
RDN processed successfully |
Request and Response Payload Sample
Request 1:
{ "registrationID":"123456789012", "sid":"IDD2707TY390527", "sre":"OD001108A00151", "partnerID":"0D001", "regStatus":"0002", "regDescription":"Document Incomplete", "accountRDN":"067101000039317", "accountName":"ABHIYASASUTABHUMIKAPALA" }
Request 2:
{ "registrationID":"123456789012", "sid":"IDD2707TY390527", "sre":"OD001108A00151", "partnerID":"0D001", "regStatus":"0000", "regDescription":"RDNberhasildiproses", "accountRDN":"067101000039317", "accountName":"ABHIYASASUTABHUMIKAPALA" }
Normal Response :
{ "responseCode":"00", "responseDescription":"RecordBerhasildiproses", "data":{ "registrationID":"123456789012", "partnerID":"0D001" } }
Erorr Response :
{ "responseCode":"14", "responseDescription":"Registration ID tidak terdaftar", "data":{ "registrationID":"123456789012", "partnerID":"0D001" } }
List of Error/Response Code
HTTP Status |
Code |
Status |
Response Description |
Description |
---|---|---|---|---|
200 |
00 |
Success |
Record Successfully saved |
Successful response is RC 00 |
200 |
14 |
Failed |
Registration ID not registered |
Response Failed |
200 |
99 |
Failed |
General error |
Response Failed |
E. Get Status Approval
Endpoint Description
The following service is used to find out the status of the application for opening a Customer Fund Account (RDN) by a Securities Company to BRI.
General Information
HTTP Method |
POST |
---|---|
Path |
/v2.0/rdn/GetStatusApproval |
Tipe Format |
JSON |
Authentication |
OAuth 2.0 with Access Token |
Header Structure
Key |
Value |
Mandatory |
Length |
Description |
Example |
---|---|---|---|---|---|
Authorization |
Bearer {token} |
M |
N/A |
Access Token |
|
BRI-Timestamp |
|
M |
- |
ISO 8601 format. Timestamp must be in UTC or GMT +0 timezone. |
2021-03-18T02:51:48.624Z |
BRI-Signature |
|
M |
64 |
- |
|
Content-Type |
application/json |
M |
- |
- |
|
BRI-External-ID |
Numeric |
M |
9 |
Unique |
|
Request Structure
Field |
Data Type |
Mandatory |
Length |
Description |
Example |
registrationID |
String |
M |
12 |
Unique ID for each submission |
123456789012 |
sid |
String |
M |
15 |
SID number from KSEI |
020601000007317 |
sre |
String |
M |
14 |
Securities sub-account number from KSEI |
123456789112342 |
partnerID |
String |
M |
5 |
Unique code for each Securities Company |
0D001 |
Response Structure
Field |
Data Type |
Mandatory |
Length |
Description |
Example |
---|---|---|---|---|---|
responseCode |
String |
M |
2 |
Response code |
14 |
responseDescription |
String |
M |
- |
Response description |
Registration successfully |
data |
Object |
M |
- |
JSON Object |
- |
errorMessage |
String |
M |
6 |
Error Message |
RD-203 |
regStatus |
String |
C |
6 |
Registration status code |
0001 |
regDescription |
String |
C |
5 |
Registration status code description |
Documents incomplete |
accountRDN |
String |
C |
15 |
Customer fund account |
020601000007317 |
accountName |
String |
C |
20 |
RDN owner name |
ABHIYASA SUTA BHUMIKAPALA |
List of Registration Status
Error Code |
Response Description |
---|---|
0001 |
Investor validation is being processed |
1001 |
SID and SRE are invalid |
0002 |
Document Incomplete |
0003 |
RDN opening is underway |
0004 |
Crosslink in progress |
0000 |
RDN successfully processed |
Request and Response Payload Sample
Request :
{ "registrationID":"123456789012", "sid":"IDD2707TY390527", "sre":"OD001108A00151", "partnerID":"0D001" }
Normal Response :
{ "responseCode": "00", "responseDescription": "Pengajuan Ditemukan", "data": { "errorMessage": "RD-208", "regStatus": "0004", "regDescription": "Crosslink dalam proses", "accountName": null } }
Erorr Response :
List of Error/Response Code
HTTP Status |
Error Message |
Response Code |
Status |
Response Description |
Description |
---|---|---|---|---|---|
200 |
RD-208 |
00 |
Success |
Pengajuan ditemukan |
RC 00 adalah Response Sukses |
200 |
RD-004 |
04 |
Failed |
Pengajuan Tidak Ditemukan |
Response Failed |
200 |
RD-999 |
99 |
Failed |
General error |
Response Failed |
G. Get List Branch
Endpoint Description
SThe following service is used to create a list of BRI branches from the Securities Company to BRI before submitting an application to open a Customer Fund Account (RDN).
General Information
HTTP Method |
POST |
---|---|
Path |
/v2.0/rdn/GetListBranch |
Tipe Format |
JSON |
Authentication |
OAuth 2.0 with Access Token |
Header Structure
Key |
Value |
Mandatory |
Length |
Description |
Example |
---|---|---|---|---|---|
Authorization |
Bearer {token} |
M |
N/A |
Access Token |
|
BRI-Timestamp |
|
M |
- |
ISO 8601 format. Timestamp must be in UTC or GMT +0 timezone. |
2021-03-18T02:51:48.624Z |
BRI-Signature |
|
M |
64 |
- |
|
Content-Type |
application/json |
M |
- |
- |
|
BRI-External-ID |
Numeric |
M |
9 |
Unique |
|
Request Structure
Field |
Data Type |
Mandatory |
Length |
Description |
Example |
---|---|---|---|---|---|
partnerID |
String |
M |
5 |
Unique code for each Securities Company |
0D001 |
Response Structure
Field |
Data Type |
Mandatory |
Length |
Description |
Example |
---|---|---|---|---|---|
responseCode |
String |
M |
2 |
Response code |
14 |
responseDescription |
String |
M |
- |
Response description |
OTP requested succesfully |
data |
Object |
M |
- |
JSON Object |
- |
errorMessage |
String |
M |
6 |
Error Message |
RD-203 |
partnerID |
String |
M |
5 |
Unique code for each Securities Company |
0D001 |
branchList |
Array |
C |
|
List of branches in Array form |
|
branchCode |
String |
C |
15 |
BRI branch code |
0206 |
branchName |
String |
C |
20 |
RDN owner name |
KCK |
Request and Response Payload Sample
Request
{ "partnerID":"0D001" }
Normal Response :
{ "responseCode": "00", "responseDescription": "List Branch sukses didapatkan", "data": { "errorMessage": "RD-205", "partnerID": "0D001", "branchList": [ { "branchCode": "0206", "branchName": "KCK" }, { "branchCode": "0341", "branchName": "Pasar Minggu" } ] } }
Erorr Response :
{ "responsecode": "14", "responseDescription": "Partner ID tidak ditemukan", "data": { "errorMessage": "RD-014" } }
List of Error/Response Code
HTTP Status |
Error Message |
Response Code |
Status |
Response Description |
Description |
---|---|---|---|---|---|
200 |
RD-205 |
00 |
Success |
Branch List successfully obtained |
Successful response only RC 00 |
200 |
RD-028 |
14 |
Failed |
Partner ID not found |
Response Failed |
200 |
RD-999 |
99 |
Failed |
General error |
Response Failed |