stored_credentials field.
How it works
- First charge: The initial payment is a customer-initiated transaction (CIT) processed directly with the payment provider to create the mandate and authorize future debits.
- PDNs: For recurring debits, Yuno sends a pre-debit notification (PDN) that the customer receives by SMS or email, waits the required notice period, and then executes the debit automatically unless the customer cancels.
- Messaging and opt-out: PDNs include the merchant name, amount, and scheduled date, plus a cancellation link. Messages are localized (for example, English, Hindi, Tamil, Telugu, Bengali, Marathi). Email templates are white-labeled with merchant branding.
- Webhook cancellation: If the customer clicks the cancellation link, Yuno validates the transaction, cancels the scheduled debit, updates the payment status, and notifies the merchant.
- Scheduling and retries: Debits are scheduled to run after the notice period in approved IST windows. If a debit fails, Yuno schedules retries based on the configured schedule and retry limits.
- Async status and webhooks: Payment state updates run asynchronously and emit merchant events for PDN sent, cancellations, successes, retry scheduled, and final failure.
- Provider support: Autopay with PDN is initially launching through Adyen and Billdesk.
Payment flows
Autopay uses amount thresholds to determine whether a charge can run as MIT or must be handled as a customer-initiated payment (CIT). This keeps recurring debits compliant and sets expectations for customer action.- Below threshold (≤ INR 50,000): Yuno sends the PDN to the customer, waits the 36-48 hour notice period, and then executes the MIT debit in an IST window. If the customer cancels during the notice period, the debit is not executed.
- Above threshold (> INR 50,000): Yuno sends a CIT notification 72-48 hours in advance with a way for the customer to complete the payment. The customer must actively pay; if they do not, no MIT debit is executed.
stored_credentials fields
Implement Autopay through the stored_credentials field available in endpoints like Create payment. The full path for create payments is payment_method.detail.detail.bank_transfer.stored_credentials.
Use stored_credentials.usage to declare the intent:
| Field | Value | Behavior |
|---|---|---|
usage | FIRST | Run the direct charge (CIT) and store the mandate reference for future debits. |
usage | USED | Send the PDN, wait the 24-hour notice period, then run the MIT debit. |
Dunning and retries
If an MIT debit fails, Yuno retries instead of marking the payment as final failure immediately. The retry schedule is configurable per account.| Attempt | Message |
|---|---|
| 1st fail | ”Payment failed. We’ll retry tomorrow. No action needed.” |
| 2nd fail | ”Payment still pending. Retry in 2 days (link to update payment method).“ |
| 3rd fail | ”Final retry scheduled for date. Please ensure funds are available.” |
| Final fail | ”Payment could not be processed. Contact merchant to resolve.” |
Regulatory compliance
Yuno follows the National Payments Corporation of India (NPCI) requirements for UPI Autopay.- Advance notice window: PDNs must be sent 36-48 hours before the debit. NPCI allows a minimum of 24 hours.
- Customer opt-out: The PDN includes a webhook link delivered via SMS or email. If the customer cancels before the scheduled debit, Yuno stops the charge.
- Execution windows (IST): Debits are executed only in approved time windows: before 10:00 AM, 1:00-5:00 PM, or after 9:30 PM.
- MIT amount threshold: MIT autopay is allowed up to INR 50,000. Any amount above that requires a customer-initiated payment (CIT).
- Retry limits: NPCI allows 1 execution attempt plus up to 3 retries.