Skip to main content
Spirii sits between the driver’s payment and your bank account. From the moment a driver pays to the moment revenue lands with you, Spirii manages acquiring, VAT, settlement, and payouts.

​
The four payment channels

Payments on the Spirii platform work across four channels. Each brings drivers different payment options, and you different operational requirements.

In-app payments

Drivers pay through the Spirii app or your branded app. Spirii handles acquiring, VAT, and digital receipts as Merchant of Record.

In-person payments

Contactless card, Apple Pay, and Google Pay at the charger. Under turnkey, Spirii supplies the terminal, POS software, and acquiring; under PAAS you bring your own terminal and acquirer. The two can also be split.

Charge key billing

Fleet drivers tap an RFID card or virtual charge key. With Full Service billing, Spirii consolidates all sessions into a single monthly invoice to the fleet company.

Roaming settlement

Drivers from other networks charge on your stations, or your drivers charge on other networks. Spirii handles the cross-network invoicing and settlement.

​
Choosing a channel

Most public sites run several at once. For the full mechanics per channel (who the merchant is, who gets invoiced, when payouts land), see Billing and payout flows.

​
Where you sit in the flow

Which side of the platform you are on decides whether money arrives or leaves.

​
As a CPO

You receive a monthly payout by self-billing invoice, covering every session across the channels you have enabled: app, terminal, charge key, and roaming. Where you share revenue with site owners, Spirii splits the payout and routes it to each party directly.

​
As a fleet operator or eMSP

Your company receives one consolidated bill for all charging by your drivers, both on the Spirii network and across roaming partners. Where your employees charge at home, Spirii pays the reimbursement straight to their bank accounts.

​
Dependencies & limitations

  • Spirii is not always the Merchant of Record. It is on in-app and roaming, and on in-person under turnkey. Under in-person PAAS you keep your own acquiring agreement and stay the merchant, and on charge key billing it follows the billing service level.
  • Two of the four channels need hardware on the charger. In-person needs a Payter Apollo terminal; charge key billing needs an RFID reader. In-app and roaming run on infrastructure you already have.
  • Only in-person payments serve a driver with nothing installed. In-app does not need an account, because a driver can charge as a guest, but it does need Spirii Go or your branded app on their phone. Charge key billing needs a fleet or eMSP account, and roaming an account with the driver’s own eMSP.
  • Spirii invoices your fleet customers only at Full Service. Under Invoice Data Service you invoice them yourself from data Spirii aggregates; under No service Spirii records the session and settles roaming only.
  • Payout timing is not uniform. App, terminal, and charge key revenue pays out the following month. Roaming pays in the same month the roaming partner is invoiced.
  • In-person needs a Merchant ID per location. Spirii requests it from the PSP under turnkey, or you supply your own under PAAS.

Billing and payout flows

How money moves between drivers, Spirii, and you — from payment to payout.

Revenue sharing & automated payouts

How Spirii distributes revenue to CPOs, site owners, and subsidiaries.