1. Seller should list the product in IDRL Market with complete and accurate details and share the same in the PayProtect group that allows the Buyer to get a complete and correct understanding of the features and condition of the product.
Any attempt or forgetfulness on part of the seller to hide/mislead details about the product that would lead to Buyer dissatisfaction and dispute will go against the Seller in the event of a dispute between the Buyer and Seller.
The extent to which the Seller has hidden details about the product will be solely decided by the PayProtect Admin after examining the details and proofs available in the PayProtect group and accordingly the decision will be conveyed to both Buyer and Seller.
The Buyer should also clarify all his doubts with the Seller and ask for working videos of the product (except when it's completely new sealed unopened package).
Real images of the product in hand of the seller are mandatory in all conditions of the product whether its New, Like New or Used or in any other condition.
It is also highly recommended that the Buyer and Seller have a video call if there are any doubts about the product and its condition or any missing details.
They should also have a video call if its deemed necessary that the Buyer requires assistance with the product before unboxing it.

2. Pre-order Products: If its a pre-order then the Seller is expected to share as accurate as possible details about the product and its condition and then proceed with sharing images and videos of the product as mentioned in the PayProtect steps when the Seller receives the product.
If working video of non-new/unsealed products is not available in the PayProtect group, then it's considered a fault of both Buyer and Seller of not following PayProtect steps.

3. Batteries: Please read the battery policy in section E completely

4. Seller must upload single continuous video of packing product to Google Drive/Youtube that clearly shows:
- Each and every item in FULL VIEW (not covered or obscured) before packing
- The process of each item being placed into the packaging
- The final fully packed box/package with all contents clearly visible BEFORE sealing
- The sealing of the package
- The sealed package AFTER sealing is complete
Shorter videos can be shared directly in the WhatsApp group.
Image/video of just packed product from outside, partially visible items, or individual WhatsApp videos will NOT be accepted as proof in the event of a dispute.

5. Buyer must upload single continuous video of unboxing and testing to Google Drive/Youtube and share.
Shorter videos can be shared directly in the WhatsApp group.
Individual WhatsApp videos will not be accepted as proof in the event of a dispute.

6. Buyer will get max. 24 hrs after product is delivered by courier to submit the single continuous unboxing and testing video after which payment may be auto-released to the Seller via IMPS per Policy Y.3 (invoked by IDRL Lawyer or PayProtect Admin after the silence protocol — not guaranteed instant bot execution). This 24-hour release clock is separate from the return-initiation window in Policy F.12.

7. DMs between Seller and Buyer will not be accepted as proof to resolve disputes.

8. All proofs must be shared in the WhatsApp group only and where they are required to be attached in the IDRL App.

9. Package weight declaration. Seller must declare package weight on the shipping label AND show the weighed package on-camera (on a visible weighing scale) in the packing video before sealing. Buyer must video the package weight on arrival, on a visible weighing scale, before cutting the seal. A discrepancy of more than 20% between declared and arrival weight (without a reasonable explanation such as packaging material added by the courier) is prima-facie evidence of item swap or tampering and is evaluated by PayProtect Admin per Policy V.

10. Serial / unique identifier documentation. For any item with a serial number, IMEI, ESC-ID, motor ID, transmitter ID, goggles ID, flight controller ID, GPS module ID, or battery cycle count, the seller must show the identifier on video during packing (Step 5) and the buyer must verify it on video during unboxing (Step 7). Any identifier mismatch is treated as a seller-side liability (see Policy R).

11. Unboxing-clock start. The 24-hour deadline in A.6 begins at the earlier of (a) the courier's "delivered" status event on its official tracking page, or (b) the buyer's explicit receipt acknowledgement in the PayProtect group, whichever occurs first. Claims of non-delivery despite a "delivered" status require courier-issued proof (written non-delivery certificate, CCTV footage, neighbour statement, etc.) submitted in the PayProtect group.

12. Listing vs agreed terms. Mutually agreed price, shipping, and included items must be confirmed in the PayProtect group and reflected in the agreed fields in the IDRL App before buyer payment (Step 4). Listing photos and description are evidence, but the agreed fields in the App govern the IMPS payout amount to the Seller (Policy AA).

13. Completeness and accessories. Seller must provide an explicit manifest of included items (props, chargers, cases, SD cards, bind plugs, spare parts, manuals, etc.) in the PayProtect group before payment. Missing non-trivial accessories not listed as excluded constitute material misrepresentation.

14. Condition definitions. For dispute purposes: "New" = sealed/unopened or never used; "Like New" = minimal use, fully functional, no crash history; "Used" = normal wear, fully functional unless stated otherwise; "For Parts / Not Working" = sold as-is, no flight-worthiness implied (Policy R.9); "BNF" = bind-and-fly (requires binding); "PNP" = plug-and-play (no receiver); "RTF" = ready-to-fly. "Powers on" ≠ "flight tested" ≠ "works in flight" — each must be stated explicitly if claimed.

15. Local pickup and hand delivery. PayProtect evidence rules require courier-based forward and return shipping (Policies A.4, A.5, V.3). Local pickup, hand delivery, or in-person exchange is NOT supported under standard PayProtect evidence rules unless PayProtect Admin pre-approves an alternate evidence protocol in writing in the PayProtect group.

1. Buyer and Seller are required to mark their respective PayProtect steps in the IDRL App compulsorily only after that step has been completed by them.

2. Failure to mark any step will halt the entire PayProtect process irrespective of any communication in the WhatsApp group and PayProtect Admin will simply not respond in the PayProtect group nor will it send any reminder.

3. It is solely the responsibility of the Buyer and Seller to make sure that the steps are marked and alert each other if they are not marked.

4. Wrong step or premature mark. Marking a PayProtect step before that step is actually completed is a policy breach. The counterparty must not mark the next step. PayProtect Admin may roll back an incorrectly marked step upon request with evidence.

5. App outage. If the IDRL App is temporarily unavailable, parties must post required evidence and a typed statement of step completion in the PayProtect WhatsApp group. PayProtect Admin may mark steps on behalf of a party after verifying the in-group evidence.

1. If a listing has multiple items, then the Seller will receive payment only after the Buyer has received all the items and they have been confirmed in satisfactory condition as per the PayProtect steps.

2. We advise against putting multiple items in a single listing for sale via PayProtect as there are many complexities involved in such transactions and it is difficult to resolve disputes in such cases.

3. It is best to list each item separately and use the PayProtect feature for each item separately.

1. To initiate a PayProtect transaction, either Buyer or Seller must be an X Member.

2. Having an X Membership for the Buyer means that he/she can initiate PayProtect transactions with both Free and X Sellers.

3. Having an X Membership for the Seller means that he/she can initiate PayProtect transactions with both Free and X Buyers.

4. Buyer payment — UPI (inbound only). When paying by UPI, the buyer pays: mutually agreed price + shipping + PayProtect service fee of max(₹20, 2% × price). Shipping price does not attract the 2% PayProtect fee. This is a buyer-to-IDRL inbound payment only — not a seller payout method.

5. Buyer payment — credit card (inbound only). When paying by credit card, the buyer pays: UPI subtotal from D.4 + payment gateway (PG) fee of 3% × UPI subtotal. Shipping is included in the PG fee base but not in the 2% PayProtect fee base. This is a buyer-to-IDRL inbound payment only — not a seller payout method.

6. PayProtect Fee is levied only on the Buyer and not on the Seller. The Seller does not pay any PayProtect Fee.

7. For Exchange Transactions: IDRL charges 2% fee on each party's collateral deposit (buyer payment). See Policy P for complete exchange transaction details.

8. Fee formula summary. UPI buyer payment total = price + shipping + max(₹20, 2% × price). Card buyer payment total = UPI subtotal + 3% × UPI subtotal. All outbound transfers (payouts and refunds) use IMPS only — see D.11 and Policy AA.

9. Fee on mutual cancellation. On Admin-approved mutual cancellation before the seller marks shipping (Step 6), the buyer receives a full IMPS refund of all amounts paid including fees. After shipping has commenced, fee treatment on cancellation is at PayProtect Admin's discretion per Policy W.

10. GST and tax. PayProtect fees are service charges; applicable GST or tax treatment is as per law. IDRL does not provide tax advice — parties should consult their own tax advisors.

11. Payment rails (inbound vs outbound). Money IN (buyer → IDRL escrow): UPI or credit card only, via the IDRL App payment gateway. Money OUT (IDRL → seller OR buyer): IMPS bank transfer only — the only outbound rail for PayProtect. Applies equally to seller payouts, full refunds, partial refunds, return refunds, cancellation refunds, and exchange collateral release. IDRL does not send money out via UPI, VPA, GPay, PhonePe, Paytm, wallet, phone number, cash, or automatic reversal to the original UPI/card instrument. Both parties must store valid IMPS-eligible bank details (account name, account number, IFSC) in the IDRL App. The seller needs this before Step 9; the buyer needs this before any refund can be processed. Refund amounts for card payers may include the PG fee layer in the IMPS transfer (Policy S.8) — but delivery is always IMPS to bank.

1. Buyer and Seller should examine the condition of the battery together over a video call. This is MANDATORY.

2. Simply sharing pics and videos of the battery without a video call will not be accepted as proof in the event of a dispute.

3. If the video is not performed before the battery is shipped, then IDRL PayProtect will not be applicable and the Buyer and Seller will have to sort out their differences between themselves.

1. A return must be approved by the PayProtect Admin before it can be initiated by the Buyer.

2. If the Buyer sends the product back to the Seller without approval from PayProtect Admin, then the Buyer will be responsible for the loss and money will be released to the Seller.

3. The PayProtect Admin will solely decide whether the product is defective or unsatisfactory after hearing from both Buyer and Seller and based on the proofs that are available in the PayProtect group and IDRL App.

4. Seller will pay for return shipping cost if Buyer has followed all his responsibilities as given in section A. above which is confirmed by PayProtect Admin.

5. Buyer will pay for return shipping cost if he has not followed his responsibilities while Seller has followed his responsibilities as given in section A. above which is confirmed by PayProtect Admin.

6. Seller and Buyer will split the shipping amount 50-50 of the return shipping cost if both Buyer and Seller have not followed their responsibilities as given in section A. above which is confirmed by PayProtect Admin.

7. Seller will be given max. 12 hrs to confirm his return shipping address to Buyer as per his details available in the PayProtect Screen of the IDRL App failing which Buyer will ship the item to the Seller's address as given in the IDRL App.

8. During return Buyer will follow the exact reverse steps as those followed by Seller during forward shipping such as uploading single continuous and complete packing video to Google Drive/Youtube along with other required proofs.

9. Buyer will receive the money only after Seller has received back all the items of the listing.

10. Seller has to perform the same steps of unboxing and testing and uploading video on Google Drive/Youtube.

11. Buyer refund after return. If the Seller does not respond or mark the return-received step within 24 hours of the courier's "delivered" event at the Seller's address, the Buyer may be auto-refunded via IMPS per Policy Y.3 (invoked by IDRL Lawyer or PayProtect Admin — not guaranteed instant bot execution). Seller may request a short extension via PayProtect Admin with valid reason.

12. Return-initiation window. Buyer must initiate a return request within 48 hours of submitting the unboxing video (Step 7/Step 8 user-facing). Returns initiated after 48 hours may be declined at Admin's discretion unless a material fault was discovered later and is demonstrably documented (e.g., battery degradation within a stated warranty window).

13. Return-shipping evidence parity. During return shipping, Buyer must match ALL seller-side evidence from Policy A: continuous packing video (A.4), serial / unique identifier verification on-camera (A.10), package weight declaration (A.9), and sealed-package video. Any missing piece is judged the same way it would be judged against a Seller in a forward shipment (see also Policy V for swap/tampering adjudication).

14. IMPS refund delivery. All approved return refunds are sent via IMPS to the Buyer's registered bank account (Policy D.11) — not to the original UPI ID, VPA, or credit card. Buyer must have valid IMPS-eligible bank details on file before Admin processes the refund.

15. Exchange transactions ineligible. Exchange transactions governed by Policy P cannot use the standard return flow. Exchange disputes go directly to PayProtect Admin under Policy P.8–9.

16. Return blocks completion. While a return is pending_approval, initiated, or in_progress, the Buyer must NOT mark transaction complete (Step 9). If Step 9 is marked during an active return, PayProtect Admin treats it as an error — any pending or completed IMPS payout to the Seller may be frozen (Policy W.7) pending review.

17. Pending admin approval. During pending_approval return status, forward-shipping obligations pause and silence timers under Policy Y are tolled until Admin approves or rejects the return request.

1. Seller and Buyer will make sure that they purchase shipping insurance for the product whenever possible during BOTH Forward & Return Shipping.

2. If product is not insured and it is damaged during shipping, then IDRL will NOT be responsible and will NOT be able to make any decision or compensation in any way and Seller and Buyer alone will have to sort out their differences.
They will not hold IDRL or PayProtect responsible for this and if they do then future PayProtect requests from them will not be accepted.

3. Insurance claim responsibility. The shipping party (Seller during forward shipment, Buyer during return) is responsible for filing the courier insurance claim within 48 hours of damage discovery and sharing the claim reference in the PayProtect group. Failure to file within 48 hours forfeits the claim and liability shifts to the non-filing party.

4. Partial damage settlement. If the product is functional but has cosmetic or minor damage, parties may negotiate a partial-refund settlement under Policy S (Partial Refunds, Price Adjustments & Deal Changes) rather than initiating a full return under Policy F.

5. Mandatory insurance threshold. Shipping insurance is MANDATORY for items with declared value greater than ₹50,000 on BOTH forward and return shipping. Skipping insurance above this threshold shifts full damage risk to the party that skipped insurance, regardless of who physically caused the damage.

6. Courier RTO and refused delivery. If the courier returns the package to origin (RTO) or delivery fails because the Buyer refused delivery, provided a wrong address, or was unavailable, liability follows Policy V.9. Seller mis-labelling shifts liability to Seller; Buyer-provided incorrect address shifts liability to Buyer.

7. Split or partial shipment. All items in the listing must arrive before the Buyer marks receipt (Step 8). Partial shipment without prior typed agreement in the PayProtect group is incomplete delivery and does not trigger seller IMPS payout.

1. At any point in time during an ongoing PayProtect, the Buyer is disallowed from dismantling, modifying, repairing, reverse engineering the received product or any such activities that could potentially hamper the original condition of the product.

2. If the Buyer performs any of such above activities on the product without the Seller's consent, then the Buyer will be responsible for the loss and money will be released to the Seller.

1. If you are new to the hobby, then we strongly recommend that you first learn from the community and get knowledgable about the basics before buying any product via PayProtect or on IDRL Market.

2. You should also first buy a new product from a reputed seller and not a used product from a random seller.

3. If you are buying on PayProtect for the first time or you are not knowledgable about the product that you have purchased then you should get on a video call with the Seller during the unboxing and testing step of PayProtect and seek appropriate guidance from the Seller.

4. Video call first for technical help. When the Buyer needs explicit help from the Seller on any technical matter that the Buyer may not be knowledgeable about (binding a transmitter, flashing firmware, changing VTX channel, setting up failsafes, calibrating sensors, understanding a wiring harness, pre-flight setup, goggle pairing, etc.), the parties should schedule a video call BEFORE raising the concern as a dispute. Many "it's broken" cases turn out to be configuration or user-error issues resolvable in minutes on a video call. The Seller is expected to make a reasonable effort to join such a call within PayProtect Admin hours. If the Seller refuses to get on a technical-help video call, that refusal is logged and counts against the Seller if a dispute is subsequently raised.

1. 10 am to 6 pm from Monday to Saturday. Manual PayProtect Admin actions — including creation of WA Groups, dispute adjudication, and manually initiated IMPS payouts/refunds — are done during these hours.

2. Buyer and Seller can communicate 24/7 with each other in PayProtect WA Group.

3. Kindly see the IDRL App Newsfeed for notices regarding any special/holiday/out of office hours. These will also be displayed at the top of any PayProtect screen in the IDRL App.

4. Automatic IMPS seller payout. When the Buyer marks Step 9 and the Seller has valid bank details on file, the IDRL system may initiate automatic IMPS payout to the Seller (Policy AA) including outside Admin hours, subject to amount limits (₹100–₹100,000) and eligibility checks. Manual Admin-initiated IMPS transfers and buyer refunds are processed during Policy J.1 hours.

1. In case of any dispute, the PayProtect Admin will hear both sides and make a decision based on the proofs available in the PayProtect group and in the IDRL App.

2. The PayProtect Admin will make a decision based on the PayProtect Policy and the PayProtect Policy is final and binding on both the Buyer and Seller.

3. The PayProtect Admin will not entertain any DMs or calls from either the Buyer or Seller. All communication must be done in the PayProtect group only.

4. Do not tag the PayProtect Admin unless it is absolutely critical. First check whether all the steps have been followed and whether they have been marked in the IDRL App.

5. The PayProtect Admin will get all notifications from the IDRL App only so kindly keep the communication in the WhatsApp Group to the point.

6. Parties cannot request exceptions to the PayProtect Policy for their own convenience. PayProtect Admin retains exceptional override authority under Policy W.1 with logged rationale — overrides are not granted on party request alone.

7. The PayProtect Admin should not be disturbed outside of the PayProtect working hours which are communicated to the Buyer and Seller at the start of the PayProtect and by the IDRL Bot.

8. The Buyer and Seller shall first try to resolve the dispute amicably between themselves before approaching the PayProtect Admin.

9. The Buyer and Seller are required to be professional and ethical in their dealings with each other and with the PayProtect Admin.
Any unethical behaviour will not be tolerated and will result in the PayProtect Admin taking a decision against the offending party.

10. Escalation ladder. Disputes follow a strict ladder: (i) parties attempt to resolve amicably in the PayProtect group, (ii) IDRL Lawyer (AI) provides policy guidance, (iii) parties may tag PayProtect Admin a MAXIMUM of 2 times per 24 hours with NEW material facts, (iv) unresolved cases escalate to IDRL Operations via the contact channel pinned in the group or via support@droneracingindia.com. Skipping rungs or re-tagging without new facts delays resolution.

11. Tagging-abuse mute. Tagging PayProtect Admin more than 2 times in 24 hours without new material facts (new evidence, new event, new courier update) may result in a 48-hour mute from tagging Admin in this group and is logged as a behaviour pattern that counts against the tagger in any active or future dispute decisions.

12. Video call first before escalating a dispute. Before any dispute is escalated to PayProtect Admin under K.10 rung (iii), the parties are strongly expected to schedule a buyer-seller video call to jointly inspect the issue (defect, damage, missing accessory, misconfiguration, functional concern). A large share of "item not as described" claims are resolved on-call once the Seller observes the exact issue the Buyer is facing. If a party refuses a reasonable video-call request during a live dispute, their refusal is logged in the group and counts against them when the Admin adjudicates. IDRL Lawyer (AI) will, as a first response to a dispute signal, propose a concrete time window for the video call and only after the call (or a documented refusal) escalate to Admin.

There are very rare cases where the Buyer and Seller are unable to resolve their differences and when both parties have either followed or not followed the PayProtect steps and in such cases the Buyer and Seller should try their very best to mutually resolve their differences failing which they will need to obey the decision that is given by the PayProtect Admin.

1. The Buyer and Seller will indemnify and hold harmless IDRL and its affiliates, officers, directors, employees, agents, and licensors from and against any and all claims, damages, costs, and expenses, including attorneys' fees, arising from or related to their use of the IDRL App or PayProtect.

2. IDRL is only a facilitator for the PayProtect transaction and does not own any liability towards the product.

3. Seller and Buyer are solely liable for their respective liabilities for the transaction and the product towards each other.

4. Seller confirms to be the bonafide seller of the product and owns all liabilities towards the ownership of the product and has submitted genuine documents of his/her identity.

5. Buyer and Seller warrants to indemnify IDRL for any third party claims arising out of the transaction.

6. In all cases that are not covered, decision of the PayProtect Admin is final and will have to be followed by the Seller and Buyer.

1. Once payment is made by the buyer in PayProtect, it is implied that both the buyer and seller are fully committed to the transaction and no party can back out unless both the buyer and seller mutually agree to cancel.

2. The seller must ship the product within 3 business days after receiving payment confirmation. If the seller fails to ship within this timeframe without valid reason, the buyer may cancel the transaction unilaterally.

3. If courier pickup is not happening due to courier-related reasons (such as service unavailability, strikes, or operational issues) for more than 4 consecutive days, or if a longer timeframe is mutually agreed between buyer and seller, then either party is allowed to cancel the transaction without requiring mutual agreement.

4. In case of courier pickup delays beyond 4 days due to reasons attributable to the courier service, the affected party must provide evidence of attempted pickups or courier service issues to justify unilateral cancellation.

5. Cancellation requests must be made in the PayProtect WhatsApp group with proper justification and evidence where applicable.

6. For mutual cancellations, both parties must explicitly agree to the cancellation in the PayProtect group before the PayProtect Admin processes the IMPS refund to the Buyer's bank account.

7. All cancellation decisions and refund processing will be handled during PayProtect Admin hours (10 AM to 6 PM, Monday to Saturday) as specified in Policy J.1.

8. In cases of disputed cancellations, the PayProtect Admin's decision will be final and binding on both parties as per Policy K.2.

9. Mutual-cancellation proposal window. A mutual-cancellation proposal posted in the PayProtect group must be explicitly confirmed by the other party (typed acknowledgement, not a reaction emoji) within 48 hours. After 48 hours the proposal lapses and the transaction continues as if no cancellation had been proposed; a new proposal must be issued to retry.

10. Cancellation refund SLA. Admin-approved cancellation refunds are processed via IMPS within 2 IDRL business days (within Policy J hours). Refund delays beyond 2 business days should be raised via Policy K.10 escalation ladder starting at rung (iii).

11. Pre-payment expiry. PayProtect transactions with no buyer payment (step below 4) may auto-expire: first warning approximately 24 hours after creation, then deletion approximately 48 hours after creation. Admin may set dontExpire on a case — this flag is Admin-only.

12. Deletion request vs mutual cancel. A one-party request to close the PayProtect record (deletion request with 6-hour grace, counterparty may resume) is NOT the same as mutual cancellation with IMPS refund under N.1/N.6. Post-payment unilateral deletion does NOT cancel escrow or trigger refund — funds remain held until Admin processes mutual cancellation or dispute resolution.

13. Post-payment abandon. Deleting or abandoning the PayProtect record does not release escrowed funds. PayProtect Admin resolves held funds per Policies K and W.

1. IDRL will not entertain or respond to any messages, claims, disputes or any other communication from users such as banning other users from IDRL, etc, if they have not transacted using IDRL PayProtect.

2. Even with valid proof, such requests will not be entertained as it is completely the decision of the user whether to use IDRL PayProtect or not.

3. The IDRL App already warns the users about the risks of transacting outside of IDRL PayProtect and the users still go ahead and do so at their own risk.

4. IDRL will not be responsible for any issues that may arise from transactions conducted outside of IDRL PayProtect.

5. IDRL always encourages the users to transact using IDRL PayProtect on IDRL Market as it is the safest and most secure way to transact.

6. DO NOT trust sellers who say that they will not use IDRL PayProtect and will do the transaction outside of IDRL PayProtect even if they have good reviews on IDRL.

7. Every transaction should be considered as a new transaction and IDRL PayProtect should be used for every transaction no matter how favorable the previous transactions with the same seller/buyer were.

1. PayProtect supports product exchanges where both parties swap items of agreed value instead of a traditional buyer-seller transaction.

2. Collateral Requirement: Each party must deposit the agreed value of their item with IDRL as collateral before shipping.

3. Fee Structure: IDRL charges 2% fee on each party's collateral deposit (buyer payment / UPI rate). For example, if Party A exchanges a ₹10,000 drone with Party B's ₹10,000 FPV goggles, each party deposits ₹10,200 (₹10,000 collateral + ₹200 IDRL fee). Total IDRL fee collected: ₹400. Collateral release uses IMPS only (Policy D.11).

4. Both parties must follow the standard PayProtect steps for their respective items: sharing product media (Step 2-3), confirming collateral deposits (Step 4-5), recording packing videos (Step 6), shipping items simultaneously (Step 7), recording unboxing videos (Step 8), and confirming receipt and satisfaction (Step 9).

5. Shipping: Both parties are required to ship their items simultaneously after collateral deposits are confirmed by IDRL Admin. Standard shipping policies from Policy C apply to both parties.

6. Upon successful completion where both parties confirm satisfaction, collaterals are released back to the original depositors.

7. Battery Policy: If either item in the exchange contains batteries, Policy E (Battery Policy) is MANDATORY for that item. Video call examination must be performed for battery-containing items.

8. Dispute Resolution: Exchange transactions cannot use the standard return flow (Policy F.15). If either party disputes the condition of the received item, PayProtect Admin evaluates evidence in the PayProtect group. IDRL Lawyer (AI) may provide advisory guidance. If both parties dispute, full evaluation of both items is conducted by Admin.

9. Failed Exchange: If the exchange cannot be completed due to disputes or policy violations, collaterals will be returned to the original depositors after deducting any applicable penalties as determined by PayProtect Admin.

10. All other PayProtect policies (A-O) apply to exchange transactions. Both parties have the same responsibilities as outlined in Policy A for their respective items.

11. Each party becomes both a "buyer" (receiving an item) and "seller" (sending an item) simultaneously, and must fulfill both sets of responsibilities.

12. X Membership requirement (Policy D.1) applies to exchange transactions - at least one party must be an X Member to initiate an exchange PayProtect.

13. Asymmetric satisfaction. If one party confirms satisfaction and the other disputes, both collaterals remain held until PayProtect Admin decides. No unilateral IMPS collateral release.

1. Only the registered IDRL account holder may initiate or participate in a PayProtect transaction. Account sharing, sub-letting, reselling access, or impersonation VOIDS PayProtect coverage for that transaction.

2. If your IDRL account is compromised (phone lost, SIM swapped, WhatsApp session hijacked, password leaked), you MUST notify IDRL within 24 hours via the support channel. Disputes arising from post-compromise activity (unauthorized listings, unauthorized purchases, unauthorized group messages) are NOT hearable by PayProtect Admin unless timely notice was given.

3. The registered identity in the IDRL App (name, phone number, KYC documents where applicable) must match the identity used during the transaction. Swapping the actual transacting person mid-PayProtect (for example, "my cousin will pay", "my friend will pick it up") triggers a mandatory Admin review before the next step can be marked.

4. No third parties may be added to the PayProtect WhatsApp group. See Policy Z.1 for full group-composition rules.

5. Systematic VPN usage, rapid geolocation jumps across cities or countries, or any signal suggesting identity masking may be flagged by IDRL's fraud scoring and can delay or block auto-payout until cleared by PayProtect Admin.

6. IDRL reserves the right to require a one-time video KYC call from either party before releasing a payout or approving a return when the transaction amount exceeds a risk threshold or when identity signals are inconsistent.

1. Serial numbers, IMEIs, or any unique identifiers — drone, battery, transmitter, goggles, motors, ESC, flight controller, GPS module, receiver — must be shown on-camera during BOTH packing (Seller, Step 5) and unboxing (Buyer, Step 7) as required by Policy A.10.

2. Seller must disclose firmware version, region lock, aftermarket modifications, repairs, and crash history in the IDRL Market listing AND re-confirm these in the PayProtect group before payment (Step 4). Any undisclosed history discovered post-delivery is a material misrepresentation.

3. Invoice / purchase proof. If the Seller lists an item as "new" or "sealed", an invoice or dealer bill is MANDATORY. Absence of an invoice automatically re-classifies the item as "used" regardless of stated condition, and the listing price must be re-negotiated in the PayProtect group before Step 4.

4. Counterfeit or cloned products (DJI clones, fake Autel units, counterfeit FPV hardware, replica GoPros, clone receivers, etc.) must be explicitly disclosed as clones in the listing title and re-confirmed in the PayProtect group. A clone sold as the original is a willful misrepresentation — the Seller bears 100% liability: full refund + return-shipping at Seller's cost + platform penalty, at Admin's discretion including suspension or permanent ban.

5. Firmware tampering — unlocked units, jail-broken FCs, region-flashed drones, cracked software licenses — must be disclosed. Undisclosed firmware modifications discovered post-delivery allow the Buyer to return the item at Seller's cost under Policy F, and the Seller may be penalized.

6. Regulatory identifiers (UIN, RPAS ID, Type Certificate number, import documentation reference) must be accurate, valid, and transferable to the Buyer. Inaccurate, expired, or non-transferable regulatory identifiers are treated as counterfeit disclosure failures and trigger the same remedy as R.4.

7. Ownership chain. For high-value used equipment (> ₹50,000), the Seller should be able to demonstrate ownership chain (prior invoice, prior transfer record, or credible explanation). Inability to demonstrate ownership chain may cause Admin to pause the payout pending investigation.

8. Account-locked devices. DJI, Autel, or other vendor account locks, firmware locks, or cloud-tethered devices must be disclosed before payment. Buyer must verify account unlink / transfer before marking Step 9. Undisclosed locks discovered post-delivery are material misrepresentation.

9. For parts and not working items. Items sold as "for parts", "not working", or "as-is" exclude flight-worthiness and full-functionality claims unless the Seller explicitly guaranteed specific subcomponents in the PayProtect group before payment.

1. Any price renegotiation after the Buyer has made payment to IDRL requires EXPLICIT WRITTEN (typed) consent from BOTH parties in the PayProtect group. Verbal agreements, DM agreements, or voice notes are not honored.

2. Partial refunds are available for minor defects where the Buyer wishes to retain the item at a reduced price. The deduction percentage AND the final revised amount must be typed in the PayProtect group by both parties before Admin executes.

3. The internal "deal_change" settlement pathway records the revised transaction amount in the PayProtect payout history. Both parties must confirm in the group before Admin executes this settlement.

4. A partial refund cannot exceed the auto-release amount for that PayProtect. If the correction required exceeds the auto-release amount, parties must initiate a full return under Policy F or open a new settlement PayProtect for the excess.

5. When Admin executes a partial refund or deal change, the decision explicitly cites the sub-clause(s) of this Policy S that justify it, for audit trail.

6. Rounding. All partial-refund percentages are rounded to the nearest ₹10 in the Seller's favor to keep computation transparent and avoid sub-rupee disputes.

7. Good-faith-use discount. If a Buyer has used the item for more than 72 hours before raising a defect that is not fundamental to safety or airworthiness, Admin may apply a depreciation-adjusted partial refund rather than a full return.

8. IMPS refund amount (card payers). Partial and full refunds are sent via IMPS to the Buyer's registered bank account (Policy D.11) — not to the original card or UPI. For card payments, the IMPS refund amount must include the proportional PG fee the buyer paid at checkout; under-refunding the PG layer is not permitted. Buyer must have valid bank details on file before Admin executes any refund.

1. Admissible evidence weights, used by IDRL Lawyer (AI) and PayProtect Admin in descending order of weight, are: (i) continuous single-file video uploaded to Google Drive or YouTube and linked in the PayProtect group (packing A.4, unboxing A.5, return F.13); (ii) a recorded live video call with both parties visibly present, shared in the PayProtect group within 24 hours of the call (see Policy Z.6); (iii) continuous videos shared directly in the PayProtect WhatsApp group if size limits permit; (iv) timestamped photographs shared in the PayProtect group; (v) short clips shared in the PayProtect group.

2. NOT admissible as primary evidence: DMs between parties, videos or screenshots from outside the PayProtect group, WhatsApp chat exports, voice notes lacking context, WhatsApp status posts, unsent drafts, forwarded messages without original timestamps, third-party recordings (friends, family, courier agents) unless corroborated by in-group evidence.

3. Evidence must be shared WITHIN the PayProtect group. IDRL Lawyer (AI) and PayProtect Admin do not review evidence from external chats, DMs, email attachments, WhatsApp Business status posts, or third-party messaging platforms.

4. Evidence tampering — edited videos, spliced photos, scrubbed metadata, fabricated screenshots, deepfake audio — detected by PayProtect Admin or IDRL Lawyer shifts dispute judgment against the submitting party and may result in a permanent ban from IDRL PayProtect.

5. Time-stamped evidence created BEFORE the dispute was raised carries more weight than evidence produced AFTER the dispute was raised.

6. Contemporaneous evidence preference. When two parties submit conflicting evidence of the same event, the evidence closer in time to the event being disputed is preferred, all other factors equal.

7. Missing mandatory evidence. Absence of a mandatory video (packing A.4, unboxing A.5, battery call E.1, return packing F.13) defaults the finding on that specific fact to the non-complying party regardless of other evidence.

1. If a Buyer initiates a credit-card chargeback or bank-level payment reversal AFTER payment has been released (auto or manual) to the Seller, the Seller is held harmless and IDRL will defend the transaction with evidence from the PayProtect group. The Buyer's IDRL account may be restricted pending chargeback resolution.

2. A chargeback filed DURING an active PayProtect voids the in-platform dispute process. The chargeback takes precedence and the Buyer's IDRL account access may be restricted pending resolution between the Buyer, their card issuer, and IDRL.

3. Bank-initiated reversals (failed mandate, NACH bounce, UPI reversal) follow the same rules as chargebacks. IDRL is NOT liable for payment-instrument failures on the Buyer side. The PayProtect is paused until the reversal is resolved.

4. If the payment instrument is reported stolen by the cardholder or bank, the transaction is reversed, any pending payout is held, and the Buyer's IDRL account is frozen pending a fraud investigation.

5. Per Policy M (Terms and Conditions), both parties indemnify IDRL against chargeback-related costs (chargeback fees, legal costs, recovery expenses). IDRL is NOT the payment guarantor — IDRL is the escrow FACILITATOR.

6. Buyers found to have attempted chargebacks after successful PayProtect fulfillment (i.e., where the Buyer confirmed receipt and satisfaction, then filed a chargeback with their card issuer) are permanently banned from IDRL PayProtect and may be reported to the card issuer for fraud.

7. Stop-payment requests at the Buyer's bank after placing a PayProtect order are treated the same as chargebacks under this policy.

8. External payment reversals vs IDRL refunds. UPI complaint, bank reversal, or card chargeback is a third-party action on the buyer's inbound payment instrument — separate from IDRL's refund process. IDRL-initiated refunds (cancellation, return, partial refund, admin override) are always IMPS to bank (Policies D.11, AA). If a buyer files a chargeback or bank reversal while a PayProtect is active, escrow is paused per U.2–U.3 and any pending IMPS outbound transfer is held. Buyers must not double-recover (chargeback AND IMPS refund).

1. Tracking numbers must be verifiable on the courier's OFFICIAL tracking page within 24 hours of the Seller marking Step 6 (tracking provided). Non-verifiable tracking (not found on the courier's portal, or found but with no origin scan) = non-shipment, and Buyer may cancel under Policy N.2.

