API Service BRI MT940
MT940 is a swift format file that displays transactions that have occurred according to the request from the Customer based on H+1 time. each MT940 file represents all transactions in "txt" format
MT942 is MT940 which is requested in realtime.
MMT940 and MT942 registration can be done through the MT940 Portal which is integrated with Portal SSO (Single Sign on Portal). Registration is done through the Transaction Banking Division Operational & Help Desk (OHD) section by sending a letter of application and attaching the required information such as:
- Account numbers to be sent MT940 and MT942
- MT940 delivery start date
- The destination of file sent:
- File Protocol
- Host
- Port
- Username
- Password
- Email address (if the MT940 and MT942 files are sent to a specific email address)
MT940 and MT942 files can be sent to:
- Email address
- FTP
The contents and file formats of the MT940 and MT942 are the same. Requests for MT940 and MT942 files through the MT940 Portal and API can be backdated up to a maximum of 3 months back.
Endpoint
API Information
Title |
Service BRI MT940 |
---|---|
Version |
v1.0 |
URL Sandbox |
|
URL Production |
|
Version Control
Doc Version |
API Version |
Date |
Link to document |
Description |
---|---|---|---|---|
v1.0 |
v1.0 |
15 Juli 2021 |
this pages |
Baseline version. |
A. Request Send MT940
Endpoint to make a request for an MT940 file
HTTP Method |
POST |
---|---|
Path |
/request |
Tipe Format |
JSON |
Authentication |
OAuth 2.0 with Access Token |
Header Structure
Key |
Value |
Mandatory |
Length |
Description |
Example |
---|---|---|---|---|---|
BRI-Signature |
{{signature}} |
M |
64 |
|
|
BRI-Timestamp |
{{timestamp}} |
M |
- |
Timestamp Format must follow ISO8601 format (yyyy-MMddTHH:mm:ss.SSSZ) and must be in zero UTC offset |
|
Authorization |
Bearer {{Token}} |
M |
Oauth 2.0 Token
|
||
Content Type |
application/json |
M |
|||
BRI-External-Id |
Alphanum |
M |
9 |
Unique ID on every API request |
687587 |
Request Structure
Field |
Data Type |
Mandatory |
Length |
Description |
Example |
---|---|---|---|---|---|
accountNo |
String |
M |
15 |
Account No |
032301000277566 |
startDate |
String |
M |
8 |
MT940 Delivery Start Date (Format : YYYYMMDDHHMMSS) |
20211116022517 |
endDate |
String |
M |
8 |
MT940 Delivery End Date (Format : YYYYMMDDHHMMSS) |
20211126022517 |
institutionId |
String |
M |
9 |
ID INSTITUSI |
87 |
Response Structure
Field |
Data Type |
Mandatory |
Length |
Description |
Example |
---|---|---|---|---|---|
responseCode |
String |
M |
4 |
Response code |
0000 |
requestId |
String |
M |
9 |
REQUEST ID IF REQUEST SUCCESSFUL |
376 |
responseDescription |
String |
M |
255 |
Response Description |
Success |
Request & Response Payload Sample
Request :
curl --location --request POST 'https://sandbox.partner.api.bri.co.id/v1.0/mt940/checkStatus' \ --header 'BRI-Signature: {{SIGNATURE}}' \ --header 'BRI-Timestamp: {{TIMESTAMP}}' \ --header 'Content-Type: application/json' \ --header 'BRI-External-Id: 4090350' \ --header 'Authorization: Bearer {{Token}}' \ --data-raw '{ "requestId": "327" }'
Normal Response :
{ "responseCode": "0000", "responseDescription": "File has been sent", "data": { "requestId": "327", "institutionId": "97", "accountNo": "039101000283992", "startDate": "20191127", "endDate": "20191127", "statusCode": "1" } }
Error Response :
{ "responseCode": "0003", "responseDescription": "File has not been sent", "data": { "requestId": "328", "institutionCode": "97", "accountNo": "039101000283992", "startDate": "20210805", "endDate": "20210805" } }
List of Error/Response Code
HTTP Status |
Code |
Status |
Response Description |
---|---|---|---|
200 |
0000 |
Success |
Success |
200 |
0001 |
Failed |
Account not registered / Check account format / start date / end date |
200 |
0002 |
Failed |
Duplicate External ID |
200 |
0012 |
Failed |
The following properties are invalid format: %errormessage% |
200 |
0014 |
Failed |
End Date < Start Date |
200 |
0014 |
Failed |
End Date - Start Date > 1 Month |
200 |
0098 |
Failed |
Execute Failed : %error message% |
503 |
0503 |
Failed |
Service Unavailable |
504 |
0504 |
Failed |
Gateway Timeout |
200 |
9999 |
Failed |
General Error |
Any error response not listed in the BRIAPI response list is considered pending and requires further investigation.
B. Check Status MT940
Endpoint to check the status of sending MT940 files
General Information
HTTP Method |
POST |
---|---|
Path |
/checkStatus |
Tipe Format |
JSON |
Authentication |
OAuth 2.0 with Access Token |
Header Structure
Key |
Value |
Mandatory |
Length |
Description |
Example |
---|---|---|---|---|---|
BRI-Signature |
{{signature}} |
M |
64 |
|
|
BRI-Timestamp |
{{timestamp}} |
M |
- |
Timestamp Format must follow ISO8601 format (yyyy-MMddTHH:mm:ss.SSSZ) and must be in zero UTC offset |
|
Authorization |
Bearer {{Token}} |
M |
Oauth 2.0 Token
|
||
Content Type |
application/json |
M |
|||
BRI-External-Id |
Alphanum |
M |
9 |
Unique ID on every API request |
687587 |
Request Structure
Field |
Data Type |
Mandatory |
Length |
Description |
Example |
---|---|---|---|---|---|
requestId |
String |
M |
9 |
ID REQUEST you are looking for |
327 |
Response Structure
Field |
Data Type |
Mandatory |
Length |
Description |
Example |
---|---|---|---|---|---|
responseCode |
String |
M |
4 |
Response code |
0000 |
responseDescription |
String |
M |
255 |
Response Description |
File has been sent |
data |
Array |
- |
Response data on document type |
||
requestId |
String |
9 |
ID REQUEST you are looking for |
327 |
|
institutionId |
String |
9 |
ID INSTITUSI |
97 |
|
accountNo |
String |
15 |
REKENING |
039101000283992 |
|
startDate |
String |
8 |
Start Date |
20191127 |
|
endDate |
String |
8 |
End Date |
20191127 |
|
statusCode |
String |
- |
Status Code |
1 |
Request & Response Payload Sample
Request :
curl --location --request POST 'https://sandbox.partner.api.bri.co.id/v1.0/mt940/checkStatus' \ --header 'BRI-Signature: {{SIGNATURE}}' \ --header 'BRI-Timestamp: {{TIMESTAMP}}' \ --header 'Content-Type: application/json' \ --header 'BRI-External-Id: 4090350' \ --header 'Authorization: Bearer {{Token}}' \ --data-raw '{ "requestId": "327" }'
Normal Response :
{ "responseCode": "0000", "responseDescription": "File has been sent", "data": { "requestId": "327", "institutionId": "97", "accountNo": "039101000283992", "startDate": "20191127", "endDate": "20191127", "statusCode": "1" } }
Error Response :
{ "responseCode": "0003", "responseDescription": "File has not been sent", "data": { "requestId": "328", "institutionCode": "97", "accountNo": "039101000283992", "startDate": "20210805", "endDate": "20210805" } }
List of Error/Response Code
HTTP Status |
Code |
Status |
Response Description |
---|---|---|---|
200 |
0000 |
Failed |
File has been sent |
200 |
0002 |
Failed |
Duplicate External ID |
200 |
0003 |
Failed |
File has not been sent |
200 |
0004 |
Failed |
Request ID is not found |
200 |
0012 |
Failed |
The following properties are invalid format: %errormessage% |
200 |
0098 |
Failed |
Execute Failed : %error message% |
503 |
0503 |
Failed |
Service Unavailable |
504 |
0504 |
Failed |
Gateway Timeout |
500 |
9999 |
Failed |
General Error |
Any error response not listed in the BRIAPI response list is considered pending and requires further investigation.