Skip to main content

Changelog

Jun 24, 2026​

New Bank & Payment Types Supported​

Added support for Standard Chartered Bank single payments with the following payment types:

SCB SG:

  • FAST (Fast and Secure Transfers) — real-time interbank fund transfer (IBFT) via the FAST network
  • MEPS (MAS Electronic Payment System) — high-value SGD interbank transfers
  • BKTR (Intra-Account Funds Transfer) — book transfer between accounts within SCB Singapore.
  • TT (Telegraphic Transfer) — cross-border international SWIFT transfer.

SCB GB:

  • GB_FPS (Faster Payment System) - real-time interbank fund transfer (IBFT) via the FPS network
  • GB_CHAPS (Real Time Gross Settlement) - same-day high-value local bank transfer via the Real Time Gross Settlement system
  • GB_SEPA (Single Euro Payments Area)- Payyments between SEPA countries. ACH(SEPA) payment is an electronic fund transfer to the payee’s account for low-value and bulk volume.
  • BKTR (Intra-Account Funds Transfer) — book transfer between accounts within SCB GB.
  • TT (Telegraphic Transfer) — cross-border international SWIFT transfer.

Jun 16, 2026​

Enhancement: DBS Singapore API Updates​

The DBS Singapore Payment API now forwards bank charge instructions to DBS for MEPS and TT APIs.​

  • bankChargeBearer accepts SENDER, RECEIVER, or SHARED and is now forwarded to DBS. Previously it was accepted but not sent, so DBS applied its default.
  • New optional chargeAccount field sets the account DBS debits for the bank charges. When omitted, DBS debits the originating account.

The DBS Singapore Payment API now accepts an optional paymentDetails field.​

  • For ACT, MEPS, and TT, paymentDetails is sent to the beneficiary bank. It is also included in the email advice when an advice email is provided.
  • For FAST and PAYNOW, paymentDetails is not sent to the beneficiary bank. It is included in the email advice only when an advice email is provided.

We corrected and clarified the DBS Singapore API payment rules to match Acme's validation. The validation behavior is unchanged. These updates correct the documentation.​

  • FAST/PAYNOW receiver.name charset is G_I3 up to 140 characters. It was previously stated as SWIFT.
  • ACT receiver.name charset on the V4 API is SWIFT up to 35 characters. It was previously stated as G_I3.
  • We noted that receiver.name for FAST, PAYNOW, and the V4 tables is validated by DBS, not by Acme upfront.

Enhancement: DBS Singapore H2H Updates​

The DBS Singapore H2H advice email and DBS IDEAL display now source the Invoice Details field from paymentDetails.​

  • paymentDetails now populates the Invoice Details field in the advice email.
  • customerReference now populates the Client Reference field in the advice email.
  • If paymentDetails is not provided, Acme uses customerReference as the Invoice Details so the field is never empty.
  • This applies to all H2H payment types when advice emails are provided in paymentAdviceEmails for the payment.

We corrected the existing DBS Singapore H2H payment rules to match Acme's validation. This is a documentation change only and does not change behavior.​

  • receiver.address is a structured object with the fields line1, line2, city, state, postalCode, and country. Acme flattens these into 3 lines of up to 35 SWIFT characters before submission.
  • The address packing applies to every existing payment type that accepts an address (FAST, PAYNOW, PAYNOW_GIRO, GIRO, MEPS, TT).
  • line1 is mandatory only for MEPS and TT. It is optional for the other types.
  • The MEPS and TT tables previously inaccurately documented the address as a single mandatory line1 of 35 characters.
  • receiver.bankAccountNumber is alphanumeric for FAST, GIRO, and ACT. It allows alphanumeric plus the hyphen character for MEPS and TT. It was previously stated as numeric.
  • We documented the existing optional fields receiver.intermediaryBank (MEPS, TT) and receiver.localRoutingIdentifier (TT).

Jun 11, 2026​

Enhancement: Zand Bank UAE — Improved Transaction Types Categorization​

  • Improved transactionType categorization in Transactions API for Zand Bank UAE transactions, aligned with the Zand payment types.
  • Removed domestic transactions with inaccurate transactionType : ACH, RTP.

Jun 5, 2026​

Upcoming Change: DBS Singapore — SWIFT ISO 20022 CBPR+ and HVPS+ migration (API and H2H)​

As part of Acme's migration across all banking partners to comply with ISO 20022 CBPR+ and HVPS+ requirements ahead of the SWIFT November 2026 deadline, the DBS Singapore payment rules will change across both the API and H2H integrations.

Acme will be migrating to the new DBS endpoints and file format once clients are ready. In the meantime, clients should start updating their integrations now — particularly to populate the newly required fields and sanitize values that fall outside the new character sets — so that payments continue to be accepted after the cutover.

Summary of change:​

