October 2026

Oct 30, 2026

Maybank Singapore: Accepted Purpose Codes

  • The Maybank Singapore guide now lists the 46 purpose codes Maybank accepts for FAST, PAYNOW and GIRO payments.
  • Maybank accepts only these codes. The list from The Association of Banks in Singapore (ABS) is longer.
  • A code that is on the ABS list but not on Maybank's list is rejected by Maybank. Maybank then rejects the whole payment file.
  • The FAST and GIRO notes no longer point to the ABS list.
  • The PAYNOW notes now say that purposeCode must be one of Maybank's codes.
  • Acme still checks only the format of purposeCode: letters and digits, up to 5 characters.

Affected pages:


Maker-checker: Payments Acme Prepares for You

  • Acme can make a payment from one of your accounts itself, for example a small one to verify a bank connection when it goes live. It appears in the dashboard, the API and your webhooks like any other payment.
  • A LIVE one waits for a second person at Acme to approve or reject it, and expires after 24 hours if nobody does. Your checkers cannot decide it: Approve a Payment, Reject a Payment and the dashboard refuse it.
  • Its review object names Acme in requestedBy, approvedBy and rejectedBy. A TEST one goes straight through, with no approval and no review.

Affected pages:


Oct 30, 2026

New Address for the Payment Lifecycle Guide

The Payment lifecycle and statuses guide has moved from /guides/maker-checker-payments to /guides/payment-lifecycle-and-statuses, to match its title. Old links, including links to a section such as #batch-payment-flow, open the new page. Update any saved links when you can.

Affected pages:


Oct 29, 2026

CIMB Singapore: Who Paid a Credit

Credits to CIMB Singapore accounts now show who paid them in counterparty, read from CIMB's statement files:

  • FAST credits: the payer's name, bankAccountNumber and bank (the payer bank's 8-character BIC) when CIMB's file includes them, and bankName when the BIC is in our bank directory. CIMB cuts the payer's name to 14 characters, and it is shown as CIMB sends it.
  • Foreign telegraphic transfers (TT) that CIMB books as "INW FOREIGN TT": the ordering party's name.

CIMB's statement files arrive after the credit is reported, so counterparty is added to the transaction later: usually within one to two hours on weekdays, and on the next working day for a credit after about 8:30 pm Singapore time or at a weekend. The transactions.created webhook is sent before that and has no counterparty; get the transaction again to see it. This applies to credits reported from this release on; earlier credits keep an empty counterparty for now.

counterparty stays empty when:

  • the credit is a CBPR+ transfer or a transfer between your own CIMB accounts: we cannot yet read the payer reliably from CIMB's files;
  • we cannot match the credit to a line in CIMB's statement files, for example interest credits;
  • the account does not send us CIMB statement files (MT942 and MT940).

Debits are unchanged.

Affected pages:


Oct 29, 2026

Payment Rules for Citibank Hong Kong, India and Philippines, and HSBC Hong Kong and Vietnam

New bank guides list the payment rules Acme already applies for these banks. Nothing in the API has changed.

  • New guides: Citibank Hong Kong, Citibank India, Citibank Philippines, HSBC Hong Kong (API), HSBC Hong Kong (H2H) and HSBC Vietnam.
  • Each payment type has a table of its fields, the important rules in a callout, and an example request.
  • Each guide has an ISO 20022 address section. The Citibank guides show which payment types are in scope of Citi's November 2026 CBPR+ address change, and what Acme already enforces.
  • New purpose code lists for Citibank India TT and Citibank Philippines TT and BKTR.
  • The HSBC Hong Kong (API) guide lists the FPS purpose codes, and the H2H guide links to it.
  • A new Bank Payment Rules page lists every bank and market, with its payment types and a link to its guide. Open it from the Bank payment rules heading in the sidebar.
  • Every bank guide now states its channel. The title ends with (API), (H2H) or (API and H2H).
  • A Channel note at the top of each guide says which payments go through the bank's API and which go to the bank as H2H files.
  • The OCBC Singapore guide is now titled (API and H2H), because single PAYNOW payments go through OCBC's API.
  • The DBS Singapore Receiving Party Purpose Codes now sit in the Reference folder under DBS in the sidebar.
  • The new Citibank purpose code lists sit in the Reference folder under Citibank.

