Payment Service Providers

The Opportunity

Every charging session is a commercial transaction. In public charging, that transaction happens between a stranger and a machine — which means it must be frictionless, secure, and support every payment method the driver expects. GreenFlux supports multiple payment models and is designed to integrate with Europe's leading PSPs at two levels: terminal-side (PSP manages the payment terminal; GreenFlux initiates and terminates the session) and CPMS-side (GreenFlux manages the full payment flow via PSP API, covering tokenisation, authorisation, capture, and refund). Operating across 38 European countries means handling iDEAL, Bancontact, SEPA Direct Debit, and regional card schemes alongside Visa and Mastercard. The CDR API provides session-level records as input for invoicing, reconciliation, and chargeback management.

Use Cases

• Large CPO networks process millions of transactions per month across multiple countries via a single PSP integration.
• Hospitality and retail CPOs enable guests to pay for charging with the same contactless terminal used at reception.
• Fleet EMSPs issue consolidated invoices to corporate customers with per-vehicle breakdowns from CDR data.

Example Integration

# 1. Register a tokenised card from Adyen/Stripe/Mollie in GreenFlux
PUT /payment/app-tok-driver-8812/external
{
  "provider": "adyen",
  "providerToken": "8415XXXXXXXXXXXX",
  "cardBrand": "VISA",
  "last4": "4242",
  "expiryMonth": 12,
  "expiryYear": 2028
}

# 2. Before session: show the driver the price
GET /tariff/app-tok-driver-8812/evse/loc-brussels-042/evse-1

# 3. Start the session — GreenFlux authorises against the stored PSP token
POST /v2.1/session/start
{
  "appToken": "app-tok-driver-8812",
  "evseUid": "evse-1",
  "locationId": "loc-brussels-042"
}

# 4. After session: pull CDR for PSP settlement
GET /cdrs?appToken=app-tok-driver-8812&sessionId=sess-9931

Authentication, base URLs, and sandbox access at developer.greenflux.com.