Skip to main content
POST
Add a bank account
60 requests per API key per 5 minutes. A trailing .json suffix counts toward the same limit. See Rate limits.
bank_code must be one of the codes on Supported banks, which also lists the account-number length each bank expects.

Verification

A successful registration does not mean the account can receive payouts yet. Every account is verified with the bank first, and status reports where that verification stands: Verification can finish before this call returns, so the response may already report verified, rejected or reviewing, including the bank-verified name. While the account is still received or pending, wait for a bank_account_status webhook or poll Retrieve a bank account instead of treating it as ready. The event payload is the bank-account object itself — see Event Types and Payloads. For that reason the first webhook can report a status other than received.

Rejected accounts

When status is rejected, rejection_reason carries a plain-language reason (for example Invalid crediting account.) and the account cannot be used to create a send instruction. For every other status, rejection_reason is null. Correct the account details before registering again. Registering the same account_number and bank_code within an hour returns the same rejected account; after that it can be registered again, but if nothing about the account has changed, expect the same result. When the account number or the bank was wrong, register the corrected details. To exercise this path on staging, register an account number ending in 0000 — see Simulating a rejected bank account.

Reviewed manually

reviewing means CHIP is checking the account manually. It cannot be used for send instructions until it is verified. Reviews are typically completed within 2 working days; contact CHIP support if it takes longer.

Holder name after verification

Until the account is verified, name is the name you submitted (uppercased). Once status is verified, name is the account holder name the bank returned, which is not necessarily the name that was submitted — treat it as the bank-verified holder name and show it to your user for confirmation before paying. Use reference for your own label or identifier: CHIP never replaces it with bank data, whereas name is replaced by the bank-verified value. You can change reference by registering the same account again. Re-registering an account that is already verified does not change the stored name.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Headers

epoch
integer<int64>
required

Unix epoch timestamp Unix timestamp (seconds).

Example:

1619740800

checksum
string
required

Refer to checksum calculation

Body

application/json

Request body for registering a recipient bank account.

account_number
string
required

The number of digits depends on the recipient bank — some banks use a fixed length, others accept a range. See the per-bank list on Supported banks.

Required string length: 5 - 17
Example:

"157380112222"

bank_code
enum<string>
required

Malaysian bank identifier in BIC/SWIFT form. This is the complete set of codes accepted by POST /send/bank_accounts.

