Subscriptions
Start recurring payment flows and manage active subscriptions, billing history, cancellations, and plan changes.
A subscription links a customer to a recurring price on a product. PayNowPro creates the recurring payment flow from a subscription intent, then exposes records you can use to display access, billing history, and plan-change state in your application.
What you need before creating a subscription
Create or identify each of these records first:
- A customer, including the PayNowPro
customerIdand yourassociatedId. - A product that represents the offer.
- A recurring price for the product.
Use those IDs to create a subscription intent. The request requires customerId, associatedCustomerId, productId, priceId, tenantAlias, and receiptUrl. It may also include a return URL, order number, start date, or reason.
Subscription records
A subscription record includes:
- Its ID, tenant alias, and associated payment-intent ID.
- The customer, product, and price IDs.
- Optional first- and next-billing dates.
- The number of successful billing cycles.
- Optional metadata and cancellation timestamp.
- Creation time.
Use the ID with the customer ID to retrieve or cancel a specific subscription. You can also list active subscriptions for a customer.
Billing history and changes
The API provides two related records:
| Record | Use it to understand |
|---|---|
| Subscription history | The product name, billing-period dates, billed amount, and currency for past billing records. |
| Subscription change | A requested upgrade or downgrade, its current status (pending, successful, or failed), the prior subscription and price, and the target product. |
Both support cursor pagination. Use history and change records to keep your billing interface in sync with the subscription lifecycle.
Cancel a subscription
Cancel a subscription with its subscription ID and customer ID. Before you call the endpoint, decide how cancellation affects your own product access and customer communication. Update access only after you have processed the resulting state in your integration.
Start building
Follow Create and manage subscriptions for the complete setup and workflow, then use the Subscriptions API reference for endpoint schemas.