Changelog
Start typing to search…
Back to All
fixed

Release 31/07/2025

21 days ago by Alice Barrow

Release: v2025.07.31.1

Date: 31st July 2025

  • Make CVV Optional on /v1/payments/credit Endpoint
  • CashFlows – Improved Mapping for Card Authorisation Attempt Limit
  • Consistent Hosted Checkout Screen Across Currencies
  • Improved 2FA Error Message Clarity
  • Apple Pay Session Fails When Merchant Name Contains Invalid Characters

Make CVV Optional on /v1/payments/credit Endpoint

We've updated the /v1/payments/credit API endpoint to make the cvv field optional. This change simplifies the integration process for merchants who do not require CVV validation, while still maintaining security and flexibility where CVV is needed.

Cashflows – Improved Mapping for Card Authorisation Attempt Limit

We've improved how our REST API maps responses when the card authorisation attempt limit has been reached via Cashflows. This update ensures clearer and more accurate messaging for merchants, enabling better understanding of transaction outcomes and quicker issue resolution.

Consistent Hosted Checkout Screen Across Currencies

Previously, the hosted checkout screen displayed slight variations depending on the currency used. This update ensures a consistent user experience and design across all currencies, improving visual consistency and customer trust at checkout.

Improved 2FA Error Message Clarity

We’ve reworded the previous error message: "Your have not config 2fa" to a clearer version, improving usability and reducing confusion for users attempting to configure two-factor authentication.

Apple Pay Session Fails When Merchant Name Contains Invalid Characters

We've resolved an issue that caused Apple Pay sessions to fail when the merchant name included unsupported or invalid characters. The updated validation ensures a smoother Apple Pay experience by preventing session initiation failures due to naming issues.