2. Package weight cross-check. Seller's declared-weight video (Policy A.9) vs. Buyer's arrival-weight video (Policy A.9). A discrepancy of more than 20% without a reasonable explanation (e.g., packaging material added by the courier hub) is prima-facie evidence of tampering or item swap; Admin rules in the Buyer's favor absent seller counter-evidence.

3. Sealed-package-on-arrival video. The Buyer MUST video the sealed package with the Seller's shipping label clearly visible and the package seal clearly intact, BEFORE cutting the seal. Absence of this video in any swap, empty-box, or item-substitution dispute defaults judgment to the Seller.

4. Empty-box or item-swap disputes are primarily adjudicated on Policy A.4 packing-video compliance. A Seller without a compliant packing video has no defense against a credible empty-box or swap claim by the Buyer.

5. Insurance is mandatory for shipments of declared value greater than ₹50,000 (Policy G.5). Below that threshold it is strongly recommended but optional.

6. Damaged-on-arrival protocol. Buyer must: (i) video the opening of the damaged package within 24 hours, (ii) file the courier insurance claim within 48 hours, (iii) share the claim reference number in the PayProtect group, (iv) preserve the original packaging (box, bubble wrap, tape) for courier inspection, (v) NOT use, repair, or modify the damaged item pending claim resolution.

