Define market responsibilities
Document the merchant of record, acquiring provider, KYC/AML responsibilities and data-processing roles before launch.
ExploreSouth America / BRL
Explore Pix for local QR-based payment. Confirm expiry, payment confirmation and refund handling before linking a payment to charging.

Representative local payment ecosystems. Availability is confirmed per country, provider, merchant entity and use case; listed methods do not imply universal live coverage.
BEFORE YOU LAUNCH
Document the merchant of record, acquiring provider, KYC/AML responsibilities and data-processing roles before launch.
ExploreExplore Pix for local QR-based payment. Confirm expiry, payment confirmation and refund handling before linking a payment to charging.
ExploreConnect payment records, fees and settlement references to charging sessions.
ExploreWait for a verified payment status. QR and wallet flows may confirm asynchronously.
For eligible card flows, capture the final session amount. Local methods may require payment first.
Enter developer centerFAQ
CpoPay focuses on payment infrastructure for CPMS providers and CPO businesses. Your CPMS continues to manage chargers, sessions and energy.
The integration pattern can be shared, but payment methods, merchant onboarding, settlement and regulatory requirements vary by market and provider.
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
Discuss your CPMS architecture, launch markets and commercial model with our team.
CPMS / TECHNICAL & COMMERCIAL
Send your CPMS architecture, target countries and payment priorities. Our team will help scope the integration and commercial model.