Release Notes - 2025

20th November 2025 (UAT: 19th November 2025)

Stability and performance improvements made to the recurring payment service.

Performance improvements made to the service that creates Direct Debit payments from schedules.

Xero Intergration added to Smarterpay cloud.

Zuora Intergration added to Smarterpay cloud.

A new property, called “external_id”, has been added to the Customer Account API end point.
This is for the Xero integration.

A new response property, called “paying_bank_reference”, has been added to the Payment API end point.

A new property, called “paying_bank_reference”, has been added to the Payment Webhook.

Updates to the submission service to improve performance and to prepare for upcoming changes to SmarterPay Cloud.
Added internal alert for Bacs submission issues.

Two new properties have been added to the API response for Mandates

SmarterPay have added the following enhancements to the Bacs Rejection Processing functionality

“Override Whitespace” option added to Custom Bacs Rejection Profiles.
- Ocasionally the Mandate or Payment references in the Bacs rejection files aren't 100% correct. For example a Mandate reference of “ABC-123” might be in the rejection file as “ABC 123”. This option allows the Bacs Rejection Processing Service to have another try at finding the record by replacing any spaces with the selected character, in this case “-”.

“New Instruction” option added to the "Mandate Selected Action" for selected Rejection codes.
- This new option will mark the Mandate as a “New Instruction” and send it off to Bacs, with the new bank details. Applies to:
  - “ADDACS 3 - Instruction Cancelled, Account Transferred New Details Supplied”
  - “ARUDD 3 - Instruction Cancelled, Account Transferred New Details”
  - “AUDDIS 3 - Instruction Cancelled, Account Transferred New Details”

SmarterPay have added Bacs core reference functionality to SmarterPay Cloud and SmarterPay Cloud API.

Core references can be used to more acurately match Direct Debit payments with a Direct Debit Instruction (DDI or Mandate).

The way this works is as follows:

A new Mandate is created with a unique core reference, for example “MA10867326”.
All payments that are created for the Mandate contain the core reference, plus a payment reference, for example “MA108673260001” for the first payment, “MA108673260002” for the second payment, and so on.

Changes, in SmarterPay Cloud, for this new feature, are:

API
- AUDDIS references cannot contain lowercase alpha characters. Valid characters: A-Z, 0-9, “/”, “-”, “.”, “&”, “ ”.
- Core reference validation added to Mandate creation, when core reference is enabled on client.
- “mandate” and “users_reference” properties added to Direct Debit creation.
Portal
- Core reference validation added to Mandate creation, when core reference is enabled on client.
  - Creation using the Portal.
  - Creation using the Payment Wizard.
  - Creation of the Ecommerce Link.
- “Users Reference” field added to Direct Debit Payments.
- “Remove Non Standard Characters” option added to File Formats.
Webhooks
- “users_reference” property added to the V2 Direct Debit Payment webhook.

Direct Debit payments, when cancelled, will now no longer have their amount set to 0.

Payment records in SmarterPay Cloud are now split by type, so Card payments are now kept separate from Direct Debits.

Changes, in SmarterPay Cloud, for this new feature, are:

Portal
- The “Payments” menu item has been renamed to “Direct Debits”, and no longer contains Card Payments.
- Card Payments are now in their own area called “Card Payments”, and have a prefix of “P02”.
- The “Scheduled Payments” menu item has been renamed to “Scheduled Direct Debit Payments”, and no longer contains Card Payment Schedules.
- Card Payment Schedules are now in their own area called “Scheduled Card Payments”, and have a prefix of “RS02”.