Release Notes - December 2023

Release date: 13th December 2023

What's included?

  • Webhook-Version 2
  • Process refunds to expired cards
  • Improvements to Hosted Checkout
  • Pay by Bank refunds

Webhook-Version 2

We have created a Webhook-Version 2 that includes changes to the following:

  • Update webhook verification to HMAC_SHA256.
  • Pass Company-Id and Mid header parameters only as GUIDs.
  • Updated the webhook structure to remove the timestamp from the webhook_body object.

Using HMAC_SHA256 significantly boosts security and simplifies the way we verify webhooks for you. This method is an industry standard, a well-supported and trusted way to protect your data. Instead of our previous more complex process, HMAC_SHA256 involves a single, robust cryptographic function applied to the entire JSON message sent to your webhook URL, streamlining the integration process.

Check out are updated webhook guides here.


Process refunds to expired cards

We've introduced a new feature enabling the processing of refunds to expired cards. This ensures that the funds will successfully reach the issuing bank, even if the card has expired.


Improvements to Hosted Checkout

We have made various changes to Hosted Checkout, to improve the user experience for both the merchant and customer.

We've made improvements that allows you to specify a particular card ID for your customers to use during payment. This enhancement enables merchants who manage cards within their systems to offer customers the option to select a card before they're directed to the Checkout.


Pay by Bank refunds

We have added the capability to process refunds for Open Banking payments. This utilises the existing /transactions/{transaction_id}/refund endpoint. In order to process an Open Banking refund Acquired will need to have visibility of the end-users bank account details – account name, sort code, account number. For this reason, only Open Banking transactions that are in settled status can be refunded.

For more information on this process, please refer to our API reference.