General Pricing Terms

AS OF 25 FEB 2026
Note for existing customers with prior commercial terms: If you have an existing signed Order Form, pricing addendum, or other written commercial agreement with Faraday covering Platform fees, that agreement remains in effect until it expires, is replaced, or is amended in accordance with its terms. This published General Pricing Terms applies to the extent designated in your applicable Order Form, Customer-Specific Addendum, Dashboard billing acceptance, or other Faraday notice.
Applies to: Customers using the Faraday Charging Platform, subject to the applicable Regional Pricing Annex and any Order Form / Customer-Specific Addendum.
This Pricing Terms forms part of, and is incorporated into, the Charging Platform Terms (the “Terms”). Capitalized terms not defined here have the meanings given in the Terms.
Related legal documents:

1. Purpose, structure, and commercial hierarchy

This Pricing Schedule sets out Faraday’s commercial pricing framework for the Platform, including:

  • fee categories and fee components;
  • fee calculation rules;
  • monthly minimum mechanics (where applicable);
  • taxes/VAT treatment for Faraday-issued fees;
  • invoicing, deduction, and billing mechanics (high-level);
  • pricing region and billing currency concepts; and
  • the hierarchy between this Pricing Schedule, Regional Pricing Annexes, and customer-specific commercial documents.

This Pricing Schedule consists of:

  • Part I — Core Pricing Terms (Sections 1–15); and
  • Part II — Regional Pricing Annexes.

1.1 Commercial order of precedence

In the event of a conflict regarding fees, fee calculations, billing mechanics, or pricing applicability, the following order of precedence applies (highest to lowest):

  1. the applicable Order Form or Customer-Specific Addendum;
  2. the applicable Regional Pricing Annex;
  3. these Core Pricing Terms; and
  4. the Terms (for general framework matters only).

For clarity, this Pricing Schedule does not override the Terms except with respect to commercial pricing details expressly covered here.

2. Scope of this Pricing Schedule

This Pricing Schedule applies only to Platform fees and related billing mechanics charged by Faraday for use of the Platform.

It does not restate or modify the legal terms governing Platform access/use, service scope, Merchant of Record responsibility allocation, suspension/termination, data protection, liability, or other matters addressed in the Terms.

3. Pricing-specific definitions

3.1 Order Form

“Order Form” means a written or electronic ordering document, commercial proposal acceptance, dashboard-based checkout/acceptance flow, or other document/record issued or accepted by Faraday that identifies Customer-specific commercial terms for the Platform (including pricing, billing method, term, and/or deployment scope).

3.2 Customer-Specific Addendum

“Customer-Specific Addendum” means a written amendment, addendum, or commercial schedule agreed between Faraday and a specific Customer that supplements or overrides this Pricing Schedule and/or a Regional Pricing Annex for that Customer.

3.3 Pricing Region

“Pricing Region” means the region or country designation used by Faraday to determine which Regional Pricing Annex applies to the Customer’s charging operations, chargers, sessions, or commercial configuration.

3.4 Billing Currency

“Billing Currency” means the currency in which Faraday denominates and/or invoices its fees under the applicable Regional Pricing Annex, Order Form, or Customer-Specific Addendum.

3.5 Base Platform Session Fee

“Base Platform Session Fee” means a fixed Platform fee charged per Charging Session, where specified in the applicable Regional Pricing Annex or customer-specific commercial document.

3.6 Pay App Session Add-On Fee

“Pay App Session Add-On Fee” means an additional per-session Platform fee that may apply to Charging Sessions initiated through Faraday’s Pay App (including Pay App remote-start flows), as specified in the applicable Regional Pricing Annex or customer-specific commercial document.

3.7 MoR Fee

“MoR Fee” means a fee charged where Faraday is the Merchant of Record for the relevant transaction(s), which may be structured as:

  • a percentage of transaction amount,
  • a fixed fee per transaction/session,
  • a combined percentage plus fixed fee,
  • payment-rail-specific processing fee components, and/or
  • other MoR service fee components,

as specified in the applicable Regional Pricing Annex or Order Form.

3.8 Monthly Minimum

