Check mandate status, trigger recurring payments, modify or cancel mandates, and view subscription payments.
This guide covers how to manage subscriptions after creation — including checking mandate status, triggering recurring payments, modifying or cancelling mandates, and viewing payment history.
Check Mandate Status
Verify that the mandate is active before proceeding
Trigger Recurring Payment
Send pre-debit notification and trigger recurring payment
Modify or Cancel Mandate
Update mandate amount/end date or cancel the subscription
Use the Pre-Debit Notification API to inform the customer about an upcoming debit, in line with UPI subscription compliance. This should be sent at least 48 hours before triggering the actual recurring payment. If the billing cycle is daily, the notification should be sent at least 24 hours before triggering the payment.
Test/Sandbox Environment: In test/sandbox environment, the recurring payment can be called immediately after the pre-debit notification is sent. The 48-hour (or 24-hour for daily billing) waiting period requirement applies only to production environment.
On the scheduled billing date, trigger the recurring payment using the Trigger Recurring Payment API.
Production Only: Cancel mandate and modify mandate operations are only supported in production environment. These features are not available in test/sandbox environments.
Use the Get Subscription Payments API to fetch all payments associated with a subscription from the internal system. This is available for all payment gateways and all environments (including production).
The response returns an array of all payment records for the subscription, including details such as the payment status, amount, mode of payment, and timestamps. Use this to build payment history views, reconcile billing records, or track installment statuses.For full response field descriptions, see the Get Subscription Payments endpoint in API Reference.
EximPe sends webhook notifications when subscription status changes occur. You can configure webhooks to receive real-time updates about subscription lifecycle events.
The Subscription Status webhook is triggered when a subscription status changes or subscription information is updated. This allows you to track subscription lifecycle events and update your billing records accordingly.For detailed webhook payload specifications, event types, and implementation details, refer to the Subscription Status Webhook in API Reference.