7. Return shipping (Policy F) applies all V.1 through V.6 rules to the Buyer acting as shipper. The Buyer is held to the same standard as the Seller was on the forward shipment.

8. Fake courier labels, spoofed tracking portals, tampered "delivered" events, and paid-off delivery agents, when detected by IDRL or courier investigation, are treated as willful fraud: full reversal, permanent ban, and cooperation with the courier's fraud investigation and any law-enforcement referral.

9. Delivery-to-wrong-address disputes. Courier records (GPS proof of delivery, agent ID, signature, OTP) are the primary evidence. Wrong-address delivery caused by Seller mis-labeling shifts liability to the Seller; wrong-address delivery caused by Buyer-provided incorrect address shifts liability to the Buyer.

1. PayProtect Admin has authority to override any automated rule (24-hour auto-release, step sequencing, return eligibility, payout timing, group composition) in exceptional circumstances. All overrides are logged and communicated in the PayProtect group with a rationale.

2. Early return enablement. Admin may set the "returnEnabledByAdmin" flag on a PayProtect to allow returns to be initiated before Step 8 user-facing (e.g., obviously damaged package on arrival, delivery to wrong address). Once set, the Buyer may initiate a return from Step 4 user-facing onwards.

3. Admin-override settlements (internally flagged "isAdminOverride"). Admin may execute settlements that bypass automated logic (e.g., 70/30 shipping cost split, partial refund at non-standard ratio, collateral release under asymmetric conditions). Both parties are notified in the group with rationale and the applicable policy clauses cited.

