Payments
Keep your gateway, connect EVCCAT
For organizations that must collect via their own provider, attach the gateway to wallet top-up flows.
Key benefits
Collection control
Keep your provider and banking relationship.
Local fit
Integrate gateways suited to your market.
CSMS continuity
Top-ups remain tracked in EVCCAT despite the external provider.
How it works
The custom payment gateway lets an organization use its own collection provider for wallet top-ups — for example CMI — instead of a single generic flow. Some organizations face banking, local or contractual constraints. Connecting their gateway avoids forcing a provider incompatible with their model.
- 1
Choose the gateway
The organization defines the collection provider to use.
- 2
Connect wallet flows
Digital top-ups are routed through that gateway.
- 3
Track in EVCCAT
Operations remain visible on the platform side.
In the EVCCAT platform
The organization's gateway is attached to wallet top-up flows. Digital top-ups then go through that provider while remaining visible in EVCCAT.
Use cases
Local provider
An organization uses CMI or a regional equivalent for collection.
Enterprise constraint
The finance stack requires an already-contracted provider.
FAQ
The module is designed for wallet top-ups via the organization's gateway.
No. It defines the collection channel; payment methods remain managed in their module.
See what EVCCAT can bring to your charging network
Talk with our team about your infrastructure, operations and monetization needs.