Changelog
Back to All
added

Release 11/12/2024

8 days ago by Alice Barrow

Version: v2024.12.11.1

Date: 11th December 2024

What's included?

  • Confirmation of Payee
  • FAPI 1.0 Updates
  • Bug fixes:
    • /single-immediate-payment error
    • Incorrect mapping invalid card number to server_error
    • Fixed Character / Issue in Customer Objects for Bank of Scotland, Lloyds, and Halifax
    • Fixed Incorrect CVV Handling for Recurring Transactions with Trust Payments
    • Fixed Pay by Bank Display for Recurring Hosted Checkout Payments
    • Recon Report Void and Missing Transactions

Confirmation of Payee

We are pleased to announce the release of our Confirmation of Payee functionality, designed to enhance the accuracy of payee account details verification for merchants using Acquired’s system. This new feature introduces a dedicated API endpoint, /tools/confirmation-of-payee, which allows merchants to provide essential payee details, including sort code, account number, account name, account type, and scheme, for validation. The endpoint ensures robust data validation, adhering to strict format and value checks for each parameter. With this enhancement, merchants can confirm the accuracy of payee details before initiating transactions, reducing errors and improving overall payment reliability.

Check out the documentation:

FAPI 1.0 Updates

We continue to implement necessary upgrades to our Open Banking integrations. This release includes FAPI 1.0 updates for the following banks:

  • HSBC
  • First Direct
  • Santander

Bug fixes

We continue to fix bugs within the system.

  1. /single-immediate-payment error:

We have fixed the issue where the /single-immediate-payment endpoint was returning a 502 error, which Cloudflare intercepted and replaced with its custom error page. The status code has now been updated to 500 to prevent Cloudflare from overriding the error response.

  1. Incorrect mapping invalid card number to server_error:

We have fixed the issue where a merchant was querying a server_error status and reason code, which, upon investigation, was incorrectly mapped. The response from Cashflows was an "invalid card number" issuing bank response that was improperly mapped to server_error. The mapping has now been corrected.

  1. Fixed Character / Issue in Customer Objects for Bank of Scotland, Lloyds, and Halifax:

We have fixed the issue where the customer object for Bank of Scotland, Lloyds, and Halifax did not support the character /. This has been addressed to ensure compatibility.

  1. Fixed Incorrect CVV Handling for Recurring Transactions with Trust Payments:

We have resolved an issue where recurring transactions processed via the REST API were being declined due to CVV-related errors. Upon investigation, it was found that the CVV value was being incorrectly included in the recurring authorisation request sent to Trust Payments. This behaviour contradicted the expected handling of recurring transactions, as CVV should not be passed for such requests.

  1. Fixed Pay by Bank Display for Recurring Hosted Checkout Payments:

We have resolved an issue where Hosted Checkout payment links with is_recurring: true incorrectly displayed Pay by Bank as an available payment method. Since PBB cannot be used to complete recurring payments or save/tokenise card details, it should not have been shown. The implementation has been updated to ensure PBB is no longer listed as a payment option for recurring transactions.

  1. Recon Report Void and Missing Transactions:

We have fixed a bug whereby the simulated recon report data in QA should not include voided transactions so it replicates the behaviour of a real bank.