4. Appeal window. Admin decisions may be appealed within 48 hours of the decision being posted in the PayProtect group. Appeals require NEW material evidence not previously considered by Admin. Appeals without new evidence are rejected and the original decision stands.

5. IDRL Lawyer (AI) recommendations are ADVISORY. Where AI guidance and an Admin decision conflict, the Admin decision prevails. AI Lawyer may be instructed to reference the Admin decision going forward within the same PayProtect group.

6. Admin ban authority. For repeated policy violations, willful fraud, impersonation, chargeback abuse, counterfeiting, or harassment, Admin may suspend or permanently ban a user from PayProtect. Bans are communicated via the registered email and may be appealed in writing to IDRL Operations within 7 days.

7. Payout freeze. Admin may freeze a pending payout for up to 7 calendar days without penalty to either party, for fraud review, identity verification, or pending bank investigation (see also Policy U).

8. Scope of override. An Admin override applies only to the specific PayProtect in which it is issued and does not set precedent for other transactions unless explicitly made a policy amendment in a future version of this document.

9. Manual IMPS path. When automatic IMPS is ineligible (no valid bank details, amount outside ₹100–₹100,000, failed IMPS, name mismatch) — for seller payout OR buyer refund — PayProtect Admin processes manual IMPS bank transfer during Policy J hours. Admin will not substitute UPI/VPA/card-reversal/cash/wallet for IMPS except where required by law.

