Requirement of UPI transaction id

[biodatanet]

To facilitate UPI-enabled transactions, the following structural adjustments are proposed to the existing payment flow. This approach addresses the requirement for unique identifiers when an acquiring bank is absent (e.g., BHIM as a BAP) and ensures support for settlement and refund scenarios.

Proposed Technical Logic
Payment Object Enhancement: A new field, upitransactionid, will be introduced within the init call. This field will be carried forward through the transaction lifecycle.

Identification Strategy: While the BPP currently creates a transaction reference within the PG, a dedicated upitransactionid is necessary because existing references lack the required uniqueness for PSP layer processing, particularly in cases of overcharging where multiple references are required.

Settlement Flow: The BAP will utilize the VPA handle of the bank from the settlement details object. The BPP will remain the beneficiary within the init call.

Response Structure: The on_init call will remain consistent with current BPP-led payment flows but will now include the upitransactionid.

Buyer Information: To facilitate reimbursements, the user's VPA details must be captured within the buyer object.

@ameetdesh @anandp504 @nirmay @nirmalnr

[ravi-prakash-v]

@biodatanet could you please highlight which schema and flow is this issue pertinent to ? It would be useful if you can mention where the implementations are breaking.

[biodatanet]

So essentially within UPI the transaction id is generated within the PSP layer. When an application like BHIM doesnt have an aquiring bank hence cannot be the beneficiary since it never collects payment only enables it through UPI. Hence follows the BPP led payment method. Now this poses an issue because the provider thinks it will generate a url for which it shall have a transaction ref. So when the payment is done through UPI and not through pg then there shoudl be a upi ref to look for else It will keep listening to the PG looking for a status change in payment. This UPI transaction id must be unique too so it cannot be the same transction referrence used within the pg.
@ravi-prakash-v

[nirmay]

@biodatanet can you list down which object in the spec is proposed to be changed? I think that is what @ravi-prakash-v is also asking. This helps us to review quickly.

[biodatanet]

Got it, buyer attributes can be changed within beckn:buyer to accomodate the buyerVPA. and beckn:payment can accomodate upitransactionid within it.

[nirmay]

we could create a upi object inside beckn:payment and add all upi related fields inside that, including transactionid as proposed here.

cc: @anandp504 @ravi-prakash-v @abhimail

[biodatanet]

Hi all, lets keep this on hold for now. We are looking at alternative routes to solve the problem. Lets shelf this for now and retake it when required. Closing this discussion. Thank you.
@nirmay @TANMOYDADA @ameetdesh @ravi-prakash-v