One-Time Mandate
Block funds once in a customer's bank account and capture the payment later after fulfilment.
UPI One-Time Mandate (OTM) lets merchants create a single-use UPI authorization where funds are temporarily locked in the customer's bank account instead of being debited immediately.
The money stays in the customer's account until the merchant captures the mandate after delivering the product or completing the service. If the order is cancelled, the block can be released without a refund transfer.
Block funds once
The customer approves a maximum amount and validity period using their UPI PIN.
Capture once later
Debit the exact payable amount only when fulfilment is complete.
Release unused funds
Release the full block or any uncaptured balance back to the customer.
Use UPI OTM when the final amount, delivery status, or fulfilment timeline is not fully known at checkout, but you still need payment assurance before providing the service.
Why integrate UPI OTM?
Minimize refund overhead
Release a blocked amount when an order is cancelled before fulfilment instead of processing a traditional post-debit refund.
Guarantee payment availability
Lock funds in the customer's bank account for the mandate validity window and reduce insufficient balance risk at capture time.
Increase customer trust
Let customers know their money stays in their own account and is debited only after the merchant completes the service or delivery.
How UPI OTM works
The merchant initiates a UPI OTM request with the maximum block amount, validity window, customer details, and order reference.
The customer reviews the request in their UPI app and enters their UPI PIN once to lock the funds.
When the order is shipped, service is completed, or final bill is confirmed, the merchant captures the payable amount.
If the order is cancelled or the final amount is lower than the blocked amount, the merchant releases the remaining blocked funds.
UPI OTM vs standard UPI Intent
| Capability | Standard UPI Intent | UPI One-Time Mandate |
|---|---|---|
| Fund status | Debited immediately from the customer's account | Locked in the customer's account until capture |
| UPI PIN requirement | Required at purchase | Required only during initial mandate setup |
| Settlement timing | During checkout | Deferred until merchant capture |
| Partial charging | Not supported | Supported through partial capture |
| Cancellation handling | Requires refund after debit | Release the block before debit |
UPI OTM vs UPI Reserve Pay
| Capability | UPI One-Time Mandate | UPI Reserve Pay |
|---|---|---|
| Debit pattern | Single successful capture | Multiple debits against one approved reserved amount |
| Best for | Orders where fulfilment happens once | Usage-based or recurring collection from one fund pool |
| Remaining funds | Released after capture or cancellation | Available for future debits until exhausted or expired |
| Customer authorization | One-time setup with UPI PIN | One-time setup with UPI PIN |
Limits and behaviour
| Item | Current guidance |
|---|---|
| Maximum validity | Up to 60 days from successful customer authorization |
| Default transaction cap | Up to ₹1 lakh per mandate for general merchant categories |
| Pre-debit notification | Not required because funds are already blocked |
| Customer cancellation | The customer cannot revoke an active OTM directly from a TPAP app; they must contact the merchant for release |
| Captures per mandate | One successful capture; the mandate closes after capture |
UPI network limits, supported merchant categories, and bank behaviour can vary by NPCI guidelines and your enabled configuration. Confirm your approved limits with the Pine Labs Online team before going live.
What's in this section
- Integration Steps — Build the block, capture, release, and webhook flow.
- Use Cases — Understand where OTM fits best.
- FAQs — Review common product, limit, and lifecycle questions.