1. Nature of IDRL Lawyer. The IDRL Lawyer is an AI assistant providing policy guidance and dispute framing within the PayProtect WhatsApp group. It is ADVISORY ONLY. Final authority rests with PayProtect Admin (Policy K.2, Policy W.5).

2. Available slash commands in the PayProtect WhatsApp group: (a) /stop or /ai off — silences IDRL Lawyer for this group until resumed; (b) /resume or /ai on — reactivates IDRL Lawyer; (c) /pause <hours> — silences IDRL Lawyer for the next N hours (maximum 72), then auto-resumes; (d) /sum — generates a structured summary of the conversation and current transaction status; (e) /help — lists all available commands.

3. Pausing IDRL Lawyer does NOT pause the PayProtect transaction itself. Step deadlines, auto-release timers, courier SLAs, and Admin actions continue regardless of AI state.

4. IDRL Lawyer may NOT be paused after a dispute has been formally tagged to PayProtect Admin. In active-dispute mode, IDRL Lawyer remains available for Admin reference and cannot be silenced by either party alone; only Admin may re-enable pause in that state.

5. Video-call first. As a first response to a dispute signal or to a Buyer technical-help signal, IDRL Lawyer will propose a concrete buyer-seller video call (with a suggested time window within PayProtect Admin hours) before routing to formal dispute escalation (see Policy K.12 and Policy I.4).

