Fund Transfer Internal v3.1

Download Postman

Product Overview

This API allows partners to transfer funds between two BRI accounts (internal transfer). The source account is the partner's account. Fund transfer API can only be done for checking accounts and savings accounts.

Endpoint

Endpoint Description

This service is used to make inquiries of Debit and Credit account information that will be used to carry out Fund Transfer instructions. Accounts that can be inquired are Current Accounts that have been registered and Beneficiary Accounts.

General Information

Header Structure

Request Structure

Response Structure

Request & Response Payload Sample

Request :

curl --location --request POST 'https://sandbox.partner.api.bri.co.id/v3.1/transfer/internal/accounts' \
--header 'BRI-Timestamp: ((TIMESTAMP))' \
--header 'BRI-Signature: ((SIGNATURE))' \
--header 'Content-Type: application/json' \
--data-raw '{
"sourceAccount": "020601000255504",
"beneficiaryAccount": "0206010060313061"
}'

Normal Response :

{
    "responseCode": "0100",
    "responseDescription": "Inquiry success",
    "errorDescription": "",
    "data": {
        "sourceAccount": "020601000255504",
        "sourceAccountName": "Jane Doe",
        "sourceAccountStatus": "Rekening Aktif",
        "sourceAccountBalance": "8631682596.05",
        "beneficiaryAccount": "020601006031306",
        "beneficiaryAccountName": "John Doe",
        "beneficiaryAccountStatus": "Rekening Aktif"
    }
}

Error Response :

{
    "responseCode": "0101",
    "responseDescription": "Inquiry failed",
    "errorDescription": "InqRekAsal: Nomor Rekening Tidak Dikenal & InqRekTujuan: 0000020601006031306",
    "data": {
        "sourceAccount": "020601023500255504",
        "beneficiaryAccount": "020601006031306"
    }
}

List of Error/Response Code

Any error response not listed in the BRIAPI response list is considered pending and requires further investigation.

Notes: Please see also the "Common Errors" page for a list of common errors in BRIAPI.

Endpoint Description

This endpoint is used to request funds transfer between two BRI accounts. However, there is a limit for total transactions and daily transactions that is set by BRI.

General Information

Header Structure

Request Structure

Response Structure

Request & Response Payload Sample

Request :

curl --location --request POST 'https://sandbox.partner.api.bri.co.id/v3.1/transfer/internal' \
--header 'BRI-Timestamp: ((TIMESTAMP))' \
--header 'BRI-Signature: ((SIGNATURE))' \
--header 'Content-Type: application/json' \
--data-raw '{
	"noReferral": "20210202126111111111",
	"sourceAccount": "020601000255504",
	"beneficiaryAccount": "020601006031306",
	"amount": "10000.00",
	"feeType": "OUR",
	"transactionDateTime": "09-03-2021 15:08:00",
	"remark": "REMARK TEST"
}'	

Normal Response :

{
	"responseCode": "0200",
	"responseDescription": "Payment Success",
	"errorDescription": "",
	"journalSeq": "8020001"
}

Error Response:

{
	"responseCode": "0299",
	"responseDescription": "Payment Failed",
	"errorDescription": "Reference number is not valid"
}

List of Error/Response Code

Any error response not listed in the BRIAPI response list is considered pending and requires further investigation.

Notes: Please see also the "Common Errors" page for a list of common errors in BRIAPI.

notes: check status service can only be executed outside of EOD (End Of Day) period. for every transfer transactions made in EOD period that resulted in timeout or pending response, account check can be done by 8 AM West Indonesian Time.

Endpoint Description

This endpoint is used to check the status of a previously made transaction. Use this if you did not receive a clear response or encountered an error, such as a timeout, during the transaction. It is important to note that the response from this endpoint does not represent the final status of the transfer process. After obtaining the "internalTransferStatus" and "internalTransferErrorMessage" in the response body, please refer to the list of error codes in the Transfer endpoint to identify whether your transaction was successful, failed, or is pending. As a more reliable alternative, partners can use the Check Bank Statement Status endpoint.

General Information

Header Structure 

Request Structure

Response Structure

Request & Response Payload Sample

Request :

curl -X POST 'https://sandbox.partner.api.bri.co.id/v3.1/transfer/internal/check' \
 -H 'Authorization: Bearer {{TOKEN}}' \ -H 'X-BRI-Signature: {{SIGNATURE}}' \ -H 'BRI-Timestamp: {{TIMESTAMP}}' \ -H 'Content-Type: application/json' \ -d '{ "noReferral": "20180212002" }'

Normal Response :

{ "responseCode":"0300", "responseDescription":"Cek Status Sukses", "errorDescription":"", "data": { "noReferral":"20210202126111111111" "journalSeq":"8020001", "internalTransferStatus":"0200", "internalTransferErrorMessage":"", } }

Error Response:

{ "responseCode":"0307", "responseDescription":"Reference number not found",
 "errorDescription":"", "data":{} }

List of Error/Response Code

notes: check status service can only be executed outside of EOD (End Of Day) period. for every transfer transactions made in EOD period that resulted in timeout or pending response, account check can be done by 8 AM West Indonesian Time.

Endpoint Description

This endpoint is used to determine the status of transfer transactions between BRI accounts previously carried out based on the results of checking the checking account. Account checking is available in 15 minutes after the transaction was made.

General Information

Header Structure 

Request Structure

Response Structure

Request & Response Payload Sample

Request :

curl --location --request POST ''\''https://sandbox.partner.api.bri.co.id/v3.1/transfer/internal/check-rekening' \
--header 'BRI-Timestamp: ((TIMESTAMP))' \
--header 'BRI-Signature: ((SIGNATURE))' \
--header 'Content-Type: application/json' \
--data-raw '{
"noReferral": "ABCD2021033112369",
"transactionDate": "01-04-2021"
}'

Normal Response :

{
"responseCode": "0300",
"responseDescription": "Status check success",
"data": {
	"noReferral": "ABCD2021033112345",
	"journalSeq": "7021301",
	"amount": "10000.00",
	"remark": "REMARK TEST BRIAPI",
	"internalTransferStatus": "0200",
	"internalTransferDescription": "Payment success"
}
}

Error Response:

{
"responseCode": "0212",
"responseDescription": "Request can not be processed",
"errorDescription": "Invalid format transaction datetime",
"data": {}
}	

List of Transfer Status

Use this parameter to determine whether the transactions made success or failure.

List of Error/Response Code

As a prerequisite for partners to be able to use the Internal Transfer API production environment, partners are required to carry out the reconciliation process using the Account Statement API or using the mt940 file provided on D+1 . How to use these reconciliation methods can be seen on the following page [Link]. 

Partners must also see common BRIAPI errors that apply to all BRIAPI products, and handle errors according to the description provided.