Acme RHB Bank Malaysia Payments (API)

This describes validations / allowed data formats for Acme payments going through RHB Bank Malaysia. These will be validated by Acme and further validated by the bank. These rules may be stricter than what the bank requires.

Common DefinitionsCopy Anchor Link

• SWIFT Character Set:

  • The 26 uppercase Latin letters A-Z
  • The 26 lowercase Latin letters a-z
  • The 10 digits 0-9
  • Forward slash /
  • Hyphen -
  • Question mark ?
  • Colon :
  • Left and right parentheses ( )
  • Full stop .
  • Comma ,
  • Single quote '
  • Plus sign +
  • Space

• BIC11:

  • 11-character Bank Identifier Code

General notesCopy Anchor Link

• The format for BIC (used in receiver.bank) is strictly validated using [A-Z]{6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3})? (as specified in ISO20022 BICFIIdentifier).
• RHB support both Pre-authorization (STP) flow and authorization flow via RHB Reflex, the configuration is done on RHB's backend.

MY_IBGCopy Anchor Link

Malaysia Interbank GIRO — next-day settlement.

Example Request:

{
  "type": "MY_IBG",
  "amount": 1000,
  "currency": "MYR",
  "senderAccountId": "intacc_0H3BQNTQGBW2W",
  "customerReference": "INV-001",
  "paymentDetails": "Payment for INV-001",
  "paymentAdviceEmails": ["finance@example.com"],
  "receiver": {
    "name": "Ahmad bin Ali",
    "bank": "PBBEMYKLXXX",
    "bankAccountNumber": "1234567890",
    "residencyStatus": "RESIDENT"
  }
}

MY_IBFTCopy Anchor Link

Malaysia Instant Fund Transfer via DuitNow Bank Account Transfer.

Example Request:

{
  "type": "MY_IBFT",
  "amount": 1000,
  "currency": "MYR",
  "senderAccountId": "intacc_0H3BQNTQGBW2W",
  "customerReference": "INV-001",
  "paymentDetails": "Payment for INV-001",
  "paymentAdviceEmails": ["finance@example.com"],
  "receiver": {
    "name": "Ahmad bin Ali",
    "bank": "PBBEMYKLXXX",
    "bankAccountNumber": "1234567890",
    "residencyStatus": "RESIDENT",
    "accountType": "SAVINGS"
  }
}

Payment ResponseCopy Anchor Link

• RHB returns a reference Id upon payment created successfully, this is returned in the bankReference field.
• The underlyingErrorMessage field should contains payment status code and error message returned by RHB (if any).

Example of underlyingErrorMessage from RHB:

"underlyingErrorMessage" : "N3: Invalid Account Number"

Payment status definition:

Possible result Code for failed payments:

Example response:

{
  "id": "pymt_0Q0T6K4DZFRZT",
  "type": "MY_IBFT",
  "amount": 100,
  "currency": "MYR",
  "bankReference": "260408894262",
  "customerReference": "ACMELVIBG02",
  "senderAccountId": "intacc_0H3BQNTQGBW2W",
  "receiver": {
    "name": "John Doe",
    "bank": "PBBEMYKLXXX",
    "bankAccountNumber": "1234567890",
    "address": {},
    "residencyStatus": "RESIDENT",
    "accountType": "SAVINGS"
  },
  "paymentDetails": null,
  "currencyExchange": {
    "fxContractId": null
  },
  "senderAccountCurrency": "MYR",
  "status": "COMPLETED",
  "resultCode": null,
  "paymentAdviceEmails": ["finance@example.com"],
  "createdAt": "2026-04-08T05:12:14.447Z",
  "updatedAt": "2026-04-08T05:12:14.936Z"
}

Bank referencesCopy Anchor Link

bankReference is RHB's reference for the payment, its ref_no. It's set when RHB accepts or completes the payment, and bankReferences has it under the key refNo.

Other keys in bankReferences:

• pymtType: RHB's payment type code, from RHB's answer to the request, such as 200218. It isn't a reference.

Good to know:

• A payment that RHB rejects after accepting it keeps refNo.
• Until RHB sends ref_no, bankReference is null and bankReferences has at most pymtType.

A completed payment returns:

{
  "bankReference": "260408894262",
  "bankReferences": {
    "refNo": "260408894262",
    "pymtType": "200218"
  }
}