Affected pages:


Oct 28, 2026

Payment Lifecycle and Statuses

The maker-checker guide is now a full guide to payment statuses. Nothing in the API has changed.

  • New diagrams show the single payment flow, the batch payment flow and the Acme maker-checker flow, and which steps happen at Acme and which at the bank. Each one links to its API reference page.
  • Each status lists where the payment is, whether it is final, and which webhook it sends.
  • Each flow shows both ways to follow a status: webhooks, or the Get a Payment and Get a Batch Payment endpoints.
  • A new section explains approval in your bank's portal: straight-through or re-authorisation.
  • Acme maker-checker has its own section. It is an optional step at Acme, where a checker API key approves payments made by a maker API key.
  • A COMPLETED batch can contain FAILED payments.
  • The batch payment flow explains how to track each payment in a batch. Only the create response lists the payments with their id. Store each id to poll a payment, or match payment webhooks to the batch by batchId.
  • The status, webhook and timeline content of the Batch Payments guide now lives on this page, and the guide links to it. The guide's examples now show batch IDs with the correct bpmt_ prefix.
  • Each bank section shows a flow of the bank's answers, labelled API or Batch file, with the final answers marked. The table under each flow shows the status for each answer.
  • A summary table shows each bank's batch acknowledgement files (ACKs) and which one is final.
  • Each bank has a table that maps its statuses to Acme's, for single payments (API) and batch payments (file). The tables show where an error or an unreadable answer from the bank marks a payment FAILED.
  • The Zand guide now shows that INITIATED maps to PROCESSING, that failed Zand payments have resultCode OTHERS, and that an error when Acme sends the payment marks it FAILED.
  • The RHB guide now shows that a posting timeout keeps the payment SUBMITTED with resultCode REQUEST_TIMEOUT.

Affected pages:


Oct 25, 2026

Bank Rate Limits on the Tracked QR Code Lookup

When UOB rate limits a lookup, Perform a direct lookup of a tracked QR code now answers 429 with a Retry-After header and errorMessage "The bank rate limited this request", as it already did for DBS. It used to answer 200 with the QR code's status unchanged, as if the bank had nothing new. Wait for the Retry-After interval and look it up again. A payment the bank receives still moves the QR code to SUCCEEDED and sends its webhook as before.

Affected pages:


Oct 23, 2026

API Reference: 400 Lists Only the Codes Each Endpoint Returns

  • Each endpoint's 400 now lists only the error codes that endpoint returns. Before, most listed the same 24 codes, including sign-in and OTP codes that the API never returns with a 400.
  • Most endpoints return INVALID_REQUEST_PARAMETER. List endpoints can also return INVALID_PAGINATION_LIMIT. Some endpoints can also return INVALID_OPERATION, when the request is valid but the action is not allowed (for example Create a Refund).
  • Create a Bank Payment File now shows paymentErrors on its 400, as Create a Batch Payment does.
  • Newly documented: the 400 of Close a Batch Payment (empty body), Approve a Payment and Delete a Virtual Account; and the cases that return a 400 with an empty body. The response bodies are unchanged.

Batch Payments: Error Responses Documented

  • Create a Batch Payment now lists the errors it returns, with what each means: 400 (with paymentErrors), 401, 403, 409, 429 and 503. The response bodies are unchanged.
  • On every endpoint, a 429 now lists only RATE_LIMIT_EXCEEDED. Before, it listed every error code of the API.
  • A badly formatted value, such as a date, now returns <field>: not a valid value instead of a general message. The general message, still used when Acme cannot read a request body for another reason, now reads "An unexpected error has occurred".
  • A saved batch is answered 200. Before, a rare failure after the batch was saved returned a 500, and a retry could create a second batch.
  • The Batch Payments guide explains each status after Acme accepts a batch. A COMPLETED batch can still contain FAILED payments.
  • The Idempotency guide says when to use a new key: after a 400, a fixed request needs one.

