Upcoming Breaking API Change - 4/16/2026

The changes will be effective starting 4/16/2026 at 7:00 PM (PST) in production.

The changes will be available for testing in sandbox starting 4/2/2026 at 7:00 PM (PST).

Deprecation of the creation of transfers with type FEE

What’s Changing?

On April 16, 2026, Fees will only be created via the Fees resource and will no longer be generated as Transfers resources that are retrievable from the /transfers endpoint. In other words, Transfer resources of type FEE will no longer be created. More details below:

All existing Transfers of type FEE have now been copied to the Fees resource.
If you would like to map between Transfers and Fees, a Transfer of type FEE will have a link to the fee with the ID of the Fees resource.
Existing Transfer resources of type FEE will remain accessible, i.e., no resources will be deleted.
The fee link on a parent Transfer will now direct to the fee resource on /fees instead of /transfers.

What action is needed?

Clients who currently retrieve fees from the /transfers endpoint or rely on webhooks must transition to utilizing the /fees endpoint.

Example of Fetching Fees for a Transfer:

To fetch Fees for a given transfer use the following linked_to query parameter on /fees.

https://finix.sandbox-payments-api.com/fees?linked_to=TRjiQJ5gRfuVtccFmtn2HYuT

Why are we making these changes?

This modification aims to provide a clearer distinction between money movement and fees, thereby simplifying API comprehension. Furthermore, it will reduce the number of webhooks triggered for implementations that subscribe to transfer webhooks.

What You Need to Do

Review Your Integration: Ensure your application is compatible with the new API behavior.
Make Necessary Updates: Modify your implementation accordingly before the change takes effect.
Test in Sandbox: Transfers of type FEE will stop being created in sandbox starting 4/2/2026 at 7:00 PM (PST).

Need Help?

If you have any questions or need assistance, our support team is ready to help. Please reach out to support@finix.com or refer to our documentation here.

We appreciate your attention to this update and your continued partnership.