6. Misuse — prompt injection, impersonating Admin, pasting fake policy text, attempting to confuse IDRL Lawyer with fabricated claims, sending deliberately toxic content to elicit a harmful response — is logged and flagged for Admin review and may result in a ban.

7. Conversation retention. All PayProtect group messages (including IDRL Lawyer responses) are retained for a minimum of 7 years for dispute audit, legal compliance, and Admin review (see also Policy Z.7).

8. Policy version. IDRL Lawyer operates against the currently deployed PayProtect policy version. A dispute decision cites the policy version in force at the time of the dispute. If policies change between dispute filing and resolution, Admin states which version governs the specific decision.

1. Substantive-question response window. When the other party (or IDRL Lawyer, or PayProtect Admin) asks a substantive question in the PayProtect group — one that is required to progress the transaction, resolve a dispute, or provide evidence — the responsible party is expected to respond in the group within 48 hours. "Substantive" excludes social acknowledgements ("ok", "thanks"), reaction emojis, and casual chat. A clarifying counter-question still counts as a response.

2. Step-progress response window. After a step's pre-conditions have been met (e.g., payment confirmed, packing video uploaded, unboxing video submitted), the party responsible for the next step is expected to act on it within 72 hours during PayProtect Admin business days. Missing the 72-hour window without a typed reason in the group is flagged as silence under Y.3.

