Skip to main content
Subscribe automatically renews subscriptions and charges the subscriber’s payment method on file at the end of their current service period.
  • **Use Case Number:**2-8-01
  • **Completed By:**NA
  • **Estimated Completion Time:**NA

​
Design Approach

Subscribe runs the subscription renewal process as a batch job shortly after midnight US Pacific time each day. The batch includes any subscriptions that have reached the end of their current subscription period as well as subscriptions with free trial periods that are converting to a paid service. For example, if the subscription period or free trial period for a given subscription ends on January 31, the subscription is included in the Subscribe renewal process which will run shortly after midnight January 31 (early morning February 1) US Pacific time.

​
Renewal Charges

The Subscribe batch job calculates the renewal charge for each subscription that is up for renewal. The renewal charge is a request for the transfer of funds sent to your payment processor. This request includes a Payment Method and Account information (including a Billing Address). When payment collection is successful, a Transaction is generated in Subscribe for the renewal charge. This Transaction includes any applicable taxation, and is charged to the subscriber’s on-file payment information. All charges for a given Subscription (for the given renewal period) are rolled into a single Transaction for that Subscription. If a subscriber has two Subscriptions, two different Transactions are generated. Each Transaction appears as a different charge on the subscriber’s credit card statement or PayPal account.

​
Transaction Status

When Transactions are first created in Subscribe, their status is marked as New. Transactions that are accepted by the payment processor are marked as Captured in Subscribe. Transactions that have not been accepted by your payment processor are marked as Canceled. For more information about Transactions, see Transactions in the Subscribe Portal User Guide.

​
Canceled Transactions

For Canceled Transactions, Subscribe interrogates the response code sent back by the payment processor. This code identifies the reason the payment processor did not accept the Transaction. Based on the code information, Subscribe marks the Transaction as either Soft-Fail or Hard-Fail. Soft-Fail Transactions are subject to retry while Hard-Fail Transactions are considered unrecoverable using the subscriber’s current on-file method of payment. In either case, the subscriber remains entitled through the end of the grace period. For more information about managing your retry strategy and grace period for canceled transactions, see Manage Grace Period And Retry Strategy for Failed Payments. Parent topic:Basic Subscription Setup