∕∕ CpoPay
Home/One orchestration layer. Every payment operation.

PAYMENT INFRASTRUCTURE

One orchestration layer.
Every payment operation.

Standardize the payment lifecycle above your providers. Keep charging logic in your CPMS and payment complexity in a dedicated control plane.

Let’s talk
ONE API / MULTIPLE PROVIDERS•••
Your CPMS

Sessions · Tariffs · CDRs

01
CpoPay02

Payment orchestration

AuthorizeCaptureRefundAllocate
Policy · Risk · Reconciliation
PSPLocal acquiringLocal rails
PSPs & local acquirers

Cards · Wallets · Account-to-account

Session contextPayment events
01

Accept locally

Cards, wallets and local payment methods, aligned to the markets you serve.

Explore
02

Orchestrate intelligently

Bring payment requests, statuses and refunds into one integration model.

Explore
03

Reconcile with clarity

Connect payment records, fees and settlement references to charging sessions.

Explore

PAYMENT LIFECYCLE

One payment lifecycle.
Connected end to end.

01 / Create

Create

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

CPMSCpoPayPSP

BUILT TO CONNECT

Embed payments.
Keep your platform in control.

White-label payment orchestration for CPMS providers. Link OCPP/OCPI session references and CDRs to payment records without moving charger control into the payment layer.

Explore
CPMS / CPO
↓
CpoPay
↓
CardsWalletsLocal QR

CHARGING PAYMENT OPERATIONS

Four workflows.
One session-aware payment layer.

01

Preauthorize → capture → reverse

Session-based authorization

For eligible card flows, capture the final session amount and request reversal of unused authorization. Issuer release times vary. QR and wallet flows follow their own pay-first / refund logic.

02

Eligibility → refund → evidence

Refund capability routing

Make refund eligibility, limits and timeframes explicit before payment. Preserve session evidence and distinguish card chargebacks from payment-method complaints.

03

Allocate → reconcile → settle

Multi-party allocation

Create order-level allocations with legal-entity and fee references. Settlement execution and any safeguarded fund arrangements remain provider- and contract-specific.

04

Market → method → confirmation

Local payment orchestration

Expose familiar local methods with a common API while retaining differences in authentication, expiry, asynchronous confirmation and refunds.

ABOVE THE PAYMENT RAILS

Provider execution.
Platform-level orchestration.

PSPs execute acceptance, authentication and settlement under their supported services. CpoPay coordinates these capabilities with charging-session events, refund policies, allocation rules and audit requirements through one integration layer.

Dispute evidence operations

Link consent, payment references and CDR records to support time-bound dispute responses.

Financial & tax data boundaries

Separate merchant ledgers, fees and tax references; keep local tax obligations with the responsible entity.

FAQ

A little more clarity.

Is CpoPay a charging management platform?+

CpoPay focuses on payment infrastructure for CPMS providers and CPO businesses. Your CPMS continues to manage chargers, sessions and energy.

Can one payment flow work in every country?+

The integration pattern can be shared, but payment methods, merchant onboarding, settlement and regulatory requirements vary by market and provider.

How is a charging session connected to a payment?+

A shared session reference links payment events to the CPMS. Your integration should handle asynchronous status updates, duplicate notifications and final reconciliation.

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