Delayed payouts
Payment disputes can leave settlement pending even after the underlying transaction has completed.
A voluntary program for buyer apps. Place a refundable Payment Assurance Security, carry the Payment Assurance Badge, and give seller apps greater assurance when defined payment-dispute exceptions arise.
Buyer apps and seller apps can transact without a prior bilateral relationship. When a payment dispute remains unresolved, uncertainty over payout can reduce a seller app's willingness to transact freely. The Program creates a common Network-level backstop for these exceptions.
Payment disputes can leave settlement pending even after the underlying transaction has completed.
Seller apps need a clear, published signal of which buyer apps have placed a Network-level Payment Assurance Security.
A common assurance mechanism can reduce the need for fragmented bilateral arrangements and strengthen confidence to transact.
Enrolment is voluntary and operates per applicable domain. The Program is currently being rolled out for Metro; additional domains may be added subsequently and this page will be updated accordingly.
From application to a live Badge, in four steps.
Fill the enrolment form with NP and SPOC details, domain, preferred mode of deposit and other required information.
ONDC determines the required Security using applicable transaction and domain parameters.
Fund the Account Deposit or complete the Bank Guarantee submission, based on the mode selected in the form.
Your Badge status is displayed in the Badge Holder List on this page.
Enrolment is voluntary; compliance after enrolment is required. A buyer app may need to recoup its Security if the required threshold increases or if the deposit is used for a dispute payout. If the shortfall is not restored within the defined number of days, the Badge is put on hold and the buyer app is marked inactive on the Network until the requirement is fulfilled. This is different from not enrolling or formally disenrolling.
Seller apps do not enrol and do not place a Payment Assurance Security. A seller app may choose to require the Payment Assurance Badge from the buyer apps it transacts with in a domain. If it chooses to mandate the Program, it can submit that intent to ONDC for publication in the Mandate List on this page.
In exception cases only, the Security provides a defined payout backstop if a covered dispute with a Badge-holding buyer app is resolved and the liable buyer app still does not pay.
You decide which buyer apps to transact with. The Badge is additional information, and a seller app may choose whether or not to mandate participation.
Submit the prescribed form for the domain(s) in which you mandate the Program. ONDC will publish your name in the Mandate List on this page.
Everyday transactions continue to settle directly between buyer apps and seller apps. The Program is used only when a defined payment dispute remains unresolved through the prescribed resolution process.
The seller app raises the payment issue with complete order and reconciliation details.
The NPs first attempt to resolve the issue directly.
If unresolved, the matter is escalated to ONDC.
ONDC issues a resolution within the defined timeline.
If the liable enrolled buyer app still does not pay within the defined period, payout is made from its available Security.
The Badge indicates that the buyer app has enrolled in the Program and maintains the required Payment Assurance Security; it is not a broader assessment of the participant.
Two lists are published here: buyer apps holding the Payment Assurance Badge and seller apps that have mandated the Program. The current rollout is for Metro; additional domains will be added as the Program expands. Refer to the “last updated on” date before relying on either list.
| S.No. | Buyer app | Domain | Status | Enrolled on |
|---|
| S.No. | Seller app | Domain | Mandated on |
|---|
Payment disputes only — where a settlement due from a buyer app to a seller app is unpaid or delayed beyond the expected timeline and the NPs are unable to resolve it themselves.
No. Normal transactions continue to settle directly between the buyer app and the seller app. The Program is used only for defined exception cases.
Not on their own. These follow the existing order and issue-resolution processes. The Program applies only when such a matter results in an unpaid settlement obligation from a buyer app to a seller app.
Only after the defined dispute process is completed and the liable buyer app still does not pay within the applicable timeline. It is a backstop, not the first step.
No. Buyer app enrolment is voluntary. However, once enrolled, the buyer app must continue to meet the Program requirements until it formally disenrols.
ONDC will notify the buyer app and provide the defined period to recoup. If the shortfall is not restored in time, the Badge is put On Hold and the buyer app is marked inactive on the Network until the required level is restored.
No. The Payment Assurance Security is refundable and adjustable in accordance with the Program terms; it is not a fee.
Yes. Once the required shortfall is recouped, the buyer app can be reinstated and its Badge status restored in accordance with the Program process.
The Notification is the binding document. It sets out the computation of the Payment Assurance Security, the dispute resolution process and all applicable timelines.
The full terms, including computation parameters and timelines.
Read the NotificationEnrolment and Badge queries are handled by the Program team. Payment issues against a counterparty NP are raised on ONDC CARE.
Enrolment, the Security, the Badge and the published lists.
Write to team@ondc.orgRaise a dispute for another Network Participant on ONDC CARE.
Raise dispute for Other ParticipantThe Notification, its Schedules, and the overview deck.
View documentsONDC is a network enabler. It is not a party to any transaction between participants or between buyers and sellers, does not act as a marketplace, merchant, payment aggregator, payment gateway or settlement system.