Release Notes - 21/03/2024

Version: 2024.03.21.1

Date: 21/03/2024

What's included?

  • Direct Debit (initial phase released):
    • Creating Mandates
    • Creating Collections
    • Direct Debit Webhook Notifications
    • Retrieving Mandates
    • Retrieving Collections
    • Cancelling Collections
    • Retrying Failed Direct Debits
  • Components enhancements:
    • Fields: saving card details
    • Payment: payment_methods array
  • Hosted Checkout: AMEX Support
  • Recurring Payments: Linking Card IDs and Customer IDs
  • Improvement to Background Colours on Sensitive Data Masking

Direct Debit

We have now released the initial phase of Direct Debit, marking a significant milestone in our payment method offering. This release includes a range of essential Direct Debit features.

Here's an overview of the key functionalities included in this initial phase:

  1. Creating Mandates:

Merchants now have the ability to create mandates that are linked to customer profiles. The creation of a mandate is the essential first step in the Direct Debit process, so collections can easily be processed against the associated mandate.

  1. Creating Collections:

With the introduction of collection creation, merchants can initiate direct debit transactions effortlessly. This feature empowers merchants to efficiently collect payments from their customers.

  1. Webhook Notifications:

The inclusion of webhook notifications ensures real-time updates and notifications for important events within the direct debit process. This feature enables users to stay informed about mandate confirmations, collection statuses, and other critical updates.

  1. Retrieving Mandates and Collections:

Utilise the GET endpoints to retrieve the full mandate and collection details.

  1. Cancelling Mandates:

Utilise the /mandates/{mandate_id}/cancel endpoint to immediately terminate a mandate.

  1. Cancelling Collections:

Similarly as above, users have the ability to cancel collections when necessary, providing them with the flexibility to modify payment arrangements as required.

  1. Retrying Failed Direct Debits:

To minimise disruptions and ensure successful payments, logic has been built to retry failed direct debits, specifically in cases where the Direct Debit has failed due to insufficient funds. This feature helps mitigate payment failures and enhances transaction reliability.

For more information on our Direct Debit solution, please refer to our guides.

Components Enhancements

We continue to make enhancements to our Components solution, that elevate the efficiency and functionality of this integration method.

  1. Fields: Saving Card Details:

We've enhanced the individual Fields component to allow merchants to specify that card details should be stored for future transactions. We have introduced a new field within the confirmParams object, named create_card, to indicate to the API to generate and return a card_id. This addition aims to facilitate the reuse of stored card details in subsequent transactions by the developer.

  1. Payment: payment_methods array:

The Payment component has been enhanced to provide merchants with the ability to designate which payment methods are presented to users. Previously the Payment component displayed both Apple Pay and Google Pay (if supported by the browser) alongside card payments upon loading, without developer input. With the addition of the payment_methods array, merchants now have the option to specify which payment methods are displayed to the end user.

Hosted Checkout: AMEX support

We continue to enhance and improve our Hosted Checkout solution.

As requested by merchants, we have now added support for AMEX within Hosted Checkout.

Linking Card IDs and Customer IDs for recurring payments

As a Hub user, it is crucial to have comprehensive insights into all recurring transactions associated with specific Customer IDs. To enhance visibility and management of recurring transactions within the Hub, we have implemented a feature where reuse or rebill requests utilising a card_id will now be associated with the relevant customer_id in the Hub.

Improvements to Background Colours on Sensitive Data Masking

During the input of card numbers and CVV in our integration methods, numerical values are appropriately masked for security purposes. Previously there was an inconsistency which was causing visual disruptions with the field colours and impacting negatively on user experience. This has now been updated and the background colour will always match that defined by the developer, irrespective of whether the data is masked or not.