DBS Singapore H2H (MEPS, TT, ACT):

  • receiver.name max length increased from 35 → 140 across MEPS, TT, and ACT.
  • MEPS and TT: receiver.address.city and receiver.address.country are now required. receiver.address.line1 and line2 max length increases to 70; state and postalCode remain optional.
  • New outgoingPurposeCode field for TT — mandatory when the payment currency is MYR, CNH/CNY, INR, or KWD, or when the beneficiary country is Myanmar (MM) or United Arab Emirates (AE). Partners should obtain the applicable purpose code list from DBS or refer to the destination country's regulator.

DBS Singapore API (ACT):

  • receiver.name max length increased from 35 → 140.
  • Breaking change: receiver.name charset is restricted from G_I3 → SWIFT. Existing payee names containing characters outside the SWIFT character set (e.g. !, #, $, %, &, *, ;, =, @, [, ], ^, _, `, {, }, |, ~) will be rejected. Clients must sanitize stored payee names before migrating.

May 28, 2026​

New Feature: Payer name updates for MY FPX Hosted Payments​

  • Hosted Payments for FPX Malaysia now support a fullName field on the request payer object, as an alternative to firstName and lastName. This is useful for customers whose names are not easily split into given and family names (e.g. Malay or single-name customers).

  • The two formats are mutually exclusive — fullName must not be combined with firstName or lastName. When fullName is provided in the request, it is echoed back in the Hosted Payment response, and firstName/lastName are null (and vice versa).

  • The Hosted Payment response payer object now also includes:

    • returnedName — bank-confirmed payer name returned after payment completes. May differ from the name submitted in the request.
    • payerBank — FPX bank name used by the customer to complete payment (e.g. "Malayan Banking Berhad (M2U)").

May 25, 2026​

New Bank & Payment Types Supported​

Added support for UOB Malaysia batch payments with the following payment types:

  • TT (Telegraphic Transfer) — cross-border international SWIFT transfer.
  • MY_RENTAS (Real-time Electronic Transfer of Funds and Securities) — high-value MYR domestic transfer.
  • MY_IBG (Interbank GIRO) — low-value MYR interbank fund transfers.
  • MY_IAFT (Intra-Account Funds Transfer) — book transfer between accounts within UOB Malaysia.
  • MY_DUITNOW — MYR proxy-based payments via NRIC, Passport, Mobile, Business Registration, or Army number.
  • MY_IBFT (Interbank Funds Transfer) — MYR interbank fund transfers via bank account.

UOB Singapore and Malaysia payment rules are now grouped under a dedicated UOB category in the Payment Rules navigation.

New reference page:​

May 22, 2026​

New Bank & Payment Types Supported​

Added support for Zand Bank UAE single payment with the following payment types:

  • BKTR (Book Transfer) — intra-Zand same-bank transfer between two Zand accounts.
  • UAE_FTS (UAE Interbank Fund Transfer Service) — high-value domestic interbank transfer (> 50,000 AED).
  • UAE_IBFT (UAE Interbank Immediate Payment Instruction) — low-value domestic interbank transfer (≤ 50,000 AED).
  • TT (Telegraphic Transfer) — cross-border international SWIFT transfer.

New reference page:​

Apr 28, 2026​

New Bank & Payment Types Supported​

Added support for CIMB Singapore H2H batch payments with the following payment types:

  • FAST (Fast and Secure Transfers) — real-time interbank fund transfer via the FAST network
  • GIRO (General Interbank Recurring Order) — low-value interbank fund transfers
  • MEPS (MAS Electronic Payment System) — high-value SGD interbank transfers
  • TT (Telegraphic Transfer) — cross-border wire transfers in any ISO currency
  • BKTR (Book Transfer) — internal fund transfers between accounts within the same bank

New reference page:​

Apr 21, 2026​

1. New Bank & Payment Types Supported​

Added support for RHB Malaysia single payment with the following payment types:

  • MY_IBG (Interbank GIRO) — low-value interbank fund transfer system in Malaysia, operated by PayNet.
  • MY_IBFT (Intrabank Fund Transfer) — real-time interbank fund transfer (IBFT) via bank account transfer.

New reference page:​

2. Updated DBS SG API and H2H Payment rules​

Apr 10, 2026​

New Bank & Payment Types Supported​

Added support for CIMB Singapore single payment with the following payment types:

  • BKTR (Book Transfer) — instant fund transfers between accounts within the same bank (CIBBSGSGXXX)
  • FAST (Fast and Secure Transfers) — real-time interbank fund transfer (IBFT) via the FAST network

New reference page:​

March 25, 2026​

New Feature: Maker-Checker flow for Payments​

We've published documentation for the Maker-Checker Payment Flow (Beta), introducing a two-step approval flow for payment processing.

New endpoints:​

New reference page:​