November 2026

Nov 18, 2026

DBS Singapore: FAST and PayNow Single Payments in Test Mode

Test FAST and PAYNOW payments from a DBS Singapore account now run against a simulated DBS, which answers as DBS does. ACT, TT and MEPS test payments are unchanged.

  • Any other number, and a PayNow payment by proxy: the response is now COMPLETED, as DBS confirms a payment in its answer, and Acme sends payments.succeeded. Before, the response was SUBMITTED, followed by payments.succeeded.
  • 000000000: the response is FAILED, as before, and its resultCode is now OTHERS.
  • 000000001: the response is SUBMITTED, as before, and the payment is now FAILED at DBS's first status check, within about 10 minutes, instead of at once.
  • New values for what DBS answers later: 000000003 (FAILED after SUBMITTED), 000000004 (COMPLETED after SUBMITTED), 000000005 (FAILED after SUBMITTED), 000000006 and 000000007 (stay SUBMITTED).
  • New value 000000008: DBS rate limits the payment, and the request is answered 429 RATE_LIMIT_EXCEEDED. On UOB Singapore, 000000008 is FAILED, as UOB refuses a rate-limited payment.

Affected pages:

UOB Singapore: Customer Reference Checked Before the Payment Is Created

On a single FAST or PAYNOW payment from a UOB Singapore account, customerReference must now be at most 19 characters, using letters, digits, spaces and ‘ ' - ? / : ; . ( ). These are UOB's limits for its payment API. Before, Acme accepted a longer reference, or one with a character such as + or ,, and the payment then became FAILED when UOB refused it. Now Create a Payment answers 400 with a field error on customerReference, and no payment is created. This applies in test mode too.

Batch payments, which go to UOB as files, keep their limits.

Affected pages:


Nov 17, 2026

UOB Singapore: Single Payments in Test Mode

Test payments from a UOB Singapore account now run against a simulated UOB, which answers as UOB does. Before, every test payment from a UOB Singapore account was FAILED, with no webhook.

  • 000000000 and 000000001: the response is FAILED, and Acme sends payments.failed.
  • Any other number: the payment is COMPLETED, and Acme sends payments.succeeded.
  • New values for what UOB answers later: 000000003 (FAILED after SUBMITTED), 000000004 (COMPLETED after SUBMITTED), 000000005 (FAILED after SUBMITTED), 000000006 (stays SUBMITTED) and 000000007 (FAILED after 2 to 4 hours).
  • A customerReference longer than 19 characters is FAILED, as UOB refuses it in live mode.
  • A failed payment's resultCode is OTHERS.

Affected pages:


Webhooks: Which Events You Receive

The webhooks guide now says which events reach your endpoint. Nothing changed in the API or in how Acme sends webhooks.

  • Webhooks are set up for your organization and mode, not for an API key.
  • Each endpoint receives every event in your organization for its mode, whatever created the object.
  • An API key's permissions limit the API calls it can make, not the webhooks you receive.
  • To act on only some events, filter on the event field and respond with HTTP 200 to the rest.

Affected pages:


Nov 10, 2026

HSBC Malaysia, Singapore and Vietnam: Receiver City and Country on High-Value Payments

HSBC's ISO 20022 (CBPR+) rules require the receiver's city and country on high-value payments. Acme will require them on these payment types:

  • HSBC Malaysia MY_RENTAS and TT: receiver.address.city and receiver.address.country.
  • HSBC Singapore MEPS and TT: receiver.address.city and receiver.address.country.
  • HSBC Vietnam VN_RTGS and TT: receiver.address.city. TT already requires receiver.address.country, and Acme always sends VN for VN_RTGS. A tax payment may leave out the city.

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

Affected pages:


Nov 6, 2026

API Reference: a Home Page by Section

The API reference tab now opens a home page. Before, it opened List Internal Accounts.

  • The home page lists every endpoint by section, with its method and path.
  • Cards at the top jump to each section.
  • Each section links its webhooks page.
  • The sidebar shows the home page as Overview.
  • Nothing changed in the API.

Affected pages:


HSBC Hong Kong Direct Debit, and When a Cancel Is Sent

HSBC Hong Kong direct debit shipped in October without a changelog entry. In live mode, Acme turns it on for each organization.

  • A payer who banks with HSBC (payerBankCode 004) gets REQUIRES_AUTHORIZATION and an otp object.
  • Confirm the code with Confirm a Direct Debit Authorization OTP. Ask for a new code with Regenerate a Direct Debit Authorization OTP.
  • A payer at another bank gets no OTP. The authorization is SUBMITTED until their bank approves it.
  • HSBC Hong Kong authorizations cannot be cancelled through Acme. The cancel endpoint answers 422 with INVALID_OPERATION. The payer cancels with their bank.
  • Acme reads HSBC's daily report each morning. A cancelled, expired or deleted mandate becomes CANCELED, and Acme sends direct-debit-authorizations.canceled.
  • Acme checks the status of each HSBC Hong Kong collection (HK_DDI). HSBC's daily report settles any collection still SUBMITTED.
  • The Direct Debit Webhooks page now shows, bank by bank, when Acme sends direct-debit-authorizations.canceled.
  • For Standard Chartered Hong Kong, Acme also sends it when the payer cancels at their bank.
  • For Singapore (eGIRO), Acme sends it only after you cancel through Acme.
  • Malaysia (FPX) authorizations cannot be cancelled through Acme. The cancel endpoint answers 400 with INVALID_REQUEST_PARAMETER, and the event is never sent for them.

Affected pages:


