This page explains the fundamental principle of how transactions such as exchanges, withdrawals, transfers, and similar operations are processed in the Fintegence Partner API. Understanding this asynchronous, queue-based model is crucial for building a reliable and robust integration.
To ensure high availability and performance, the API does not process operational transactions in real time. Instead, every transaction request follows a consistent asynchronous flow.
The Most Important Rule to Remember
A 2xx success response only confirms that your request was accepted into the processing queue. It does not mean the transaction was successful. Business logic errors such as insufficient funds, compliance failures, or invalid operational conditions are only detected during the background processing stage.
To build a reliable system, you should always track the final status of every transaction.
1. Use Webhooks (Recommended)
This is the most efficient method. Subscribe to our Webhooks, and the system will send a real-time notification as soon as a transaction reaches its final status.
2. Poll for Status (Alternative)
If webhooks are not an option, periodically call the relevant details endpoint and check the status field until it reaches a terminal state.
3. Design Your UI Accordingly
When a user initiates a transaction, immediately display a pending or processing state in the interface. Only mark it as completed or failed after receiving the final status through a webhook or polling.
A typical transaction integration should follow this pattern:
1.
Submit the transaction request.
2.
Store the returned transaction identifier.
3.
Mark the operation as pending in your internal system or UI.
4.
Wait for a webhook or poll the relevant details endpoint.
5.
Update the final state only when the transaction reaches a terminal status.
Asynchronous Processing in Practice
This model applies broadly across the Fintegence API, including exchanges, SEPA transfers, crypto withdrawals, internal transfers, orders, and Travel Rule review flows.
What's Next?Now that you understand the asynchronous processing model, the next step is to implement status tracking via Webhooks.
