Large networks can't afford a single driver who can't pay
At scale, payment friction isn't a minor inconvenience. It's hundreds of abandoned sessions per week. Monta gives your network the flexibility to accept every payment method, across every market, so every driver can start a session instantly.
What payment gaps cost a network running thousands of charge points
Session loss
Every unsupported payment method is a session that never starts
Multi-market operations
Each country expects a different payment method as the default
Operational overhead
At scale, every failed payment creates a support ticket
Making it simple to start a charge, no matter how the driver wants to pay
Monta supports every major payment method: card, digital wallet, payment terminal, and RFID; so no driver is left standing at a charger that won't accept their payment.
QR & AppClips / WebInstant
Just tap your phone to the sticker for easy and smooth payment: Apple Pay, Google Pay, or credit card.
Payment terminals
Integration with Payter and Nayax to ensure card payments are widely accepted at any charger.
RFID cards
In-network and out-of-network cards activate charges instantly. Works across roaming partners on the Monta network.
In-app
Start a charge via the Monta app or white-label app using Monta Wallet, Apple Pay, or Google Pay.
Local payment apps
MobilePay, Vipps, and Twint supported natively, the apps drivers in Denmark, Norway, and Switzerland already use.
Drivers pay exactly what they charged. Not a penny more.
Less money tied up during charging
The hold grows only as energy is delivered, not as a large upfront block. Drivers with tighter card limits won't get blocked by an inflated pre-auth.
Funds released faster after the session
No excess holds, no waiting days for a bank to release the difference. The driver sees the holds as charging progresses, with only the final amount captured.
Failed sessions cancel the hold immediately
If charging fails, the reservation cancels immediately, no unnecessary freeze on the driver's card for days.
Card is verified. A small initial pre-authorisation confirms the payment method and starts the session.
As energy is delivered, the reserved amount grows in small steps, minute by minute. No large upfront block on the driver's card.
The charger reports total kWh delivered. The last auth increment may be slightly above the actual cost.
Capture is sent for the exact session cost. Any difference between the final auth and the captured amount is released back to the driver immediately.
You control what's available. Monta handles the rest.
Payment configuration lives in your operator settings. Enable the methods that fit your network. From that point, every driver session resolves payment automatically with no manual step required at the charger.
Configure payment methods for your network
Driver arrives and pays in seconds
Revenue flows in, reconciliation is automatic
FAQs
Can we choose which payment methods to enable on our network?
Yes. Payment configuration lives in your operator settings in MontaHub. You enable the methods that fit your network, by market, by site type, or across the board. Once configured, every driver session resolves payment automatically with no manual step at the charger.
Do we need to set up our own contract with Stripe or Adyen?
No. Monta has existing partnerships with Stripe, Adyen, and Wise. You don't need to negotiate your own PSP contracts or manage the integration, Monta handles payment acquiring on your behalf as part of the platform. If you already have a preferred PSP relationship and want to bring your own, that's also a conversation we can have during onboarding.
What exactly is incremental authorisation and how is it different from a standard pre-auth?
A standard pre-auth places one large block on the driver's card upfront (e.g. €50) and releases the excess after the session ends. With incremental authorisation, Monta places a small initial hold and increases it in steps as energy is delivered, minute by minute. At session end, the capture is sent for the exact amount charged, and any difference is released immediately.
What happens if a payment fails mid-session?
If a session fails before charging starts, the pre-authorisation is cancelled immediately, no hold remains on the driver's card. If a payment failure occurs during an active session, Monta's payment layer handles the fallback logic and captures what was delivered up to that point. Failed payment events are logged and visible in Monta Hub.
Are MobilePay, Vipps, and Twint included, or do we need separate agreements?
These are supported natively within Monta, you don't need separate agreements with MobilePay, Vipps, or Twint. They're available as part of the platform for operators running in Denmark and Finland (MobilePay), Norway (Vipps), and Switzerland (Twint).
Can drivers use RFID cards from other networks on our charge points?
Yes. Monta supports both in-network RFID cards and out-of-network cards through roaming partners. Payment and settlement flow through the roaming agreement, your charge point accepts the card, and revenue is settled through the established roaming terms.
How quickly does revenue from driver payments reach our account?
Payment is captured at session end and flows into your Monta wallet. Settlement timing to your bank account depends on your payout schedule configuration, typically on a daily or weekly basis.