Walk-in: Payment Flow

[dubeyAyush]

The payment status is changed here:

https://github.com/Beckn-One/DEG/blob/405fd47f7f209f84f94169e58a3cc8832ee0431a/docs/implementation-guides/v2/EV_Charging_V0.8-draft.md?plain=1#L1769

This is on_confirm API.

As it's a BPP lead payment (as the user journey desc it's UPI payment) no BPP VPA or BPP's payment information is shared in the API

Also, the payment confirmation should have been shared in an on_status call by BPP (and the payment status should have been updated in confirm api) but no such API call is shown.

Requesting to please improve this part

[anandp504]

@dubeyAyush The payments are going to be performed through a payments link. Here is an example. https://github.com/Beckn-One/DEG/blob/draft/docs/implementation-guides/v2/EV_Charging_V0.8-draft.md?plain=1#L1783. We will not take the bank account number details or UPI vpa details as part of the payments object.

[dubeyAyush]

But then in cases of over charge and under charge how will we know who owns the payment?
@ravi-prakash-v need your help here.

The payment details of customer and BPP would be needed to ensure cases of under charge and over charge are resolved.

[ameetdesh]

(Discussed in NBSL - FIDE meeting on 5 Nov 2025)
Ayush is saying there is a missing on_status API call between on_init & confirm where BPP returns the same order object except the order ID, but confirming that the payment is PAID. Without such confirmation, there is no rationale to proceed with the order confirmation in most common cases.

An issue should be created to correct this, and example json added.

Next Actions:

• NBSL team member to create a PR with on_status section in the right place, example json.
• Add Ravi, Anand as reviewers.