User creates app account
User connects charger to app account
User inputs address and MPAN
Check user eligibility for flex
eligibleineligible
User provides informed consent to T&Cs and access to boundary meter data
User finishes set up and enters proposition
Legacy onboarding flow
You need to collect two separate consents from each user:
- Terms & Conditions: the user agrees to participate in the flexibility proposition. Store a record of this agreement.
- Boundary meter consent: the user allows Axle to access data from their site’s boundary meter. Save the timestamp of this consent; you’ll send it to us when you onboard the site.
Address collection
An MPAN (Meter Point Administration Number) is required for eligibility checks and participation in a proposition. We use the address to get a user’s MPAN. You may already be collecting the user’s address but our purpose built address lookup flow is optimised for matching to an MPAN.Collecting addresses
Learn how to implement an address collection workflow
Get MPAN from address
Learn how to retrieve meter details
Eligibility
Use the check-eligibility endpoint to find out which propositions a site qualifies for, to determine whether to proceed with the user proposition. Pass the MPAN, and optionally a charger model.Check eligibility
Check the eligibility of a site without persisting any data.
Consent
Once you’ve identified an eligible user, collect two consents before onboarding them. You can ask for both on the same screen, but each needs its own checkbox: don’t bundle boundary meter consent into the T&C acceptance.1. Terms & Conditions
The user agrees to participate in the flexibility proposition. This is typically an update to your Terms & Conditions that users must accept before onboarding. Store a record of when the user accepted, and which version of the terms they accepted. You keep this record; you don’t send it to Axle.2. Boundary meter consent
The user allows Axle to access data from their site’s boundary meter (the meter identified by their MPAN). We use this data as proof of delivery for flexibility events. Save the timestamp of when the user gave this consent. You’ll send it assite.gave_boundary_meter_consent_at when you onboard the site in the next step, and onboarding fails without it.
Next Steps
Once you’ve collected:- MPAN: from the address lookup
- Terms & Conditions record: stored on your side
- Boundary meter consent timestamp: to send as
site.gave_boundary_meter_consent_atwhen you onboard
Smart Charging Integration
Start onboarding eligible users to Smart Charging
Flex Lite Integration
Start onboarding eligible users to Flex Lite

