∕∕ CpoPay
Home/Built for the people who build the platforms.

DEVELOPER CENTER

Built for the people
who build the platforms.

A clear integration model. Predictable payment states. Session-linked references. Design your payment flow with the team that understands your use case.

payment-request.json
// Illustrative contract · not a live API
POST /example/payments

{
  "session_reference": "cs_demo_001",
  "market": "DE",
  "currency": "EUR",
  "amount_minor": 20000,
  "method": "card"
}
Illustrative contract · not a live API

01 / INTEGRATION

Integration guide

A clear integration model. Predictable payment states. Session-linked references. Design your payment flow with the team that understands your use case.

  1. Create

    Create a payment request with your CPMS session reference, market, currency and amount.

  2. Confirm

    Wait for a verified payment status. QR and wallet flows may confirm asynchronously.

  3. Capture

    For eligible card flows, capture the final session amount. Local methods may require payment first.

  4. Reconcile

    Match session references to payment records, provider fees and settlement reports.

02 / PAYMENT STATES

Payment states

created → pending → confirmed
failed · expired · refunded

Illustrative state model. Final statuses and transitions are defined in your provider-specific integration contract.

03 / WEBHOOKS

Webhook design

Validate webhook signatures, prevent replay and use idempotent processing before updating session or financial state.

{
  "event": "payment.confirmed",
  "event_id": "evt_example_001",
  "session_reference": "cs_demo_001"
}

Illustrative contract · not a live API

04 / SANDBOX

Sandbox access

Request the verified API specification, sandbox credentials and supported-method matrix from the integration team. Examples on this page do not send network requests.

Request integration pack

THE NEXT MOVE IS YOURS

Build your next
payment advantage.

Discuss your CPMS architecture, launch markets and commercial model with our team.

Let’s talk