“Monthly Minimum” means a minimum monthly Platform fee amount (if any) applicable at the level specified in the relevant Regional Pricing Annex or customer-specific commercial document (for example, per charger, per site, or per account).

3.9 Minimum Top-Up Fee

“Minimum Top-Up Fee” means the amount charged, if any, to bring counted fees up to the applicable Monthly Minimum for the relevant billing period.

3.10 Billing Workflow

“Billing Workflow” means Faraday’s applicable invoicing, deduction, settlement, and billing configuration/process for the Customer, as communicated through the Dashboard, invoice/statement materials, or other written/electronic notice.

4. Pricing region, billing currency, and applicability

4.1 Pricing Region vs Billing Currency

Pricing Region determines which Regional Pricing Annex applies. Billing Currency determines the currency in which Faraday’s fees are denominated/invoiced.

For clarity, use of a currency (including EUR) does not by itself determine the Pricing Region.

4.2 Determination of applicable Regional Pricing Annex

Unless otherwise agreed in writing, the applicable Regional Pricing Annex is determined by Faraday based on the Customer’s relevant charging operations and billing configuration, as specified in:

  • the Order Form,
  • Customer-Specific Addendum,
  • Dashboard billing settings, and/or
  • Faraday’s published pricing designation.

4.3 Equivalent rate designations outside the named region

Faraday may designate certain jurisdictions as using another region’s rate levels (for example, “EEA-equivalent rates”) for commercial purposes without classifying those jurisdictions as part of that region for legal or regulatory purposes.

5. Pricing categories and fee types (framework)

Depending on the applicable Regional Pricing Annex and customer configuration, Faraday may charge one or more of the following fee types:

  • Base Platform Session Fee (fixed amount per Charging Session)
  • Pay App Session Add-On Fee (additional per-session fee for qualifying Pay App-initiated sessions, where applicable)
  • MoR Fee (where Faraday is Merchant of Record), which may include one or more of:
    • percentage fee component,
    • fixed fee component,
    • payment-rail-specific processing fee component,
    • MoR service fee component
  • Monthly Minimum / Minimum Top-Up Fee (where applicable)
  • Other fees only if expressly set out in a Regional Pricing Annex, Order Form, or Customer-Specific Addendum

Faraday may distinguish pricing categories based on factors such as:

  • personal/residential vs business organization use;
  • use of Faraday Pay App;
  • Merchant of Record designation;
  • Pricing Region / geography;
  • payment rail / processor configuration;
  • deployment type (e.g., pilot vs production); and
  • volume tiers (if agreed).

6. General fee calculation rules

6.1 Charging Session fee trigger

Where a Base Platform Session Fee applies, it is calculated per Charging Session recorded by the Platform for the applicable Customer and Pricing Region, subject to the relevant Regional Pricing Annex.

Unless otherwise stated in the applicable Regional Pricing Annex, Order Form, or Customer-Specific Addendum, a Base Platform Session Fee may apply regardless of:

  • whether the session is public or private;
  • authentication/authorization method (e.g., QR, RFID, Plug & Charge, dashboard/admin initiation, or similar methods);
  • whether the End User is charged or not charged; and
  • whether Faraday, Customer, or a third party acts as Merchant of Record.

6.2 Pay App Session Add-On Fee trigger

Where a Pay App Session Add-On Fee applies, it is charged for Charging Sessions initiated through Faraday’s Pay App (including Pay App remote-start flows), as identified in Faraday’s session records and billing classification.

A Regional Pricing Annex or customer-specific commercial document may further specify:

  • which session initiation methods qualify;
  • any exclusions; and
  • how mixed-use organizations (e.g., some sessions via Pay App and some not) are billed.

6.3 MoR Fee basis and structure

Where a MoR Fee applies, it is charged only where Faraday is the Merchant of Record for the relevant transaction(s), and may be structured as a percentage fee, fixed fee, combined percentage plus fixed fee, and/or payment-rail-specific fee components, as specified in the applicable Regional Pricing Annex or Order Form.

Unless otherwise stated, percentage-based MoR Fee components are calculated on the relevant End User transaction amount successfully captured/settled before deduction of MoR Fees.

