Changelog
Back to All
improved

Release 23/07/2024

5 months ago by Alice Barrow

Version: 2024.07.23.1

Date: 23.07.2024

What's included?

  • Create a mandate endpoint v2
  • Hub: email branding
  • Improve “no payments available” error messaging
  • Send PAR in authorisation messages
  • Direct Debit collection attempts

Create a mandate endpoint v2

We are updating the endpoint for creating a mandate as part of our direct debit solution. The current endpoint, POST https://api.acquired.com/v1/{{customer_id}}/mandates, will be changed to POST https://api.acquired.com/v1/mandates. The request body will now include the customer_id parameter.

Hub: email branding

As part of our continued brand uplift project, we have updated some system generated emails to match the new branding.

The following emails have been updated:

  • New user
  • Password reset
  • Hub export is ready
  • Rejection Transaction Alert
  • URGENT - Account Balance Warning
  • Invoices - rebranding
  • Password expired
  • Your Bulk Payout has been successfully processed

Improve “no payments available” error messaging

We have implemented a validation change for payment links. Previously, when Pay by Bank was the only available payment method and capture:false was set for a payment link, a link_id was returned. Opening this link_id resulted in an error screen, as the Pay by Bank transaction could not proceed with capture:false. To address this, we have moved the validation to the /payment-linksrequest, ensuring an error response is returned immediately if Pay by Bank is the only payment method and capture:false. This validation will also be applied when creating a payment link from the Hub.

Send PAR in authorisation messages

We are updating our system to include the Payment Account Reference (PAR) in authorisation requests when a network token is used. The PAR is a non-financial reference that links multiple network tokens associated with a single PAN. This change is requested by Trust Payments to address issues with network token BINs and will apply to both Visa and Mastercard. For consistency, we are also applying this update to CashFlows.

Direct Debit collection attempts

We have added a new feature for Hub users to view a detailed record of each attempt made on Direct Debit transactions. When a Direct Debit transaction is retried using the /retry API endpoint, a new entry is added to the attempts array, providing a complete transaction history with statuses. This information will now be displayed on the Transaction Details page under a new "Collection Attempts" section, showing all recorded attempts in order of creation time.

Bug fixes

  1. Components Error:

We have resolved an issue where we were returning an Internal Server Error when using the Company Guid only to create a customer, without the company having a default Mid.

  1. Requests tab access:

We have updated the user permission to allow read-only roles to have access to the Requests tab.

  1. Bug with creating customers:

We have resolved a bug where the creation of a customer was defaulting to the first company created on the account.

  1. Sales Lite user permissions:

We have updated the sales lite user permissions to be able to create customers in the Hub.