Pay per asset

Written By Spandana Patnam (Administrator)

Updated at December 19th, 2025

Apart from live plans, if you publish any special story or article, which cannot be included in the existing plans, then you could add them as an asset. The subscriber who has an active subscription still has to buy this asset to access the content. By default, the asset type would be “story”, but this can be customized.


 Release Notes: FEBRUARY 2020

What’s new

1. CSV upload is now easier and enhanced

CSV upload has become much easier now, as we have provided guidelines and constraints while using the CSV upload feature for the users. The new guidelines make sure the users know what are the mandatory/optional fields, date formats supported and what happens when the user put subscription id in the CSV to be uploaded

 

 

Users now have the option to "Turn OFF" price validation in CSV uploads. This feature will be helpful in cases where the plan price has changed before migration, subscriptions that are to be migrated might be bought at older price, whereas the plan is created with latest price.

 

 

While uploading subscription CSV, now we show specific error messages to the user making it easier for them to understand the issue.

 

Additional fields in Attempts CSV Report

The attempts CSV Report now contains additional fields such as 'payment type' which makes it easy for the publishers to know the PG used for the payments and run some analysis on them.


Release Notes: JANUARY 2019

Updated Subscription CSV Report Structure

The subscription CSV Report now contains additional fields for financial related purposes: Base Price, Discount amount, the amount after the discount before tax and round-off.

 

Release Notes: Oct 15th, 2024

Bundle subscription import

The feature enables importing bundled subscriptions for secondary accounts via CSV, requiring a valid primary subscription ID with the payment type "bundle_subscription." If the primary ID exists, the system checks for a bundle, creates one if missing, and assigns it to both primary and secondary accounts. The implementation ensures error handling for invalid IDs, unmatched plans, or subscriber details, and has been tested and deployed in production.