6.4 Failed, aborted, zero-energy, and similar sessions

Unless otherwise stated in the applicable Regional Pricing Annex or customer-specific commercial document, Faraday’s default billing treatment is to exclude clearly failed or aborted sessions with no material energy delivery from per-session Platform fees. Faraday may apply reasonable operational thresholds and billing classification rules to determine whether a session is treated as having no material energy delivery.

6.5 Failed/aborted sessions and MoR Fee treatment

Exclusion of a session from per-session Platform fees (including any Base Platform Session Fee and Pay App Session Add-On Fee) does not, by itself, require Faraday to waive MoR Fee components to the extent Faraday has incurred third-party payment processing or payment-rail costs in connection with an attempted transaction.

The applicable Regional Pricing Annex, Order Form, Customer-Specific Addendum, or billing workflow may specify how failed, aborted, no-material-energy, low-energy, or similar session attempts are treated for MoR Fee components, including whether and to what extent such incurred costs are chargeable to Customer.

6.6 Currency and FX conversion

Fees are denominated in the Billing Currency stated in the applicable Regional Pricing Annex or Order Form.

If conversion is required (for example, where transaction currency differs from Billing Currency), Faraday may apply the conversion method specified in:

  • the applicable Regional Pricing Annex;
  • the Order Form / Customer-Specific Addendum; or
  • Faraday’s Billing Workflow/settings (if enabled and disclosed to Customer).

6.7 Rounding

Unless otherwise agreed:

  • fixed fees are charged to the stated minor unit (e.g., cents);
  • percentage fees are rounded to the nearest minor unit at the line-item or invoice level, as reasonably determined by Faraday’s billing system and applied consistently.

6.8 Invalid, duplicate, and test sessions

Faraday may exclude session records from fee billing where identified by Faraday (acting reasonably) as duplicate, test/internal, or invalid/corrupted records not representing actual chargeable operational sessions.

For clarity, session initiation method alone does not determine whether a session is excluded from fee billing.

7. Monthly minimum mechanics

Where a Regional Pricing Annex specifies a Monthly Minimum, the default interpretation is:

  1. The Monthly Minimum applies at the level specified in the applicable Annex (for example, per charger, per site, or per account).
  2. The Annex must specify which fee components count toward the Monthly Minimum.
  3. Faraday charges only the difference between the applicable Monthly Minimum and the counted fees (a Minimum Top-Up Fee), if any.
  4. Fee components excluded from counting toward the Monthly Minimum (if any) must be stated in the Annex.

For clarity:

  • Monthly Minimums are not charged unless expressly included in the applicable Regional Pricing Annex or customer-specific commercial document.
  • Unless the Annex states otherwise, MoR Fee components do not count toward the Monthly Minimum.

8. Taxes and indirect taxes (billing treatment only)

8.1 Fees exclusive of taxes

All fees in this Pricing Schedule and its Regional Pricing Annexes are exclusive of VAT and other applicable indirect taxes unless expressly stated otherwise.

8.2 Taxes on Faraday fees

Faraday will apply VAT or similar indirect taxes to Faraday-issued Platform fees where required by applicable law, based on the Customer’s billing country, tax status, and tax information provided by Customer.

Customer is responsible for providing accurate billing and tax information (including registration/VAT numbers where applicable) and for promptly notifying Faraday of changes to Customer’s billing address, tax registrations, or tax status that may affect invoicing or tax treatment.

8.3 MoR tax responsibilities

MoR-related tax responsibilities for End User charging transactions are governed by the Terms and the applicable commercial configuration. This Pricing Schedule addresses only the pricing and billing of Faraday’s fees.

9. Invoicing, deduction, settlement, and billing statements

9.1 Billing method

Faraday may use one or both of the following methods, as specified in the applicable Regional Pricing Annex, Order Form, Customer-Specific Addendum, or Billing Workflow:

  • Invoice model (Faraday invoices Customer); and/or
  • Deduction model (Faraday deducts fees from amounts otherwise payable to Customer, where supported by the payment/settlement configuration).

9.2 Billing frequency and accrual

Unless otherwise agreed, Platform fees accrue and are billed monthly in arrears.

