Different Scenarios and steps to orchestrate them

Paytm’s subscription offering is suited for most business models and can be flexibly used to suit your business requirements. Following are the few business scenarios mentioned-

1. Charge a fixed price every time :

   This is useful when you need to charge a fixed price each cycle. Attributes required for creating fixed amount subscriptions are:
   • txnAmount = The first payment amount to be charged to the customer at the time of subscription creation.
   • subscriptionAmountType= FIX
   • renewalAmount = Fixed amount to be charged to the customer in each frequency cycle.

2. Charge depending on the customer’s usage:

   This is useful when you need to charge a variable price each cycle. Attributes required for creating variable amount subscriptions are:
   • txnAmount = The first payment amount to be charged to the customer at the time of subscription creation.
   • subscriptionAmountType= VARIABLE
   • subscriptionMaxAmount = Maximum amount that can be charged to the customer in each frequency cycle.

3. Charge an addon fee to the customer for a specific cycle:

   This is useful when you may need to charge an additional fee for a specific cycle. In such a scenario always create a VARIABLE amount type subscription. Attributes required for creating the subscription are:
   • txnAmount = The first payment amount to be charged to the customer at the time of subscription creation.
   • subscriptionAmountType= VARIABLE
   • subscriptionMaxAmount = Amount to be deducted in each frequency cycle + Max additional fee that may be charged in the future 

4. Provide a trial period

   This is useful when you need to provide a trial period or free period at the start of the subscription. Attributes required for creating free trial period subscriptions are:
   • txnAmount = 0 (Pass this value as 0. Re 1 may be deducted for Debit Card, Credit Card, UPI and Paytm Wallet for authentication)
   • subscriptionAmountType= VARIABLE
   • subscriptionMaxAmount = Fixed amount/ Maximum amount to be charged to the customer in each frequency cycle.

5. Debit user on a future date

   You can also raise the payment request in advance. This is useful in case you have created an upload tool which your operations teams use to raise payment collection requests. Attributes required while collecting payment
   • DEBIT DATE = Pass the date on which you want the payment should be charged to the user

6. Debit user at any frequency (on demand/as and when presented)

   You can debit the user at any frequency/ on demand debit by setting the subscriptionFrequencyUnit as ONDEMAND in Initiate Transaction API. Thus, you can exercise the flexibility of debiting the user at any frequency, without the restriction of specifying the exact frequency at the time of subscription creation. Reach out to us here to get the same enabled on your account.