Changelog
Contact Sales
Back to All

Verifications product renaming

6 days ago by ReadMe API

We are renaming the Verifications product to Access Verifications. This change will be effective on March 25, 2025.

Why the change?

When the Verifications product was initially developed the available possibilities to determine the access and legal account holders of a bank account were very limited.

In the last few years, the landscape has changed and we now have more options, including Valitic in the spanish ecosystem and VOP (Verification of Payee) in the SEPA area.

This new available schemes allow not only the verification of the access to a given bank account but also the verification of the legal account holders. To better reflect the new capabilities of the incoming products, we are renaming the current service to Access Verifications.

What does this mean for you?

  • The Verifications product will be renamed to Access Verifications.
  • The old Verifications API endpoints (/v1/verifications) are deprecated as of March 25, 2025.
  • The new Access Verifications API endpoints (/v1/access_verifications) are available as of March 25, 2025.
  • The Access Verifications API endpoints are fully compatible with the old Verifications API endpoints: same parameters, same responses, same behavior.

What do I need to do?

  • Update your code to use the new Access Verifications API endpoints (this should be a matter of changing the endpoint path verifications to access_verifications).
  • If you are processing webhooks, you will need to update your code to process the new webhook types (e.g. access_verification.confirmed instead of verification.confirmed).

That's it. Just a simple replace of naming to migrate to the new product. Of course you should verify the new endpoints are working as expected but as we have kept the all the functionality compatible with the old product, the migration should be straightforward.

When will be the old product sunset?

  • As we considered this is a trivial migration we are giving our customers a 30 days period to migrate to the new product.
  • The old Verifications API endpoints (/v1/verifications) will be removed as of April 24, 2025.
  • If we positively confirm that all our customers have migrated to the new product we may remove the endpoints before the 24th of April.

What if I have any questions?

If you have any questions, or need help with the migration, please contact us at [email protected].

We are very excited about the new capabilities we are bringing to the family of verification related products. We think they will enable you to create better products for your customers by providing a complete, robust verification experience.