Changes in Verifications and Transactions Listing

Today, we announce a modification in the verification processing and the removal of some parameters in the transactions' listings. Let's talk business!

Verifications processing:

Until now, customers have been able to trigger as many verifications per IBAN as they want. After analysing the product's use, we have discovered that some customers may inadvertently let their users create multiple verifications in rapid succession without introducing any delay or restriction.

This will consequently create multiple verifications and 1ct transfers to the provided IBAN, each one providing a new verification code and making the confirmation process more difficult.

To protect our customers, we are introducing a new behavior that will prevent the creation of a new verification for those IBANs that already have an in-progress verification. To this effect, we consider in progress any verification that is in a transient state.

In those cases, if you try to create a new verification for that IBAN, you will get an error, and no new verification will be created. If the in-progress verification is rejected, expires, or fails to be confirmed, customers will be able to send a new verification to the same IBAN.

We hope this new behavior will help customers reduce their costs and improve the general user experience by only sending one verification code and simplifying the flow.

The change will be effective:

• On June 25, 2024, in the sandbox environment.
• On July 22, 2024, in the production environment.

Removal of parameters in transaction listing:

Until now, the transaction listing endpoint presented the option to filter the returned list by concepts like operation_type, credit_debit, amount.cents, amount.currency. The idea was to provide a filtering grammar that would allow customers to produce complex queries over the endpoint.

After analysing the use of this endpoint, we are removing those parameters, and we are reevaluating how those filtering operations should be conducted in the future to make them a) more usable, b) more ergonomic and c) more performant.

The removal will be effective on July 22, 2024, and any future change to how transactions are filtered will be notified in a timely manner.

PD: We are cooking a lot of new stuff to make the processing of high-volume payment windows more performant. We will keep you posted as we improve the Devengo API in the coming months!