Core Concept

Our platform manages the lifecycle of a payment through a small set of core REST API actions, providing you with a single, standardized integration layer for handling payments across multiple providers.

At a high level, the payment lifecycle is built around 3 primary actions and endpoints and post-decline fallback scenarios:

Creating a checkout
Tokenization
Creating an order
Fallback/Retry scenarios*

In addition to these core actions, the platform provides a set of payment lifecycle management endpoints that allow you to control and maintain transactions after authorization. These include actions such as manual capture (where applicable), cancellation, and refunds, depending on the payment flow and configuration.

From a merchant’s perspective, our API serves as a single, unified REST interface. Behind the scenes, we abstract and normalize the complexity of working with multiple Providers, translating standardized API calls into the native APIs of each PSP. This allows merchants to integrate once and operate across multiple providers seamlessly, without having to manage the differences between them.

*Fallback scenarios are handled by us and do not require additional API actions from your end. You can either use a default fallback configuration or adjust it to your needs. Find out more here.

On top of the core payment actions and fallback scenarios, the platform provides status updates that reflect the progress and final outcome of each transaction.

Payment status changes are communicated primarily through webhooks, allowing your system to be notified automatically when important events occur, such as authorization results, captures, cancellations, or refunds.

This approach ensures that your system can reliably track the state of each payment and react to changes in real time.