Transaction Processing

This page explains the fundamental principle of how transactions (such as exchanges, withdrawals, and transfers) are processed in the P100 Partner API. Understanding this asynchronous, queue-based model is crucial for building a reliable and robust integration.

Our Asynchronous-First Approach

To ensure high availability and performance, our API does not process transactions in real-time. Instead, every transaction request you send follows a consistent, asynchronous flow visualized below.

The Most Important Rule to Remember

A 2xx success response only confirms that your request was accepted into our processing queue. It does not mean the transaction was successful. Business logic errors, such as "Insufficient Funds," are only detected during the background processing stage.

How to Build a Resilient Integration

To build a reliable system, you must track the final status of every transaction. Here’s how:

1. Use Webhooks (Recommended)

This is the most efficient method. Subscribe to our Webhooks, and we will send you a real-time notification as soon as a transaction reaches its final status (SUCCESSFUL or FAILED).

2. Poll for Status (Alternative)

If webhooks aren't an option, you can periodically call the relevant "Get Details" endpoint (e.g., GET /v1/exchange/details/:exchangeId) and check the status field in the response until it becomes final.

3. Design Your UI Accordingly

When a user initiates a transaction, immediately display a "Pending" or "Processing" state in your interface. Only update the UI to "Completed" or "Failed" after you receive the final status via a webhook or polling.

What's Next?

Now that you understand our asynchronous model, learn how to implement the recommended tracking method in our Webhooks Guide.

Transaction Processing

Our Asynchronous-First Approach#

How to Build a Resilient Integration#

Our Asynchronous-First Approach

How to Build a Resilient Integration