improved

Release 12/11/2024

Version: v2024.11.12.1

Date: 12th November 2024

What's included?

  • Updates to mandate endpoints
  • Bin Configuration Header Parameter
  • FAPI 1.0 Updates
  • Bug fixes:
    • Country Code and Phone Number Field Update
    • Network Token Usage - MOTO

Updates to mandate endpoints

Retire POST /v1/{{customer_id}}/mandates

We have retired the original /{{customer_id}}/mandates endpoint as it was no longer used. All merchants integrated to use Direct Debit are now using /mandates.

Update to Mandate Creation Process

The mandate creation process has been updated to make customer billing address details optional, ensuring mandates can be created without requiring address fields like line_1, city, postcode, and country_code. This update maintains validation for essential fields (e.g., customer_id, sort_code, account_number, and mandate_type) to ensure mandate integrity.


Bin Configuration Header Parameter

A new solution has been introduced to allow developers using Acquired.com's REST API to apply BIN rules at the MID level while utilising load balancing. This is achieved by adding a new header parameter, Bin-Configuration, to the /payment-links, /payment-sessions, and /payments endpoints.

When Bin-Configuration is provided, it takes priority over the Mid parameter, applying the specified BIN rules to block particular BINs, while maintaining load balancing functionality. If Bin-Configuration is not provided, the existing Mid logic will apply. This enhancement maintains backward compatibility to support merchants who haven't yet migrated.

Additionally:

  • For Hosted Checkout, if a blocked BIN is entered, an error message will notify users that the card cannot be processed.
  • A 400 error will be returned if Bin-Configuration is invalid.

FAPI 1.0 Updates

We are releasing several essential updates to our bank integrations to align with FAPI 1.0 standards for Open Banking.


Bug fixes

  1. Country Code and Phone Number Field Update

We've added separate fields for "Country Code" and "Phone Number" in the customer creation and update forms within the Hub, replacing the single "Billing Phone Number" field. This change aligns with the API structure and includes updated form validation to ensure correct formatting. Existing data has been migrated to the new fields where applicable.

  1. Network Token Usage - MOTO

We've updated the processing logic for MOTO REBILL and RECURRING transactions to ensure that network tokens are utilised wherever possible, aligning with current processing standards.