Affected pages:


Citibank: Structured Receiver Addresses (ISO 20022)

To meet Citibank's ISO 20022 address rules, each part of receiver.address now goes to the bank in its own field, with at most 2 address lines (line1, line2). Addresses that already fit the limits below need no change.

  • postalCode is now at most 16 characters (was 35). In Citibank Brazil, line1, line2, city and state are at most 35 each.
  • The check that the whole address fits in 3 lines of 35 characters is removed; each field is checked on its own.
  • country, when sent, must be a 2-letter ISO 3166-1 alpha-2 code (GB, not UK).
  • The guides now list each address field on its own row. Citibank Indonesia TT and ID_RTGS show city and country as mandatory, as validation already required, and Citibank Malaysia no longer lists line3, which the API does not have.

Affected pages:


Oct 21, 2026

Citibank: City and Country Required When an Address Is Sent

Citibank's ISO 20022 rules require the town and country whenever a payment carries an address. For cross-border and urgent payment types, receiver.address.city and receiver.address.country will be required when any part of receiver.address is sent. A payment with no address is unchanged.

  • Citibank Singapore MEPS and TT, Citibank Korea TT, Citibank Australia AU_HVCS and TT, and Citibank US US_WIRE_DOM and US_WIRE_INTL.
  • Citibank China CN_TT_DOM will always require receiver.address.city and receiver.address.country.

We are turning this on organization by organization and will contact you before it applies to your payments.

Affected pages:


Oct 15, 2026

Bank References for More Banks

Payments now return the bank's references for most banks and payment types. For most banks, references sent before the payment completes show on the payment while it is in progress; each bank's guide says when its references appear. The response schema has not changed.

  • bankReference is the bank's main reference for the payment. It can be null even when the bank sends other references, if none of them is the bank's main reference. An id a bank only echoes back from the payment request, such as UOB's transactionReference, is kept in bankReferences by name.
  • bankReferences has every reference the bank sent, keyed by the bank's own field names. Where a bank has a guide, its "Bank references" section lists the keys; the others are listed below.
  • A failed payment keeps the references it already showed.
  • References that arrive after a payment completed or failed are added, but never replace ones you already have. No webhook is sent, so fetch the payment to see them.
  • Banks that now return references:
    • DBS Singapore: every API payment type, and H2H.
    • Standard Chartered: every API payment type in every country, and H2H in Singapore, Great Britain and India (the same keys as Singapore H2H).
    • UOB Singapore and Malaysia: API, and the Malaysia DuitNow result file.
    • OCBC: Singapore and Malaysia API (BankReferenceNo is the main reference; Malaysia also keeps BizMsgID), and Singapore H2H.
    • CIMB Singapore: FAST and TT (API), CIMB's JournalId for BKTR, and H2H.
    • Citi: H2H in every country, and the API.
    • HSBC H2H (Singapore, Malaysia, Hong Kong, Vietnam; the same keys as the Singapore guide) and HSBC Malaysia API, ANZ Australia, and Deutsche Bank Singapore when its status files carry them.
    • Banco Azteca Mexico.
    • Airwallex: id is the main reference, with short_reference_id, request_id and external_reference (from dispatch_info).
    • Banking Circle: paymentId is the main reference, with transactionReference.
  • RHB Malaysia already returned bankReference. Its guide now names the keys.
  • Payments completed before this change are not updated.

Affected pages:


Oct 15, 2026

Lower POST Burst Limit

The burst allowance for POST requests is now 30 requests per API key, down from 100, in both LIVE and TEST modes. The sustained rate is unchanged at 25 requests per second, and GET limits are unchanged.

  • Once a key's burst is used up, POST requests sent faster than 25 per second get HTTP 429 RATE_LIMIT_EXCEEDED with a Retry-After header. Wait for the time it gives before retrying.
  • To send a large batch, spread the requests at or below the sustained rate instead of sending them all at once.

Affected pages:


Oct 14, 2026

UAE Cut-offs, Limits, POP Codes and Bank Codes

The Standard Chartered UAE payment rules now cover cut-off times, processing times, amount guidance and the Purpose of Payment codes. A new page lists the UAE bank codes Acme uses to find a bank's BIC from a UAE IBAN. No API behavior changes.

  • A new summary table lists the SCB rail, currency, cut-off, processing time and amount guidance for UAE_IBFT, UAE_FTS, TT and BKTR.
  • UAE_IBFT is available 24/7. SCB recommends it for amounts below AED 50,000.
  • UAE_FTS has an 18:30 UAE time cut-off, Monday to Friday. A payment after the cut-off is processed the next working day.
  • TT has a 20:30 UAE time cut-off every day.
  • BKTR in the same currency is available 24/7. A transfer between currencies has an 18:00 UAE time cut-off.
  • The full list of Purpose of Payment (POP) codes, also called FTS codes, is published. It marks which codes UAE_IBFT accepts.
  • Each payment type now has an example payload.
  • A new UAE Bank Codes page lists the bank code in each UAE IBAN with its BIC. It also says when you need to send receiver.bank.

Affected pages:


Oct 10, 2026

Webhook Examples Updated

The webhook examples now match what Acme sends, and each set sits in the API reference next to the endpoints it relates to. No webhook behavior changes.

  • The examples are split into five pages, one per API reference group. Acme webhook examples links to each one.
  • Each example shows the fields Acme sends for that case, in the order it sends them. The notes under an example list the fields that are sent only in some cases.
  • Fields that are left out when they have no value are no longer shown as null.
  • Timestamps have the number of decimal places Acme sends. Most object timestamps have 3, and a few have up to 9.
  • Transactions, payments, hosted payments, direct debits and virtual accounts have a tab for each country, bank or payment method where the body differs.
  • Most events now have a failed example, with the result codes Acme sends.
  • The payments.approved example now shows the payment after Acme submitted it to the bank. Its status is usually PROCESSING.
  • The direct debit payment batch examples now show type GIRO or FAST, and no metadata.

Affected pages:


Oct 9, 2026

Batch Direct Debit customerReference Per Bank

The reference for creating a batch direct debit collection now says how each bank uses customerReference. No API behavior changes.

  • Use a different customerReference for each payment in the batch.
  • UOB prints customerReference on your payer's bank statement.
  • DBS rejects a payment whose reference is not unique, if you subscribe to DBS's customer reference uniqueness check.
  • DBS does not publish how far back it checks.

Affected pages:


Oct 8, 2026

Batch Direct Debit Field Rules Documented

The reference for creating a batch direct debit collection now lists the length and allowed characters of each field. No API behavior changes.

  • customerReference is required. It allows up to 20 characters from the SWIFT character set.
  • Every field in directDebitAuthorizationInformation is required.
  • billReferenceNumber allows 1 to 35 characters from the SWIFT character set.
  • payerName allows up to 35 characters.
  • payerBankAccountNumber allows up to 34 letters and digits, with no dashes or spaces.
  • payerSwiftBic allows up to 11 characters.

Affected pages:


Where CIMB Singapore Shows Payment References

The CIMB Singapore (API) guide now says where each reference goes. Payment behavior has not changed.

  • FAST: CIMB returns customerReference as the end-to-end reference on the account statement and in account notifications. paymentDetails is sent as the payment reference. If it is not provided, Acme sends customerReference instead.
  • BKTR: CIMB shows customerReference as the Remarks on the account statement. paymentDetails is kept with the payment, and CIMB does not receive it. The example payload no longer includes it.
  • TT: paymentDetails is sent as up to 4 lines of 35 characters.

Affected pages:


Oct 6, 2026

RHB Malaysia paymentDetails Limited to 20 Characters

MY_IBG and MY_IBFT payments from an RHB account are now rejected on create when paymentDetails is longer than 20 characters. The limit was 140, and RHB rejected MY_IBG payments with longer details after they were sent.

Affected pages:

On this page