API Reference: Corrected Examples

  • Create a Payment: the PENDING_APPROVAL example no longer shows a review block. The create response does not carry one. Get a Payment does.
  • Create a tracked QR code: the test amounts are 117 for SUCCEEDED and 72 for FAILED. The description said 225 and 125.
  • Create a Batch Payment now links to Batch payments: integrate and test.
  • Nothing changed in how the API behaves.

Affected pages:


Test Mode Values: Steps, Payloads and More Endpoints

Special test mode values is now Test mode values. Each endpoint has its steps, its values in a table, and an example payload where one helps.

  • hpm_TESTMODEPENDING_INSUFFICIENTFUNDSPENDINGTOPUP leaves a hosted payment PENDING. The page said it failed.
  • The PayLah! test values work only with method PAYLAH.
  • The HSBC Hong Kong direct debit section is now three steps and a set of tables.
  • Newly documented: Hong Kong direct debit authorizations when your account is at Standard Chartered.
  • Newly documented: the direct debit customerReference values pending, FAIL and FAIL-BATCH.
  • Newly documented: test values for tracked QR codes, refunds, bank account verifications and payment proxy lookup.
  • In test mode, the FX endpoints use fixed sample rates, not live rates.
  • API reference pages for endpoints with test values now link to them.
  • Nothing changed in the API.

Affected pages:


Single Payments: Integrate and Test

A new page, Single payments: integrate and test, sits under Payment lifecycle and statuses.

  • It has an example request and response, the rules every bank applies, and each error with what to do.
  • Send type, currency and receiver with every payment. DBS answers 400 when one is missing. Some banks answer 500.
  • In test mode, 000000001 fails a single payment straight away, like 000000000. It is not a later failure.
  • Test mode differs by bank. The page has a table by bank.
  • Zand, Banco Azteca and OCBC Singapore test payments always succeed.
  • Citibank Singapore, Citibank Malaysia and UOB Singapore single payments cannot be tested yet. Every test payment fails, with no webhook. Test with a batch payment instead.
  • Nothing changed in the API.

Affected pages:


Batch Payments: Integrate and Test

The Batch Payments guide is now Batch payments: integrate and test, a page under Payment lifecycle and statuses. Links to the old address still work.

  • The validation list described only the earlier DBS rules. It now lists the rules every bank applies, and each bank's guide lists its own.
  • Two of the old rules were wrong even for DBS. An ACT payment may have an address. A PAYNOW payment must not have receiver.bank.
  • Most banks take up to 1,000 payments in a batch. Some take fewer, for example ANZ.
  • The page has a full example request and 200 response, and an example 400 with paymentErrors.
  • paymentErrors is empty when only batch fields fail.
  • paymentErrors is left out when the sender account, its currency or the payment type is not valid.
  • After a 500, check for the batch before you retry, and retry with a new Idempotency-Key.
  • In test mode, 000000000 and 000000001 both fail that payment.
  • Test results arrive about 10 to 25 minutes after you create the batch.
  • AU_BPAY, MY_JOMPAY and GB_SEPA test payments cannot be made to fail. They have no receiver account number.
  • UAE Bank Codes moved under Standard Chartered in the sidebar. Only Standard Chartered UAE uses its table. Its address is unchanged.
  • Nothing changed in the API.

Affected pages:


A New Docs Home Page

docs.tryacme.com now opens a home page, Build with Acme. Before, it opened the first API endpoint.

  • The home page has a Get started button and an API reference button.
  • Start building lists the five steps to your first live payment.
  • Browse by product links each product to its API reference page.
  • Browse by bank links each bank's payment rules, market by market.
  • Getting started is now a walkthrough in five steps: get a test key, authenticate, send a test payment, receive webhooks, and go live.
  • Nothing changed in the API.

Affected pages:


Nov 5, 2026

Banco Azteca: Special Characters Rejected at Create

A Banco Azteca payment now returns 400 at create when paymentDetails, or a book transfer's customerReference, holds anything other than letters, digits and spaces. Before, Acme accepted the payment and Banco Azteca then rejected it, so it failed with resultCode OTHERS.

Affected pages:


Direct Debit Webhooks: External DDA Examples

The Direct Debit Webhooks page now shows collections made with an authorization kept outside Acme (an external DDA).

  • Two new tabs show a Singapore FAST collection and a Singapore GIRO batch collection made with an external DDA.
  • These webhooks carry directDebitAuthorizationInformation instead of directDebitAuthorizationId.
  • In that block, internalAccountId is the receiving bank account number.
  • Every collection example now shows bankReference.
  • bankReference is null except for HSBC Hong Kong payments.
  • The Singapore authorization examples now show the deprecated maxAmount and maxAmountCurrency as null.
  • In live mode, they have a value only for an authorization created with them.
  • The successful Singapore authorization example now shows precheckMaxAmount lowered to the amount the payer authorized.
  • Nothing changed in the API. Only the examples were incomplete.

Affected pages:


Nov 3, 2026

Maybank Singapore: a Returned Payment Fails

A Maybank Singapore payment that your verifier or authoriser returns in Maybank2E is now FAILED, with a payments.failed webhook. Before, it stayed SUBMITTED.

Maybank cannot accept a returned payment again. Treat it as failed in your system; to pay again, create a new batch payment.

Affected pages:


Payment Lifecycle: How Banks Report on a Payment

The Payment lifecycle and statuses guide now explains bank reports in levels, the same way for every bank. Your integration still needs only the Acme statuses and webhooks.

  • A single payment goes through two levels: the bank accepts or rejects it, then reports its final status. A table shows the Acme status at each level.
  • A batch file goes through up to three levels: the file, the payments in it, and each payment's final status. A table shows the Acme statuses each level can produce, and when Acme sends payment-batches.rejected.
  • The per-bank sections, with each bank's files and status codes, are removed. Contact Acme if you need a bank's detail.

Affected pages:

On this page