3. Silence protocol. If a party does not respond to substantive group messages for 3 consecutive IDRL business days (Policy J hours), IDRL Lawyer will post a SILENCE WARNING tagging that party. If silence continues for 2 additional business days (total 5 business days), the non-silent party may invoke the applicable automated remedy already defined elsewhere in the policy: Policy N.2 (Seller non-shipment = Buyer unilateral cancel), Policy F.14 (Seller silence after return delivery = auto-refund to Buyer), or Policy A.6/A.11 (Buyer silence post-delivery = auto-release to Seller). This policy does not create new auto-release triggers — it normalizes the silence-detection path that feeds into them.

4. Abandonment. A PayProtect transaction where one party has been silent for 10 consecutive IDRL business days after Admin has tagged the silence is classified as ABANDONED. Admin may, at its sole discretion: release escrowed funds per the pre-defined automated remedy, re-invite the silent party one last time, and log the abandonment against the silent party's account. Repeated abandonment across multiple PayProtects may result in suspension or ban per Policy W.6.

5. Planned absence. A party who anticipates being unable to respond (travel, hospitalization, work-event, exam) must post a typed notice in the PayProtect group BEFORE the absence begins, stating the duration and a specific return-to-group date. A posted planned absence of up to 10 calendar days is honoured and pauses the Y.1–Y.3 windows for that party for the stated duration. Silence without a prior notice is NOT retroactively forgiven by a post-hoc explanation.

6. Post-delivery support window. The Seller is expected to be reasonably reachable in the PayProtect group for 72 hours after the Buyer submits the unboxing video (Policy A.5/A.6). During this window the Seller must make a good-faith effort to help the Buyer with setup, binding, calibration, firmware, and basic usage questions — including joining a short video call when requested (Policy I.4). A Seller who ignores reasonable technical-help requests during this 72-hour window has that conduct logged and it may count against the Seller in any dispute arising during or shortly after this window.

7. Post-delivery support is advisory, not a warranty. Post-delivery support under Y.6 is a best-effort help window — it does NOT obligate the Seller to repair, replace, refund, or provide indefinite lifetime support. Hardware warranty, if any, remains with the original manufacturer / retailer per the invoice; Policy M.2 (IDRL is facilitator, not product-liable) continues to govern.

8. IDRL Lawyer (AI) response pacing. IDRL Lawyer is not bound by Y.1–Y.3 — it responds near-real-time when enabled and remains silent when paused (Policy X). Silence from IDRL Lawyer caused by a /stop, /pause, or active-dispute lock is NOT counted as party silence; parties remain responsible for their own group responses regardless of AI state (Policy X.3).

9. Tolling for admin-review pauses. When Admin has paused a transaction pending evidence review, collateral verification, or fraud investigation (Policy W.1, W.7), the Y.1–Y.3 windows are TOLLED for both parties until Admin posts a resume message in the group. Tolling does not erase prior silence accrued before the Admin pause.

10. Chronic-delay pattern. Repeated near-miss delays (e.g., responding on day-5 of every window across multiple PayProtects) may be flagged by IDRL's housekeeping agents as a chronic-delay pattern. Chronic-delay users may be required to pre-fund a deposit before initiating future PayProtects, at Admin's discretion, to protect counterparties from foreseeable friction.

