NEW6.00.05 · Not yet released
NEWfinPOWER Connect
Version
6.00.05
Not yet released
  1. Opened12 Aug
  2. Closed30 Oct 2026
  3. ReleasedPending
Article 22746 Job J037276

Banking Interface; Zepto (Split) Australia and Monoova; Payments now send a stable payment reference so the provider can recognise a re-sent payment

Payments sent via the Zepto (Split) Australia and Monoova Banking Interface services now include a unique payment reference derived from the payment's Bank Transaction. The reference is identical across every attempt to send the same payment, so if a send fails (for example, due to a timeout) and the payment is re-sent, the provider can recognise it as the same payment rather than creating a duplicate. This matches the existing behaviour of the Ezidebit service.

This applies to all payment types sent in real time via these services, including PayTo payments and Monoova Credit Card payments. The reference combines the Account Id with the Bank Transaction's unique identifier. Any character in the Account Id other than a letter, digit, hyphen or underscore is replaced by a hyphen, so the provider accepts the reference whatever the Account Id contains.

For PayTo payments the reference is included in the request sent to the provider. For all other payment types it is also recorded on the request's Service Log. A payment that is reversed and re-raised is a new payment and carries a new reference.

Re-send a failed payment promptly. A provider may only recognise a repeated reference for a limited period, after which a re-send can be processed as a new payment.

Re-sending a payment the provider refuses as a duplicate

If the provider refuses a re-send as a duplicate, it already holds a payment with that reference. Check the payment's status with the provider before taking any further action. If the provider has taken the payment, do not reverse and re-raise it: the replacement is a new payment and would be processed in addition to the original.

Additionally, Zepto (Split) Australia requests now retry automatically when the provider rate-limits a request, consistent with the Monoova and Ezidebit services.</wiki>