Changelog
Back to All
improved

Release 06/08/2024

5 months ago by Alice Barrow

Version: 2024.08.06.1

Date: 06.08.2024

What's included?

  • Display Direct Debit mandates in the Hub
  • Enable AMEX via Lloyds
  • 3DS Mandated Fields: Hub Payment Links changes
  • Bug Fixes:
    • Apple Pay/Google Pay tokenised card error
    • DOB issue
    • custom_data issue
    • Generate merchant session - endpoint updated
    • Extend display_name validation
    • Apple pay timings incorrect in the Hub
    • Payment Links default setting for capture:true/false

Display Direct Debit mandates in the Hub

We have added the functionality to display Direct Debit mandates within the Hub. This includes a new Mandates tab that is visible when viewing a customer record. The Mandates table features headers such as Mandate Reference, Mandate ID, Account Name, Account Number Ending, Status, Created, and Action. Users can copy the Mandate ID to their clipboard with a copy button and view mandate details in a modal pop-up. The data for these features is populated from the GET Mandates API call, ensuring that all relevant information is accurately presented.

Enable AMEX via Lloyds

We have enabled AMEX processing via Lloyds. When a merchant sends AMEX transactions to their Lloyds MID, we will route the transaction to the Trust Payments gateway, similar to our current process for CashFlows, Finaro, and Barclaycard.

3DS Mandated Fields: Hub Payment Links changes

Following the newly mandated 3DS field changes from Visa on August 13th, we have added a warning message to inform users that including an email address when adding a customer record is recommended for 3-D Secure authentication, although it is not mandatory. This update applies to both Rest API Payment Links and VT, as well as Core API Payment Links and VT forms.

Bug fixes

  1. Apple Pay/Google Pay tokenised card error:

We have resolved an issue where we were showing the incorrect last 4 digits associated to the card_id.

  1. DOB issue:

There was a bug where the DOB field was populating incorrectly.

  1. custom_data issue:

There was a bug whereby we were not accepting Base64 encoded custom_data in the create customer endpoint, this has now been updated and resolved.

  1. Generate merchant session - endpoint updated:

We have updated our response in this endpoint as it contained values from the Core API and was not the correct standard for the Rest API.

  1. Extend display_name validation:

We have extended the display_name validation to support special characters. This was raised by 2b1c (our Magento developer).

  1. Apple pay timings incorrect in the Hub:

The Apple Pay timings were incorrect when exporting the data, this has now been resolved.

  1. Payment Links default setting for capture:true/false:

There was an issue with the /payment-links endpoint where if a merchant does not include the capture parameter, it is defaulting to false. When amount > 0 and PBB is the only available payment method, the capture:false parameter is causing the request to fail.