Brick API Documentation
Brick API

Bank Account Validation

Server

Verify Indonesian bank account details before storing beneficiaries or initiating payouts. Account validation reduces failed transfers, mistyped account numbers, and operational reconciliation issues.

Client Reference

clientReference is an optional query parameter that lets your system send a custom unique reference for each Bank Account Validation request. Use it to simplify tracking, transaction matching, and reconciliation against your own internal reference.

Supported values: letters, numbers, hyphen (-), underscore (_), and period (.), up to 64 characters. An empty clientReference is treated the same as not providing the parameter. If the same client sends a duplicate clientReference, Brick returns 409 duplicate_reference.

Request without clientReference

Code
GET https://api.onebrick.io/v2/payments/gs/bank-account-validation?accountNumber=<ACCOUNT_NUMBER>&bankShortCode=BCA_SYR Headers: Accept: application/json Content-Type: application/json publicAccessToken: Bearer <token>

Response without clientReference

JSONCode
{ "status": 200, "data": { "message": "Bank account validation has been completed successfully, and the submitted account details have been verified.", "bankShortCode": "BCA_SYR", "accountNo": "<ACCOUNT_NUMBER>", "accountName": "<ACCOUNT_NAME>", "activityId": "7b63f490900376f0f60aab63afde17d5" }, "error": null, "metaData": { "source": "API", "entity": "Payment" } }

Request with clientReference

Code
GET https://api.onebrick.io/v2/payments/gs/bank-account-validation?accountNumber=<ACCOUNT_NUMBER>&bankShortCode=BCA_SYR&clientReference=BAV_TEST-001 Headers: Accept: application/json Content-Type: application/json publicAccessToken: Bearer <token>

Response with clientReference

JSONCode
{ "status": 200, "data": { "message": "Bank account validation has been completed successfully, and the submitted account details have been verified.", "bankShortCode": "BCA_SYR", "accountNo": "<ACCOUNT_NUMBER>", "accountName": "<ACCOUNT_NAME>", "activityId": "a7014608c43969d890ea0fbf1cfc493e", "clientReference": "BAV_TEST-001" }, "error": null, "metaData": { "source": "API", "entity": "Payment" } }

Duplicate clientReference response

JSONCode
{ "status": 409, "data": null, "error": { "code": "duplicate_reference", "message": "clientReference has already been used.", "action": "Please use a unique clientReference for each Bank Account Validation request.", "reason": "The provided clientReference already exists." }, "metaData": { "source": "API", "entity": "Payment" } }

Account Verification API

GET
https://sandbox.onebrick.io
/v2/payments/gs/bank-account-validation
publicAccessToken (header)

Verify bank account details before saving a beneficiary, onboarding a user, or initiating a payout. Use this endpoint as a Financial Insight or risk-control check to reduce typo-related failures and suspicious account usage. The response helps your system decide whether account data is valid enough to continue the workflow.

Account Verification API › query Parameters

accountNumber
​string · required

The bank account number to be verified.

Default:
bankShortCode
​string · required

The bank short code to validate. Collection example: MANDIRI.

Default:
clientReference
​string · maxLength: 64 · pattern: ^[A-Za-z0-9._-]*$

Optional unique reference supplied by your client system for tracking, transaction matching, and reconciliation. Use up to 64 characters: letters, numbers, hyphen (-), underscore (_), or period (.). Leave it empty or omit it when you do not want to send a client reference.

Default:

Account Verification API › Responses

200 Success

oneOf
Exactly one variant must match.

Decision Table

VariantMatching Criteria
type = object
type = object
Properties for Success:
status
​integer
​object
error
​
​object