Skip to main content
Every charging session ends with money moving from the driver to you, with Spirii in the middle handling acquiring, VAT, settlement, and payouts. How it plays out depends on who operates the chargers, who owns the site, and whether Spirii holds the acquiring agreement.

​
The transaction flow

1

Driver pays

The driver pays Spirii directly at the tariff you’ve set, using the app, a contactless terminal, or a stored payment method.
2

Spirii processes the payment

Spirii charges the driver’s payment method, applies the correct VAT for the charger’s country, and issues a receipt.
3

Spirii pays you

At the end of the billing period, Spirii pays you for the energy consumed via a self-billing invoice, net of platform and payment fees.
The commercial relationship runs between the driver and Spirii, and between Spirii and you. You do not invoice roaming partners or eMSPs for sessions Spirii collected on, and they do not invoice you.

Payment flows

How each payment channel (app, terminal, charge key, and roaming) moves money into your account.

​
Payment channel comparison

Spirii supports four payment channels for CPOs and site owners. Each captures a different type of driver and requires different infrastructure. Most public CPOs enable several channels on the same location.

​
Who pays whom

These are the platform’s roles seen from the money side. For what each one is, see Platform overview.

​
Who is the merchant

When Spirii acts as Merchant of Record (MoR), it buys the energy from you and resells it to the driver at the moment of the transaction. You are paid for the energy, and Spirii carries what comes with being the seller. Spirii is the MoR on in-app, charge key, and roaming sessions, and on terminal sessions where it holds the acquiring agreement.

Spirii handles

  • Acquiring and card processing (via Stripe and other PSPs)
  • Chargebacks, disputes, and refunds
  • PCI-DSS compliance for the cardholder data environment
  • VAT calculation and local reporting in each country of operation
  • Automated digital receipts to drivers
  • Pre-authorisation and capture on the driver’s payment method

You handle

  • Setting the charging tariff
  • Providing the physical infrastructure (chargers and locations)
  • Receiving your monthly payout from Spirii

​
VAT

Spirii reports and remits VAT in each country where your chargers operate. Your payout is net of VAT: the VAT collected from the driver is not passed on to you, and goes directly to the relevant tax authority instead.

​
When you are the merchant

In PAAS (Platform as a Service) mode you bring your own acquiring agreement and stay the MoR for payment terminal sessions. On those sessions:
  • Card funds reach you directly from your payment service provider (PSP)
  • You carry PCI-DSS self-assessment as a merchant
  • You handle disputes and refunds for your drivers
  • You report VAT yourself
  • You manage peer-to-peer roaming agreements and settlement with eMSPs
  • You manage charge key billing and settle your own mobility sessions
Spirii still provides the platform, the POS software, and the session data, but does not touch the financial flow for those sessions.

​
Common setup scenarios

How the parties relate, and how money flows between them, depends on who operates the chargers and who owns the site. Each of these has a page of its own.
The CPO operates the chargers and accepts payments. Spirii collects revenue from drivers across app, terminal, and roaming sessions, and pays the CPO.
A site owner (landlord, retailer), also called a charge station owner or CSO, owns the location the CPO operates on. Spirii splits the payout and pays each party directly, on a percentage or per-kWh share you set in Spirii Connect. See Revenue sharing.
A fleet gives charge keys to its employees, and Spirii invoices the fleet monthly for everything they charge. An eMSP can hold the billing relationship with its own fleet customers instead, in which case Spirii invoices the eMSP only for sessions on chargers it does not operate as a CPO. See Charge key billing.
A fleet reimburses employees for electricity used at home. Spirii produces the expense reports, and payment runs through the fleet’s payroll or a licensed PSP. See Home charging reimbursement.

​
Dependencies & limitations

  • Payout timing is not uniform. App, terminal, and charge key revenue pays out the following month. Roaming pays in the same month Spirii invoices the roaming partner — so a month’s income arrives in two pieces.
  • Not every session earns a payout. Sessions under 0,2 kWh, sessions running past seven days, free and voucher charging, and terminal sessions where you hold the acquiring are all excluded. The specification file with each payout names the reason per session. See Understanding your payout.
  • Fees are not netted line by line. The self-billing invoice carries your revenue; Spirii’s platform and payment fees arrive on a separate invoice. Neither document is the full picture on its own.
  • Spirii invoices your fleet customers only at Full Service. Under Invoice Data Service you invoice them yourself from data Spirii aggregates, and under No service Spirii records the session and settles roaming only. See Charge key billing.
  • Spirii does not pay out ahead of the funds. Your payout follows the money Spirii has collected, so it does not carry cash flow risk on your behalf.

In-app payments

Spirii is always the MoR for app-based charging sessions.

In-person payments

Choose between Spirii acquiring (turnkey) and your own acquiring (PAAS).

Understanding your payout

How to read a self-billing invoice and reconcile it against Connect.