A Regional Pricing Annex, Order Form, Customer-Specific Addendum, or Billing Workflow may provide for different statement, invoicing, deduction, or settlement cycles (including quarterly cycles), including where Faraday provides transaction settlement or profit-share reporting.

Unless otherwise stated in the applicable Regional Pricing Annex, Order Form, Customer-Specific Addendum, or invoice, invoices are due within thirty (30) days from the invoice date.

9.3 Billing statements

Faraday may provide invoice details, settlement statements, and/or dashboard billing reports showing, as applicable:

  • session counts;
  • Base Platform Session Fees;
  • Pay App Session Add-On Fees;
  • MoR Fee components (including percentage and/or fixed transaction components);
  • Monthly Minimum / Minimum Top-Up Fees;
  • taxes on Faraday fees; and
  • credits and adjustments.

Unless otherwise stated, fee calculations and billing classifications are based on Faraday’s billing records and relevant Platform/payment processor records, acting reasonably, subject to correction of clerical, calculation, or manifest errors under Section 9.4.

9.4 Billing disputes, corrections, and manifest errors

If Customer reasonably disputes a billed amount, Customer should notify Faraday within the period stated in the applicable Order Form, Customer-Specific Addendum, or Billing Workflow. If no period is specified, a commercially reasonable notice period applies.

Faraday may correct clerical, calculation, or manifest billing errors in a subsequent invoice or settlement statement, provided Faraday acts reasonably and, upon request, provides supporting detail for the correction.

Any other corrections or credits may be reflected in a subsequent invoice or settlement statement.

10. Customer-specific commercial terms and overrides

Faraday may agree customer-specific commercial terms in an Order Form or Customer-Specific Addendum, including:

  • custom rates;
  • custom fee components or fee structures;
  • waivers/modifications of Monthly Minimums;
  • promotional pricing;
  • custom billing cycles;
  • custom MoR Fee structures (including percentage/fixed components);
  • volume tiers;
  • pilot pricing;
  • country-specific payment cost treatment; and
  • custom settlement/profit-share cycles.

Such terms override this Pricing Schedule and any applicable Regional Pricing Annex only to the extent expressly stated.

11. Regional Pricing Annexes

Faraday may publish and update Regional Pricing Annexes for specific regions and/or countries.

Only the Regional Pricing Annex(es) expressly designated for the Customer or relevant charging operations apply. Each applicable Regional Pricing Annex forms part of this Pricing Schedule as of its stated effective date.

If more than one Regional Pricing Annex could apply to the same charging operations, the annex expressly designated in the applicable Order Form, Customer-Specific Addendum, or Faraday billing configuration will control.

Regional Pricing Annexes may include, for example:

  • country-specific annexes; and/or
  • regional annexes with country-specific tables.

12. Pricing updates and notice

Faraday may update this Pricing Schedule and/or any Regional Pricing Annex from time to time in accordance with the Terms and applicable law.

Unless a shorter period is required by applicable law, tax/regulatory changes, or payment processor changes outside Faraday’s reasonable control, Faraday will provide at least thirty (30) days’ prior notice before a pricing change takes effect, via the Dashboard, email, website publication, or other electronic notice.

The notice period runs from the date Faraday provides the relevant notice by Dashboard posting, email, website publication, or other electronic notice.

Customer-specific pricing in an active Order Form or Customer-Specific Addendum remains in effect for the stated term of that document unless that document expressly permits earlier pricing changes.

13. Governing law and legal interpretation

The governing law and jurisdiction for disputes relating to the Platform and this Pricing Schedule are determined by the Terms and/or the applicable Order Form, unless expressly stated otherwise in a customer-specific commercial document.

14. Out of scope (interpretive clarification)

This Pricing Schedule does not define or modify:

  • Platform feature scope or service descriptions;
  • legal Merchant of Record responsibility allocation;
  • suspension, termination, acceptable use, or security obligations;
  • data protection/DPA/privacy terms;
  • disclaimers, liability limitations, indemnities; or
  • End User tariff terms, refund policies, or consumer disclosures.

Those matters are governed by the Terms and/or other applicable Faraday documents.