11. Automated remedies. Auto-release, auto-refund, and unilateral-cancel remedies referenced in Policies A.6, F.11, F.14, N.2, and Y.3 apply when IDRL Lawyer or PayProtect Admin invokes them after the silence protocol — they are not guaranteed instant automated bot execution.

1. PayProtect WhatsApp group composition is strictly: the registered Buyer, the registered Seller, PayProtect Admin, and the IDRL Bot. No other participants are permitted.

2. Adding any third party (family member, friend, broker, agent, advisor, lawyer, another drone pilot for advice) to the PayProtect group WITHOUT prior Admin approval is a policy breach. The added party is removed by Admin and the adding party may forfeit the dispute or be penalized.

3. Leaving the PayProtect group during an active transaction is PROHIBITED. Leaving is treated as refusal to cooperate; judgment may be rendered against the leaving party. The group is re-invited once by Admin; if the party rejoins, the transaction continues. A second departure is considered final and Admin proceeds to decide based on available evidence.

4. Deleting messages is PROHIBITED. WhatsApp retains deletion records visible to IDRL. Deleting messages mid-dispute creates an inference of concealment and counts against the deleting party.

5. Screenshots of the PayProtect group may be used ONLY for the purposes of the PayProtect dispute within IDRL. Sharing screenshots publicly (social media, forums, WhatsApp status, public group chats) or with non-IDRL third parties without both parties' consent is a privacy breach and may result in a ban.

6. Recording video calls. Recording buyer-seller video calls is permitted. If a recorded call is relevant to any later dispute, the recording MUST be shared in the PayProtect group within 24 hours of the call; otherwise it is inadmissible under Policy T.

7. Data retention. PayProtect conversation history, videos, evidence, and IDRL Lawyer (AI) responses are retained for a minimum of 7 years for audit, legal compliance, and future dispute reference.

8. Data access. Parties may request their own transaction history in writing from IDRL Operations. IDRL does NOT share one party's data with the other outside the PayProtect group context, except as required by applicable law or by Admin in the course of a specific dispute.

9. No external recording of Admin. Admin messages in the PayProtect group are the authoritative source. Any external recording, transcription service, or bot attached to the PayProtect group other than the IDRL Bot is prohibited.

10. Group creation failure. If WhatsApp group creation fails or stalls, parties must not transact off-platform or exchange payment details. IDRL operations will attempt recovery. No IMPS payout or refund is released without an active PayProtect group except under PayProtect Admin override (Policy W.1).

1. Escrow hold. IDRL holds the buyer's inbound payment (UPI or credit card) in escrow until PayProtect steps and policies are satisfied. The seller receives price + shipping via IMPS — IDRL PayProtect fee was collected from the buyer at payment and is not deducted again from the seller payout.

2. Money IN (buyer → IDRL escrow). UPI or credit card via the IDRL App payment gateway only.

3. Money OUT (IDRL → anyone). IMPS bank transfer only. No exceptions for seller payouts, buyer refunds, partial refunds, return refunds, cancellation refunds, or exchange collateral release. IDRL does not refund to original UPI ID, VPA, credit card, or wallet — even if that was how the buyer paid in.

4. Seller IMPS payout trigger. When the Buyer marks Step 9 (transaction complete), the IDRL system may automatically initiate IMPS to the Seller if: valid bank details (account name, account number, IFSC) are on file; payout amount is between ₹100 and ₹100,000 inclusive; and no active return or dispute freeze applies (Policy F.16). Otherwise Admin processes manual IMPS during Policy J hours (Policy W.9).

5. Buyer IMPS refund trigger. Admin-approved refunds (cancellation, return, partial refund, deal change, admin override) are queued as IMPS to the Buyer's registered bank account. Buyer must have valid bank details on file. Card payers receive IMPS amounts that include the PG fee layer where applicable (Policy S.8).

6. Bank detail requirements. Both parties must maintain accurate IMPS-eligible bank details in the IDRL App (More → View/Edit Profile). Failed IMPS (wrong IFSC, name mismatch, closed account) must be corrected in the App; parties should notify the PayProtect group. Admin may retry IMPS after correction during Policy J hours.

7. Concurrent payout and return. If Step 9 is marked while a return is active, Admin may freeze IMPS outbound transfers pending review (Policies F.16, W.7).

8. Anti-patterns. Requests to "refund to my UPI/GPay/PhonePe" or "send payout to my UPI" violate Policy D.11 and will not be processed.

1. PayProtect group — the WhatsApp group containing registered Buyer, registered Seller, PayProtect Admin, and IDRL Bot (Policy Z.1).

2. Material misrepresentation — any undisclosed fact about condition, inclusions, authenticity, locks, or history that a reasonable buyer would consider in the purchase decision.

3. Continuous video — a single unedited recording file (or clearly sequential single take) showing the required packing, unboxing, or return-shipping evidence (Policies A.4, A.5, F.13, T.1).

4. IDRL business day — Monday through Saturday, 10 am to 6 pm IST, excluding holidays announced on the IDRL App Newsfeed (Policy J).

5. Substantive message — a group message required to progress the transaction, provide evidence, or answer a policy-relevant question; excludes casual chat and reaction emojis (Policy Y.1).

6. Auto-remedy — a policy-defined outcome (auto IMPS release, auto IMPS refund, unilateral cancel) invoked by IDRL Lawyer or PayProtect Admin after the silence protocol (Policy Y.11).

7. Escrow — funds held by IDRL between buyer inbound payment and IMPS outbound transfer.

8. Return flow — the reverse-shipment process under Policy F after Admin approves a return.

9. Exchange flow — dual-party collateral and simultaneous shipping under Policy P; standard return flow does not apply.

10. Buyer payment (inbound) — funds the buyer sends to IDRL escrow via UPI or credit card only.

11. Outbound transfer — any funds IDRL sends out of escrow: IMPS bank transfer only (seller payouts, buyer refunds, partial refunds, collateral release).

12. Seller payout — outbound IMPS to the seller after successful completion (price + shipping).

13. Refund — outbound IMPS to the buyer's registered bank account; never UPI/VPA/card reversal initiated by IDRL.

14. UPI — inbound buyer payment method only; never used for any outbound transfer.

15. IMPS — the only outbound rail for PayProtect; requires valid Indian bank account details on file for the recipient.

16. Binding decision — PayProtect Admin only (Policies K.2, X.1). IDRL Lawyer (AI) guidance is advisory.

17. Policy hierarchy — PayProtect Admin decision > deployed policy version at dispute time (Policy X.8) > IDRL Lawyer advice.

18. Language. English text of this policy controls in case of conflict with translations. If any clause is held invalid, remaining clauses continue in effect.