Clarification & Field Mapping for Onboarding API (Beckn v2 – Energy Program Onboarding)

[siddharth584]

Description:
For the Onboarding API in Beckn v2, specifically during the onboarding of a user into an energy program offered by an Energy Program Provider, there is ambiguity regarding how certain critical attributes should be represented and where they should be passed in the confirm request.

We request clarification and/or suggested standard mappings for the following items:

Consumer Identifier (Consumer Number / Account Number)

How should this be represented in the confirm request payload?

Mobile Number (Registered Phone Number of the User)

Where should the user’s mobile number be carried in the confirm request?

User Type: Consumer vs Prosumer

How should we indicate whether the user is a consumer (only consuming energy) or a prosumer (both generating and consuming energy)?

Because this information is not clearly defined in the current API contract/specification, there is implementation uncertainty on where to place these values in a standard Beckn v2-compliant onboarding implementation.

Context: When a user is onboarded to an energy program offered by an Energy Program Provider via the Beckn v2 Onboarding API, the confirm request should clearly capture three critical attributes about the user:

Consumer Number (Consumer Identifier) – This is the unique identifier assigned to the user by the Distribution Company (DISCOM) or Energy Provider (for example, the electricity consumer number, account number, or meter-linked identifier). This value is used for:

Mapping the user to their physical connection or meter, and

Enabling accurate billing, settlement, and reconciliation for the energy program.

Mobile Number – This is the phone number registered with the program and used for. This field is necessary because the user may not know the existing registered mobile number and may choose a different mobile number to register themselves during onboarding:

Sending OTPs and transactional notifications,

Communicating program updates 

User Type (Consumer vs Prosumer) – This indicates whether the user:

Only consumes energy from the grid (CONSUMER), or

Both generates and consumes energy, e.g. via rooftop solar or other generation assets (PROSUMER).