# September 2026 (/changelog/2026-09) {/* GENERATED by scripts/gen-changelog.mjs from content/changelog.mdx — do not edit. */} ## Sep 10, 2026 [#sep-10-2026] ### Direct Debit Authorization Test Mode: Mock `payerIdType` and `payerIdHash` Are Now Opt-In (API) [#direct-debit-authorization-test-mode-mock-payeridtype-and-payeridhash-are-now-opt-in-api] Successful Singapore eGIRO Direct Debit Authorizations in test mode once again return `null` for `payerIdType` and `payerIdHash` by default. The mock values introduced on Aug 14, 2026 are still available, but only on request. * To receive them, create the authorization with `billReferenceNumber` set to `S1234567D`. `payerIdType` is then `NRIC` and `payerIdHash` is the SHA-256 hex digest of uppercased `S1234567D`. * Any other bill reference number returns `null` for both fields. * Live mode, Malaysia, and Hong Kong are unchanged. #### Affected pages: [#affected-pages] * [Special Test Mode Values](/guides/special-test-mode-values) *** ## Sep 9, 2026 [#sep-9-2026] ### Sample Responses for Payments and Collections [#sample-responses-for-payments-and-collections] The API reference now shows worked sample responses for the payment and collection endpoints, with one sample per supported country for direct debit and hosted payments. Every endpoint also documents its `429` rate limit response, and endpoints that take input document the `400` response with `INVALID_REQUEST_PARAMETER`. #### Affected pages: [#affected-pages-1] * [Create a Payment](/reference/post-payments) * [Get a Payment](/reference/get-payments-id) * [Create a Batch Payment](/reference/post-batch-payments) * [Create a Direct Debit Authorization](/reference/post-direct-debit-authorizations) * [Create a Direct Debit Collection](/reference/post-direct-debit-payments) * [Create a Hosted Payment](/reference/post-hosted-payments) *** ## Sep 8, 2026 [#sep-8-2026] ### Beneficiary Bank Name for Citi Taiwan and Philippines Domestic Payments [#beneficiary-bank-name-for-citi-taiwan-and-philippines-domestic-payments] Citi rejects Taiwan and Philippines domestic files without a beneficiary bank name, so `receiver.bankName` is now **required** on `TW_ACH`, `TW_RTGS` and `PH_PESONET`. It is the bank's name, not a BIC. #### Affected pages: [#affected-pages-2] * [Acme Citibank Taiwan Payments (H2H)](/guides/citi-tw-payments) *** ## Sep 7, 2026 [#sep-7-2026] ### ANZ Australia Address Field Limits Corrected [#anz-australia-address-field-limits-corrected] The [Acme ANZ Australia Payments](/guides/anz-au-payments) guide described `receiver.address` as three fields of 35 characters. That was not accurate. The post code accepts at most 16 characters, because it maps to `PstCd` in the ISO 20022 pain.001 message. The guide now lists each address subfield with its own limit, for both `TT` and `AU_HVCS`. The guide also listed `receiver.address` as optional for `TT`. It is mandatory. The country is always required. If neither address line is given, the city, state and post code are all required. Nothing changed in the API. Acme has always validated the address this way. Only the guide was wrong. #### Affected pages: [#affected-pages-3] * [Acme ANZ Australia Payments](/guides/anz-au-payments) *** ## Sep 4, 2026 [#sep-4-2026] ### API Rate Limits [#api-rate-limits] We now enforce rate limits on the Acme API, per API key and HTTP method. A request over the limit receives HTTP `429` with a `Retry-After` header. The limits are sized well above observed integration traffic, and can be raised per API key on request. See the new [Rate limits](/guides/rate-limits) guide. #### Affected pages: [#affected-pages-4] * [Rate limits](/guides/rate-limits) *** ## Sep 3, 2026 [#sep-3-2026] ### Standard Chartered Hong Kong and UAE Payment Rules [#standard-chartered-hong-kong-and-uae-payment-rules] We published payment rules for [Standard Chartered Hong Kong](/guides/scb-hk-api-payments) and [Standard Chartered UAE](/guides/scb-ae-api-payments) over the SCB Open Banking API. The Hong Kong page covers `HK_FPS_PROXY`, `HK_FPS_ACCOUNT`, `HK_ACH`, `HK_CHATS`, `BKTR`, and `TT`, including the FPS proxy formats and the per-rail currency restrictions. The UAE page covers `UAE_IBFT`, `UAE_FTS`, `TT`, and `BKTR`, including the mandatory Purpose of Payment code, UAE IBAN handling, and the supported sender account currencies. #### Link to payment rules: [#link-to-payment-rules] * [Acme Standard Chartered Bank Hong Kong Payments (API)](/guides/scb-hk-api-payments) * [Acme Standard Chartered Bank UAE Payments (API)](/guides/scb-ae-api-payments) *** ## Sep 1, 2026 [#sep-1-2026] ### DBS Singapore Receiving Party Purpose Codes Reference [#dbs-singapore-receiving-party-purpose-codes-reference] We added a dedicated [Acme DBS Singapore Receiving Party Purpose Codes](/guides/dbs-sg-receiving-party-purpose-codes) page covering the `outgoingPurposeCode` field on DBS Singapore `TT` payments. It lists the country-specific purpose code list for each corridor that requires one. #### Affected pages: [#affected-pages-5] * [Acme DBS Singapore Receiving Party Purpose Codes](/guides/dbs-sg-receiving-party-purpose-codes)