Changelog
Back to All

Release 05/09/24

about 2 months ago by Jamie Lynch

Version: 2024.09.03.1

Date: 03.09.2024

What's included?

  • Configurable payment submit button in Checkout
  • Configuring the payment methods included in a payment link
  • Visa Direct - Billing country is sent to Trust Payments
  • Network tokens are not created or processed without SRD
  • Updating pending DD collections to cancelled when Mandate is cancelled
  • Bug fixes
    • Virtual Terminal support cards with extended validity period
    • Restrict mandates displayed for a customer to that customer
    • Prevent invalid dispute defence file generation
    • Issue with Retrying Failed Direct Debit Payments
    • Hub timezone of transaction data display
    • Filter field for integration methods in Hub
    • Missing Shift4 reconciliation reports
  • Non-functional enhancements
    • Merchant custom data for refunds is now populated in reconciliation reports

Configurable payment submit button in Checkout

Checkout developers can now adjust the text displayed in the payment submit button, to better match the transaction type. While the default will be “Pay Now”, merchants can choose to adjust this to Buy, Checkout, Donate, Register or Subscribe.

https://docs.acquired.com/docs/configure-your-checkout#configuring-the-payment-submit-button

Configuring the payment methods included in a payment link

Hub users can now choose to include a subset of active payment methods in a payment link. The default set of payment methods from Hub Settings can be configured per payment link, supporting a custom set of payment methods offered depending on the payment link.

This is completed in the Settings section of the payment links form on the Acquired.com Hub.

Visa Direct - Billing country is sent to Trust Payments

Trust Payments have informed us that passing the billing country code for Visa Direct transactions may increase auth rates in some regions so we have uplifted our integration to support it.

Network tokens are not created or processed without SRD

Visa and Mastercard have become more strict on the use of scheme reference data as a required field when processing recurring transactions, specifically those using network tokens. On the rare occasion we do not have scheme reference data for a stored card that has an active network token, we will attempt the transaction using the PAN instead to increase the chance of a successful authorisation.

Since network tokens will not be processed without scheme reference data, network tokens will not be created if the stored card does not have an active scheme reference data value.

Updating pending DD collections to cancelled when Mandate is cancelled

Direct Debit collections are based on an active and valid mandate being in place. Therefore when we receive a request to ‘cancel’ a mandate, any future attempts to collect a DD against that mandate should be blocked. This change ensures that any DD collections in ‘pending’ status are ‘cancelled’ when we receive a mandate collection request.

Virtual Terminal supports cards with extended validity period

Cards that are issued with expiry dates up to 10 years out will now be accepted.

Bug fixes

  1. Different customer mandates are displayed against the incorrect customer profile

Previously all mandates were shown on any customer for a merchant. Now the mandates displayed are restricted to the selected customer.

  1. Prevent invalid dispute defence file generation

Resolves an issue where generated dispute defence files include duplicate pages resulting in exceeding upstream file restrictions.

  1. Issue with Retrying Failed Direct Debit Payments

Acquired was not providing response to Nuapay webhooks within 10 secs limit

  1. Hub timezone of transaction data display

Bug fixed whereby the Hub displayed data on graphs not in line with a merchant’s timezone. This meant that transactions were being displayed with a one hour offset to the actual time they were processed.

  1. Improving filter field for integration methods in Hub

When reviewing the link ids generated by a merchant, in the ‘Status’ page of Payment Links page in the Hub, the “Integration Option” filter has been fixed to include all available options.

  1. Missing Shift4 reconciliation reports

Resolved an issue where reconciliation reports from Shift4 were not available for download in the Hub since Aug 20th.

Non-functional enhancements

  1. Merchant custom data for refunds is now populated in reconciliation reports.
    For refund transactions, we will now pull in the merchant custom data associated with the initial sale and populate it in the reconciliation reports so that merchants can reconcile transactions accordingly.