improved

Release 08/04/2025

Release: v2025.04.08.1

Date: 8th April 2025

Items:

  • Settlement Report Retired
  • New "Settled" Status for Direct Debit Transactions
  • Increased Password Reset Request Limit for Improved User Experience
  • Enhancement to card_update Webhook for Network Token Updates
  • Bug fixes:
    • Fixed Sidebar Scroll Issue on Smaller Screens
    • Identified Multiple Active Network Tokens for Single Card or Transaction
    • Fixed Missing Transaction Status in HPP Webhook Responses
    • Missing Payment Reference in GET Transactions Endpoint

Settlement Report Retired

Access to the Settlement tab for the Settlement Report has now been retired in the Hub. Non-Super Admin users can no longer view or export the Settlement Report. Access to the Reconciliation Report remains unchanged and fully available to all relevant users.


New "Settled" Status for Direct Debit Transactions

To streamline reconciliation for Direct Debit (Managed Service) merchants, Acquired has introduced a new "Settled" transaction status. This status is automatically applied when funds from Nuapay are confirmed to have been deposited into the merchant’s account. Previously, merchants manually reconciled lump sum settlements with individual transactions. Now, Acquired leverages Nuapay webhooks and payout data to match settlement amounts against successfully processed transactions (confirmed via the DirectDebitDReturnPeriodPassed webhook). When amounts align, affected transactions are updated to "Settled" and a collection_settled webhook is sent to subscribed merchants. This automation improves accuracy and reduces operational overhead. If amounts do not match, transaction statuses will remain as "Success" until resolved.


Increased Password Reset Request Limit for Improved User Experience

To reduce user frustration and improve accessibility, the password reset request limit has been increased from 2 to 5 times per hour. This update offers greater flexibility without compromising security, and remains fully compliant with PCI DSS requirements.


Enhancement to card_update Webhook for Network Token Updates

The card_update webhook now includes two new fields: update_type and update_detail. These fields are sent when a card_id is updated with new PAN and/or expiry details following a network token update (via VTS or SCOF). When triggered, the webhook will include:

  • update_type: network_token
  • update_detail: card_updated

This enhancement provides greater clarity on the nature of card updates and supports improved downstream processing for merchants.


Bug fixes

  1. Fixed Sidebar Scroll Issue on Smaller Screens

Resolved an issue where the left-hand sidebar in the Hub did not resize or provide a scroll option on smaller screens, making bottom tabs (e.g., Settings) inaccessible. The sidebar now adjusts dynamically with window size, and a scrollbar appears when needed to ensure full navigation access.

  1. Identified Multiple Active Network Tokens for Single Card or Transaction

Detected data integrity issues where multiple active (status = 1) network tokens exist for the same card_id or transaction_id, despite the expectation that only one active token should exist per card or transaction. Query outputs attached highlight affected records for further investigation.

  1. Fixed Missing Transaction Status in HPP Webhook Responses

Resolved an issue where the code and message fields in return_url and callback_url responses were returning null, preventing merchants from determining the transaction outcome. The webhook responses now consistently include the correct status code and message, ensuring accurate post-transaction handling.

  1. Missing Payment Reference in GET Transactions Endpoint

Resolved an issue where the reference value entered via the Payment Links feature was not returned in the GET Transactions endpoint response, despite being visible in the Hub. The endpoint now correctly includes the reference field, ensuring consistency across API responses and the Hub interface.