Define market responsibilities
Document the merchant of record, acquiring provider, KYC/AML responsibilities and data-processing roles before launch.
ExploreEurope / GBP
United Kingdom
Local payments.
Plan a familiar card and digital-wallet experience, with clear merchant identification, refund handling and session references.
Currency
GBP
Local ecosystem
Visa · Mastercard · Apple Pay · Google Pay · Pay by Bank
Market readiness
Confirm on enquiry
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
What to confirm before entering a new market
Plan the integration around the payment method.
Wait 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
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.
CPMS / TECHNICAL & COMMERCIAL
Start a technical conversation.
Send your CPMS architecture, target countries and payment priorities. Our team will help scope the integration and commercial model.