Payment Status & Webhooks

Once a payment has been initiated and processed, you will be informed about transaction outcome through payment statuses and webhook notifications.

Payment statuses represent the current state of a transaction during its lifecycle. Depending on the payment flow, a payment may go through several status changes until it reached a definite status.

In addition to synchronous API responses, the you will receive webhook notifications to inform the your system about important payment events. This allows to reliably track payment progress and update the transaction on your end accordingly.

Webhooks are particularly useful for handling asynchronous events such as authentication flows, delayed authorizations, or post-payment operations.

Payment Status

Each order is associated with a status that reflects the current state of the payment.

Some typical payment statuses include:

• Authorization successful – the payment has been successfully authorized by the payment provider.
• Capture successful – the funds have been captured and the transaction is completed.
• Authorization declined – the payment was rejected or could not be completed.
• Refund successful – the payment was successfully refunded after capture.

The exact status progression may vary depending on the payment method, PSP behavior, and your merchant configuration.

Webhooks

Our platform concept regarding status updated is built around asynchronous notifications. Webhooks allow us to notify your system automatically when a payment event occurs.

When a relevant event happens (for example authorization, capture, refund, or cancellation), we will send an HTTP request to the webhook endpoint configured in your account.

This mechanism enables to:

• update order status in your system
• handle asynchronous payment events
• monitor post-payment operations

To receive webhook events, you must configure a webhook endpoint during the integration setup and decide which events you want to subscribe to. You can find more details about webhooks in a dedicated documentation section here.