Q3 2025 Silverflow Product Updates

Q3 2025: Silverflow Product Updates

Welcome to your quarterly update on the latest and greatest product updates from Silverflow. Find out what's new and see what Silverflow can now offer you!

Developer Happiness: New and improved Test Scenarios on our Sandbox

The sandbox environment is a controlled and simulated environment that allows clients to test and validate their integrations. Developers can use the sandbox to simulate various scenarios and test different functionalities of their applications. This includes testing data inputs, processing logic, error handling, and other critical integration aspects.

Some of the things we're updating include:

Easier Use of PANs in Sandbox Environment
- Silverflow aims to allow maximum flexibility for its sandbox users. In order to accomplish this, in the sandbox environment Silverflow does not strictly validate PANs, rather it accepts a wide range of PAN - for example any PAN on Sandbox starting with a '4' will be treated as Visa.
3DS Authentication Test Scenarios (for Mastercard & Visa) will soon be amount based, so for example amount.value>3000 or challengeIndicator = challenge-preferred will trigger a challenge flow
We will also add more POS Test Scenarios.

Please keep an eye on our Developer Guides for more on this during the quarter.

Developer Happiness: New Sections to our Integration Guides pages

We value your ability to fully understand how the Silverflow API can be applied to solve some of your payments business cases. To this end, we will be continually adding and updating our Developer Guides. Please always refer to our Developer guides along side our API reference - our Guide is developed to give you example use cases for our API. For example we've added more detail to our Funding and Payouts documentation on the Guides page.

List Reconciliation Details by Network Funds Transfer Key

Our Clients have spoken and we listened: Clients typically use the List Reconciliation Details by Network Funds Transfer Key endpoint to get the reconciliation details for an NFT. The concern with this is that you may need to start paginating if there are too many transactions. Clients preferred to use the Reconciliation Details Report, however we did not support the ability to pass in an NFT key for this report. Clients wanted a JSON format used in the List Reconciliation Details and be able to filter by Network Funds Transfer Key. This is now all avaialable.

New CSV reporting guidelines

As we have more customers relying on parsing CSV report formats for their daily operations. We have updated our reporting guide with some considerations regarding these reports, as well as a list of breaking/non-breaking changes specific to CSV reports. This will ensure we can guarantee stability and continuity, like we do on our API. This gives us more flexibility when we add new data / change the order of columns on CSV reports. You'll now be required to integrate with CSV reports using column headers instead of the column number. This eliminates disruptions in case of new data fields or changes in column order.

Rename MIT charge endpoints

We are planning on renaming the MIT charge endpoints to clarify what they do (the ones we currently refer to as “Unreferenced”). The following renames will be performed.

On our API docs you will soon see:
- Create MIT Charge updated to Create MIT Charge from Initial Charge
- Create Unreferenced MIT Charge updated to Create MIT Charge
- Create Unreferenced MIT Funding Charge updated to Create MIT Funding Charge

Schemas & Code
The above will not be considered breaking changes, however, do let us know if there any questions and please do monitor our API docs for this change.

Mastercard Identity Check Migration to Acquirer Reference ID-Based Enrollment

Silverflow are monitoring GLB 11171.2 Mastercard Identity Check Migration toAcquirer Reference ID-Based Enrollment and Decommission of Identity Solutions Services Management Merchant Enrollment API anncouncement. This was published on the 15th of July 2025.

Mastercard is announcing a switch to acquirer-based enrollment for Mastercard Identity Check® using assigned Acquirer Reference ID (ARID) and eliminating the requirement for merchant ID level enrollment.

Please note the new timelines and Effective date details as published by Mastercard in this updated bulletin:

On the 26th of September 2025 ISSM Merchant Enrollment API will be decommissioned and all access will be revoked by Mastercard.
Silverflow will match any deprecations to this updated bulletin. Silverflow will update our date for the removal of POST/enrollments for ISSM and deprecation of GET/enrollments for ISSM to 26 September 2025.
Mastercard has added informaton on exactly how clients can review and manage their ARID level enrollments going forward in the bulletin. Please review this and reach out to Mastercard directly with any questions.