Supported Verification Methods
Energy Consumer Onboarding via Glow#
Organisations signed up to the Glow Data Service can onboard their own energy consumers to start accessing their smart meter data. Glow offers multiple onboarding journeys, including integration into your own front end.To onboard an energy consumer, you must:1.
Capture a subject, so the energy consumer can be identified later on. This can be an email address or a reference that uniquely identifies the energy consumer. This information will be used as their username in the Glow Platform.
2.
Verify the energy consumer.
3.
Capture their consent for their data to be accessed.
The Glow SDK does not facilitate steps 1 and 3 — you must incorporate these into your own front end to complete the sign-up process. Step 3 requires acceptance of Terms and Conditions. The Terms and Conditions APIs and Management document outlines how to present and manage your Terms and Conditions. Glow SDK Verification Methods#
The Glow IDV SDK offers two verification options, each providing fast, instant results.1.
MPXN + last 4 digits of in-home display (IHD) GUID — the energy consumer is verified upon providing their MPXN and the last four digits of their in-home display's GUID.
2.
Document upload — the energy consumer provides their MPXN and uploads a supporting document from a constrained list. The document is reviewed, and the energy consumer receives instant feedback on whether verification succeeded.
Method 1: MPXN + Last 4 Digits of IHD GUID#
The energy consumer enters their name, MPXN, and the last 4 digits of their in-home display's GUID. This lets them verify occupancy without uploading a document, using data already tied to the property's smart meter.The GUID is a 16-character code found on the in-home display given to an energy consumer by their supplier. It's registered against a property and can be retrieved from an MPXN database to compare against an address to prove residency.Data collected#
Last 4 digits of IHD GUID
Matching logic#
The address associated with the provided MPXN in an industry MPXN database is compared to the address associated with the provided GUID. If the two addresses match, verification succeeds.On mismatch#
The system returns an error stating that the details don't match what's on record.Result#
Method 2: Document Upload#
The energy consumer enters their MPXN, full name, and address, then uploads a piece of evidence proving they live at the property they're requesting data access for.Data collected#
Supporting document (file upload)
Document types supported#
| Document type | Criteria |
|---|
| Energy bill | Must be dated within the past 3 months. Name, address, and MPXN must match what the customer entered. |
| Tenancy agreement | Must be a current, valid agreement, showing name, date, and address matching what the energy consumer entered. |
| Driver's licence | Must be valid, showing a name and address that match what was entered. |
| Council tax bill | Must be for the current tax year, showing a name and address that match what was entered. |
Matching logic#
The extracted address information is compared to the address matched to the provided MPXN in an industry MPXN database. If the two addresses match, verification succeeds.On mismatch or unreadable document#
Depending on the issue, the system returns an error explaining what went wrong:A mismatch between an entered field and what's on the document (name, address, MPXN, etc.)
An image that's blurry or unreadable
A document that doesn't show the required information
A document that shows the required information, but does not meet the criteria (for example, an out of date bill)
A document that doesn't match the type that the energy consumer selected
Result#
Verification is instant. The energy consumer receives either an error message if verification failed, or a successful result and a Verifiable Credential — without leaving the IDV iframe.Modified at 2026-08-13 13:12:29
