Paytm has offered some non-mandatory rules which you can choose and apply in summation to make them work together smoothly. For a user to get the benefits of the offer/campaign, a user must satisfy all the rules. Ruling out a single rule will disqualify the user from getting the benefits, and will show an error message associated with that rule.
- Maximum eligible transaction amount
You must select this rule, if you want to cap the maximum order value inorder to gratify the offer/discount to your users.
Example: You need to create multiple campaigns in case you want to define multiple slabs for a campaign.
- “Get Rs 100 off on all orders up to Rs 1000”
- “Get Rs 100 off on all order values between Rs 500 and Rs 1000”, if you want to define a particular slab for discount eligibility. In this example, Rs 1000 would come as an input for this rule
- Minimum eligible transaction amount
You must select this rule, if you want to define the minimum order value against which you would want to gratify the discount/offer to the user.
Example: If you enter 1000 as value in this rule, then the campaign would not let users avail the benefit below Rs.1000. You can edit the value in the future. “Get 10% off on all orders of Rs 1000 and above”. This rule helps you define Rs 1000 value in the mentioned example.
- Total number of promo transactions
You must select this rule, if you want to define the total number of transactions which would qualify for gratification for a particular campaign during the entire course of the campaign.
Example: If you enter 100 as value in this rule, then the campaign would not let users avail the benefit after 100 transactions, if you have already qualified for the benefit successfully. You can edit the value in the future.
Set promo transaction sub-limits for a campaign
You can define the promo transaction limit against a calendar value, i.e. Daily/ Weekly/ Monthly. Here, Day is a calendar day, Week is defined from Monday to Sunday, and Month is a calendar month.
Example: If you create a campaign from 15 April to 15 July and want a monthly limit for promo transactions and put 30 as value, then our system would allow 30 transactions for April (15 days), May (30 day), June (30 days) and July (15 day) as the logic works on calendar months. But altogether the overall promo transactions will stop once 100 promo transactions are successfully processed, which means for the month of July only 10 promo transactions would be allowed.
- Maximum number of promo transactions per user
You must select this rule, if you want to define the maximum number of promo transactions allowed per user for an active campaign/offer. This rule works for the entire duration of the campaign. You must pass on the user ID (unique ID) to Paytm to identify the users uniquely.
Example: If you put 100 as value in this field, then the user defined by their unique ID will benefit for 100 txns against that campaign/offer. This is a mandatory condition.
Set promo transaction sub-limits per user for a campaign
You can define the promo transaction limit per user against a calendar value, i.e. Daily/ Weekly/ Monthly. Here, Day is a calendar day, Week is defined from Monday to Sunday, and Month is a calendar month.
Example: If you create a campaign from 15 April to 15 July and want a monthly limit for promo transactions per user and put 30 as value, then our system would allow 30 transactions per user for April (15 days), May (30 day), June (30 days) and July (15 day) as logic works on calendar months. But altogether the overall promo transactions for a user will stop once 100 promo transactions are successfully processed, which means for the month of July it would allow only 10 promo transactions for that user.
- Number of times a card can be used
You can select this rule, If you want to define the maximum number of times a card (Credit or debit) would qualify for gratification during the campaign. This is a mandatory condition.
Example: If you enter 100 as value in this rule, then the campaign would not let users avail the benefit on the same card after the 100 transactions have already qualified for the benefit successfully for that card. You can change the value in the future.
Set transaction sub-limits on a Debit/Credit Card
You can define the transaction limits on a card for a campaign against a calendar value i.e. Daily/ weekly/ monthly. Here, Day is a calendar day, Week is defined from Monday to Sunday, and Month is a calendar month.
Example: If you create a campaign from 15 April to 15 July and specify 30 as a value against the promo transaction per month/card then Paytm would allow 30 transactions for April (15 days), May (30 day), June (30 days) and July (15 day) as logic works on calendar months. But altogether the overall promo transactions will stop once 100 promo transactions are successfully processed on this card, which means for the month of July it would allow only 10 promo transactions on this card.
- Maximum benefit amount per card
You can select this rule to define the maximum gratification amount a user will receive on a card for the entire course of the campaign.
Example: You enter Rs 500 in this field and a user gets Rs 300 on all orders above Rs 1000. User has already got this gratification once on a card i.e. of Rs 300 on first order, then next time they would get only Rs 200 on that card as they would have hit the ceiling limit of Rs 500 defined by you in this rule. Hence, this rule helps you control your burn on a card level basis. This will happen, even if the second time they would be eligible for Rs 300 gratification again.
Set transaction sub-limits on benefit amount per card
You can define the maximum gratification amount limit to a user against a calendar value i.e. Daily/ weekly/ monthly. Day is a calendar day, Week is defined from Monday to Sunday, and Month is a calendar month.
Example: You create a campaign from 15 April to 15 July and want to impose a monthly limit for maximum benefit per card and put 300 as value. Then our system would allow Rs 300 gratification for April (15 days), May (30 day), June (30 days)and July (15 day) as logic works on calendar months. But altogether the overall promo transactions will stop for this card once Rs 500 gratification is availed for a card which means for the month of June and July no benefits will be awarded as the user will already reach the overall Rs 500 gratification in May itself.
- Total burn amount at campaign level
You can select this rule to define and configure the budget for the entire campaign.
Example: If you put Rs 1,00,00,000 in this rule, then you will limit your campaign budget to Rs 1cr and the campaign will end and stop providing gratification further. You can either extend the budget in such cases or mark the campaign inactive.
Set sub-limits for burn amount
You can define the burn amount limit for the campaign against a calendar value i.e. Daily/ weekly/ monthly. Here, Day is a calendar day, Week is defined from Monday to Sunday, and Month is a calendar month.
Example: If you create a campaign from 15 April to 15 July and want to put a monthly limit over the total burn, then enter Rs 30 lacs as value then our system would allow promo transactions for April (15 days), May (30 day), June (30 days) and July (15 day) as logic works on calendar months with Rs 30 lacs limit for promo transactions. But altogether the overall promo transactions will stop once 1cr worth of promo gratification is successfully processed, which means for the month of July only 10 lacs worth promo gratification would be allowed if gratification would run on full potential.
Note:
- Currently, we support 10 active campaigns per MID. If you want a large number of campaigns to be allowed for your MID, please reach out to your KAM or contact us.
- If you want to add more customization features w.r.t Bank Offers configuration, please feel free to reach out to your KAM.
