Payment gateway & API

Connect payment to your own experience.

Think of checkout as part of your website or app. An API-based integration handles payment states in a way your system can act on.

How it works

Payment gateway & API

Integration shaped around your flow

Event-based payment state model

Controlled path from test to live

How it works

Connect payment to your own experience.

Think of checkout as part of your website or app. An API-based integration handles payment states in a way your system can act on.

Create the payment context
Move the customer to checkout
Track the result in your application

Where it fits

Build checkout into the journey you already own.

A digital service can start payment from its own account or order flow, then show the customer a clear result.

A growing store can keep order and payment references together, so teams know what happened before fulfilling an order.

A custom application can plan its test cases around success, failure and an interrupted checkout before going live.

Before you integrate

Before you integrate

What should be defined first?

Map when an order is created, when payment starts, and which result allows the order to move forward. That decision guides the interface and the integration.

How should a failed payment appear?

Give the customer a plain explanation and a safe way to retry. Keep an unsuccessful attempt distinct from a completed order in your own records.

Where are the API specifications?

This public page describes the intended payment journey. Verified endpoints, credentials and integration terms will be published with the connected product source.

MANUELL

Let's choose the right payment route.

Tell us which of the three paths fits your business.

Let's talk