Changelog
Back to All
added

Release 08/10/2024

12 days ago by Alice Barrow

Version: 2024.10.08.1

Date: 8th October 2024

What's included?

  • update_card webhooks
  • AFT updates
  • Bug fixes:
    • Cashflows 'High Risk' entries removed from Recon report
    • Custom data not updating on Direct Debit retry requests
    • Pay by Bank Hub error
    • Improved 3DS error handling for REST and CORE API
    • GET /transaction endpoint response error
    • GET /transaction endpoint not including refund amount

update_card webhooks

We've introduced a new card_update webhook, built to follow the Webhook Version 2 standards. This webhook notifies merchants when a card_id is updated due to a network token change, including updates to the card's PAN and/or expiry date. This ensures merchants stay informed and up-to-date on card changes in real-time.

Check out our updated webhook documentation here.

AFT updates

We have extended the shipping information mapping in the Core API for Visa, in addition to Mastercard, for transactions under MCC 4829. This update is aligned with a scheme mandate requiring shipping details to be passed to Shift4 for both card types, with a production deadline of 20 October. When the acquiring bank is Finaro, shipping data such as first name, last name, street, city, state, and country code will be correctly mapped to the respective fields in Shift4 for Visa and Mastercard transactions.

Bug fixes

We are committed to continuously improving our products by addressing and resolving system bugs to ensure optimal performance and a seamless user experience.

  1. Cashflows 'High Risk' entries removed from Recon report

We’ve removed “High Risk” entries in the CashFlows Dispute & Fees file from Reconciliation reports. Given these entries are purely fraud alerts and do not involve the movement of any funds, removing them will avoid confusion.

  1. Custom data not updating on Direct Debit retry requests

We have resolved the issue where custom fields (custom_data, custom1, and custom2) passed in a retry Direct Debit request were not being stored against the new collection event created after a retry. Now, any custom fields provided in the retry request will correctly update the stored data against the Direct Debit Transaction ID as expected.

  1. Pay by Bank Hub error

We have resolved a bug where the incorrect status was being displayed for Pay by Bank transactions in the Hub.

  1. Improved 3DS Error Handling in REST API & Core API

We have fixed an issue related to the handling of 3DS errors in the REST API and Core API for Hosted Checkout, API, Components, and Payment Links. Previously, a 3DS ERROR with a misleading "configuration" reason was returned when the issue was actually due to an invalid cres being collected from the ACS window. This error has been addressed to correctly identify and handle the underlying 3DS challenge flow issues. The fix improves error reporting and ensures clearer messaging when a 3DS failure occurs.

  1. GET /transaction endpoint response error

We have resolved an issue where the Transaction endpoint returned an empty status immediately after a recurring payment request. In cases where the status field was empty, it will now properly default to pending.

  1. GET /transaction endpoint not showing refund amount

We have fixed an issue where the amount field returned null when querying the transaction endpoint for a refunded transaction. This has now been corrected to display the refund amount accurately, ensuring proper visibility of transaction details in refund scenarios.