This is not the FPX bank code used for CHIP Collect FPX checkouts (MB2U0227, ABB0233, PBB0233, …). The two lists identify banks on different networks and are not interchangeable.

  • ACDBMYK2: AEON Bank (M) Berhad
  • PHBMMYKL: Affin Bank Berhad
  • AGOBMYKL: Agrobank
  • RJHIMYKL: Al Rajhi Bank
  • MFBBMYKL: Alliance Bank Malaysia Berhad
  • ARBKMYKL: AmBank Malaysia Berhad
  • BIMBMYKL: Bank Islam Malaysia Berhad
  • BKRMMYKL: Bank Kerjasama Rakyat Malaysia Berhad
  • BMMBMYKL: Bank Muamalat Malaysia Berhad
  • BOFAMY2X: Bank of America (M) Berhad
  • BKCHMYKL: Bank of China (M) Berhad
  • BOTKMYKX: MUFG Bank (Malaysia) Berhad
  • BSNAMYK1: Bank Simpanan Nasional Berhad
  • BNPAMYKL: BNP Paribas Malaysia Berhad
  • BOBEMYK2: BOOST Bank Berhad
  • PCBCMYKL: China Construction Bank (M) Berhad
  • CIBBMYKL: CIMB Bank Berhad
  • CITIMYKL: Citibank Berhad
  • DEUTMYKL: Deutsche Bank (Malaysia) Berhad
  • FNXSMYNB: Finexus Cards Sdn. Bhd.
  • GXSPMYKL: GX Bank Berhad
  • HLBBMYKL: Hong Leong Bank Berhad
  • HBMBMYKL: HSBC Bank Malaysia Berhad
  • ICBKMYKL: Industrial and Commercial Bank of China (M) Berhad
  • CHASMYKX: JP Morgan Chase Bank Berhad
  • KFHOMYKL: Kuwait Finance House
  • MBBEMYKL: Maybank Berhad
  • AFBQMYKL: MBSB Bank Berhad
  • MHCBMYKA: Mizuho Bank (Malaysia) Berhad
  • OCBCMYKL: OCBC Bank Berhad
  • PBBEMYKL: Public Bank Berhad
  • RHBBMYKL: RHB Bank Berhad
  • SCCHMYKL: RYT Bank
  • SCBLMYKX: Standard Chartered Bank Malaysia Berhad
  • SMBCMYKL: Sumitomo Mitsui Banking Corporation (M) Berhad
  • TNGDMYNB: TNG Digital (Touch 'n Go eWallet)
  • UOVBMYKL: United Overseas Bank Berhad (UOB)
Available options:
ACDBMYK2,
PHBMMYKL,
AGOBMYKL,
RJHIMYKL,
MFBBMYKL,
ARBKMYKL,
BIMBMYKL,
BKRMMYKL,
BMMBMYKL,
BOFAMY2X,
BKCHMYKL,
BOTKMYKX,
BSNAMYK1,
BNPAMYKL,
BOBEMYK2,
PCBCMYKL,
CIBBMYKL,
CITIMYKL,
DEUTMYKL,
FNXSMYNB,
GXSPMYKL,
HLBBMYKL,
HBMBMYKL,
ICBKMYKL,
CHASMYKX,
KFHOMYKL,
MBBEMYKL,
AFBQMYKL,
MHCBMYKA,
OCBCMYKL,
PBBEMYKL,
RHBBMYKL,
SCCHMYKL,
SCBLMYKX,
SMBCMYKL,
TNGDMYNB,
UOVBMYKL
Example:

"MBBEMYKL"

name
string
required

The account holder name as you understand it. It is provisional: once verification succeeds, responses return the bank-verified holder name instead, which may differ from the value sent here.

Required string length: 1 - 65535
Example:

"Ahmad Razali"

reference
string

Unique value used to prevent duplicate submissions.

Required string length: 1 - 65535
Example:

"VENDOR-EMP-001"

Response

Successful response

A recipient bank account registered for payouts.

account_number
string
required

The number of digits depends on the recipient bank — some banks use a fixed length, others accept a range. See the per-bank list on Supported banks.

Required string length: 5 - 17
Example:

"157380112222"

bank_code
enum<string>
required

Malaysian bank identifier in BIC/SWIFT form. This is the complete set of codes accepted by POST /send/bank_accounts.

This is not the FPX bank code used for CHIP Collect FPX checkouts (MB2U0227, ABB0233, PBB0233, …). The two lists identify banks on different networks and are not interchangeable.

  • ACDBMYK2: AEON Bank (M) Berhad
  • PHBMMYKL: Affin Bank Berhad
  • AGOBMYKL: Agrobank
  • RJHIMYKL: Al Rajhi Bank
  • MFBBMYKL: Alliance Bank Malaysia Berhad
  • ARBKMYKL: AmBank Malaysia Berhad
  • BIMBMYKL: Bank Islam Malaysia Berhad
  • BKRMMYKL: Bank Kerjasama Rakyat Malaysia Berhad
  • BMMBMYKL: Bank Muamalat Malaysia Berhad
  • BOFAMY2X: Bank of America (M) Berhad
  • BKCHMYKL: Bank of China (M) Berhad
  • BOTKMYKX: MUFG Bank (Malaysia) Berhad
  • BSNAMYK1: Bank Simpanan Nasional Berhad
  • BNPAMYKL: BNP Paribas Malaysia Berhad
  • BOBEMYK2: BOOST Bank Berhad
  • PCBCMYKL: China Construction Bank (M) Berhad
  • CIBBMYKL: CIMB Bank Berhad
  • CITIMYKL: Citibank Berhad
  • DEUTMYKL: Deutsche Bank (Malaysia) Berhad
  • FNXSMYNB: Finexus Cards Sdn. Bhd.
  • GXSPMYKL: GX Bank Berhad
  • HLBBMYKL: Hong Leong Bank Berhad
  • HBMBMYKL: HSBC Bank Malaysia Berhad
  • ICBKMYKL: Industrial and Commercial Bank of China (M) Berhad
  • CHASMYKX: JP Morgan Chase Bank Berhad
  • KFHOMYKL: Kuwait Finance House
  • MBBEMYKL: Maybank Berhad
  • AFBQMYKL: MBSB Bank Berhad
  • MHCBMYKA: Mizuho Bank (Malaysia) Berhad
  • OCBCMYKL: OCBC Bank Berhad
  • PBBEMYKL: Public Bank Berhad
  • RHBBMYKL: RHB Bank Berhad
  • SCCHMYKL: RYT Bank
  • SCBLMYKX: Standard Chartered Bank Malaysia Berhad
  • SMBCMYKL: Sumitomo Mitsui Banking Corporation (M) Berhad
  • TNGDMYNB: TNG Digital (Touch 'n Go eWallet)
  • UOVBMYKL: United Overseas Bank Berhad (UOB)
Available options:
ACDBMYK2,
PHBMMYKL,
AGOBMYKL,
RJHIMYKL,
MFBBMYKL,
ARBKMYKL,
BIMBMYKL,
BKRMMYKL,
BMMBMYKL,
BOFAMY2X,
BKCHMYKL,
BOTKMYKX,
BSNAMYK1,
BNPAMYKL,
BOBEMYK2,
PCBCMYKL,
CIBBMYKL,
CITIMYKL,
DEUTMYKL,
FNXSMYNB,
GXSPMYKL,
HLBBMYKL,
HBMBMYKL,
ICBKMYKL,
CHASMYKX,
KFHOMYKL,
MBBEMYKL,
AFBQMYKL,
MHCBMYKA,
OCBCMYKL,
PBBEMYKL,
RHBBMYKL,
SCCHMYKL,
SCBLMYKX,
SMBCMYKL,
TNGDMYNB,
UOVBMYKL
Example:

"MBBEMYKL"

name
string
required

The account holder name, in uppercase.

Until the account is verified this is the name submitted at registration. Once status is verified it is the name the bank returned, which may differ from the name that was sent. Show it to your user for confirmation before paying, and keep your own label or identifier in reference.

Registering an account that is already verified again does not change this value.

Required string length: 1 - 65535
Example:

"Ahmad Razali"

id
integer<int64>
read-only

The ID returned in the response must be stored, as it will be required for subsequent operations.

Example:

1

status
enum<string>
  • received: The bank account has been created and verification has not started yet.
  • pending: Verification of the bank account with the bank is in progress.
  • verified: The bank has confirmed the bank account, so it can be used for send instructions.
  • rejected: The bank refused to confirm the bank account, so it cannot be used for send instructions; rejection_reason explains why.
  • reviewing: CHIP is reviewing the bank account manually; it cannot be used for send instructions until it is verified.

received and pending are not final: wait for a bank_account_status webhook or retrieve the bank account again.

A reviewing account is typically reviewed within 2 working days; contact CHIP support if it takes longer.

A rejected account can be registered again once the rejection is more than one hour old. If nothing about the account has changed, expect the same result, so correct the account details first.

Available options:
received,
pending,
verified,
rejected,
reviewing
Example:

"verified"

group_id
integer<int64> | null
Example:

null

reference
string

Your own label or identifier for the bank account. CHIP never replaces it with bank data.

Use this instead of name when you need a value that survives verification: name is replaced by the bank-verified holder name once verification succeeds. You can change reference by registering the same account again.

Required string length: 1 - 65535
Example:

"VENDOR-EMP-001"

created_at
string<date-time>
read-only

Object creation time in UTC.

is_debiting_account
boolean
read-only
Example:

false

is_crediting_account
boolean
read-only
Example:

false

updated_at
string<date-time>
read-only

Object updated time in UTC.

deleted_at
string<date-time>
read-only

Object deletion time in UTC.

rejection_reason
string | null
read-only

A plain-language reason why the bank account was rejected.

Populated only when status is rejected; null for every other status. It describes the problem the bank reported, so correct the account details (or the bank-side problem) before registering the account again.

Maximum string length: 65535
Example:

"Invalid crediting account."