∕∕ CpoPay
Home/Designing payments for a variable final amount

PAYMENT GUIDES

Designing payments for a variable final amount

Authorization is not the same as capture. Compare card preauthorization with payment-first local methods.

Let’s talk

CpoPay · Payment design guide

One payment lifecycle.
Connected end to end.

Authorization is not the same as capture. Compare card preauthorization with payment-first local methods.

Create

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

Confirm

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

Capture

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

Reconcile

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

Representative local payment ecosystems. Availability is confirmed per country, provider, merchant entity and use case; listed methods do not imply universal live coverage.
Enter developer center

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