Special case for 202 code

Modified on Thu, 22 Jul, 2021 at 2:21 PM


In this article we demonstrated an example of the async flow where a processing time for an account takes more than 210 seconds. 


Whenever the API connects to the bank and faces a new flow that is not supported (for example, if the bank is prompting now a new banner offering a seasonal product), your request could be in a suspended state and you would get the code 202 OPERATION_DISPATCHED.


In the eventuality this would happen, our uptime team is alerted in real time and gets in action by verifying what was unexpected in the flow, and built the support for this new flow right away.


For most of these special cases, the new support is built in less than 15 minutes, but there are cases where it takes more time due to complexity. For that reason, we recommend to have a 30 minutes timeout on your side, to stop calling the async endpoint for a specific request.


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article