Release 15/10/2024

Version: 2024.10.08.1

Date: 8th October 2024

What's included?

• GET /reconciliation report endpoints
• Renamed "Finaro" to "Shift4" in the Hub
• Bug Fixes:
  • Disabled the Hub payment links send by SMS feature
  • Google Pay button not appearing on Safari and Firefox (Components)
  • Network Tokens should not be used for MOTO Payments
  • Webhook endpoint error messaging
  • Handling of Duplicate CRES from ACS
  • Dispute defence file size validation

GET /reconciliation report endpoints

We have expanded the API suite with two new endpoints to streamline the retrieval of reconciliation reports:

GET /reports/reconciliations: This new endpoint allows users to retrieve a list of available reconciliation reports, supporting queries based on Company-Id, Mid, date range, and specific fields. It also includes pagination for efficient data handling. This functionality mirrors the actions available via the Hub's financials section, enabling users to programmatically access reconciliation reports.

GET /reports/reconciliations/:id: This endpoint provides detailed, transaction-level information for a specific reconciliation report. It supports filtering through query parameters and pagination to manage large datasets effectively.

Check out the documentation here:

• Guide
• API Reference

Renamed "Finaro" to "Shift4" in the Hub

All instances of the label "Finaro" in the Hub interface have been updated to "Shift4" to reflect the latest branding changes.

Bug fixes

1. Disabled the Hub payment links send by SMS feature:

We have made a change so Hub users know that the SMS service is currently not operational. While this issue will be resolved in an upcoming ticket, we are providing this notice since the feature is not actively in use by users at the moment. The default selection for the “SMS Message” <> “Email” toggle will be updated to "Email" (previously set to "SMS Message").

2. Google Pay button not appearing on Safari and Firefox (Components):

Resolved an issue where the Google Pay button was not displaying in Safari or Firefox browsers within Components. This issue was caused by a default cross-site tracking setting in these browsers. We’ve implemented a solution to bypass this setting. However, for Firefox users, the "Block Pop-ups" feature must be disabled in order for Google Pay to function correctly, as we were unable to bypass this specific setting in the browser.

3. Network Tokens should not be used for MOTO Payments:

We have fixed an issue in our integration with CashFlows for MOTO payments. Previously, a network token was being passed during transactions, which was incorrect for MOTO payments. Now, the standard PAN will be passed as required, ensuring proper transaction processing.

4. Webhook endpoint error messaging:

When adding a webhook without selecting a type, the error message has been updated from "add nothing" to a more informative message: "Please select a webhook type." This ensures better clarity for users during webhook creation.

5. Handling of duplicate CRES from ACS:

We have implemented a change to address the issue where a second CRES is posted from the ACS. The system will now ignore the second CRES and proceed as though it was not received. This is a similar approach to what was previously used with the HPP to resolve similar issues.

6. Dispute defence file size validation:

We have fixed a bug that limited Dispute File uploads to 0.4MB, instead of the intended 2MB limit as originally specified.