Subscriptions: plans, renewals, failures and cancellation
What recurring billing supports, how to check subscriptions and what to do when billing fails
The basics
A subscription collects recurring payments for an ongoing service. Unlike a one-time checkout, it needs a schedule and a way to manage renewal failures or cancellations.
What recurring billing means
A subscription is an agreement to charge a customer for a service at repeating intervals, such as each month. A product describes what you sell; a recurring price determines the amount and billing period. An invoice records a billing cycle.
What is available
Paypercut supports recurring payments through supported subscription integrations. You can define a recurring amount, billing schedule and customer payment method, then monitor renewals and cancellations. For Magento, use its subscription settings. If you use another platform, contact Paypercut to choose an appropriate setup.
Set up subscription signup
- Decide what the customer will pay, how often they will be charged, and what cancellation terms apply.
- Check whether your selected integration offers recurring billing. Magento has a dedicated setup; other integrations must be checked individually.
- For a custom website or billing system, ask your developer to configure recurring prices and checkout using Paypercut documentation.
- Test the first payment, renewal, failed renewal and cancellation before offering subscriptions.
Manage renewals and failures
Check the subscription and invoice states when a customer asks whether renewal succeeded. A failed renewal may require a customer to update their payment method. Your system should distinguish active, past-due and canceled access. Developers should rely on invoice.paid and invoice.payment_failed rather than inventing subscription webhook events.
How to cancel or change a plan
Open the subscription in the dashboard and use the available management actions. Check the effective end date and whether future invoices are scheduled. For a custom billing integration, your developer can configure advanced plan changes and automated cancellation through the available API.
Before selling subscriptions
Before launching, check your selected integration supports the subscription experience you plan to offer. Test first payment, renewal, failed payment and cancellation in Sandbox. For automated access to subscription services, have your developer connect billing events using the technical documentation.
Before offering a plan
Decide on the product, price, currency, billing interval, cancellation terms and any trial. Explain the recurring charges clearly to the customer.
How it is set up
Your developer can connect a recurring Price to subscription Checkout; a dashboard operator can review the resulting subscription under Subscriptions. The docs do not establish a universal no-code subscription creation flow for all merchants.
Common states
| Status | What it means |
|---|---|
| Trialing | The customer is in a trial period; billing may start at the end of the trial |
| Active | The subscription is ongoing; check invoice payment outcomes for paid periods |
| Past due | A payment is overdue or failed and the subscription may require recovery |
| Cancelled | The subscription has been cancelled; check the effective end date before removing access |
Review a subscription
- Open Dashboard → Subscriptions.
- Choose the subscription and review the linked customer, plan, billing cadence and next renewal date.
- Check whether cancellation is immediate or scheduled for the end of the billing period.
- Use the available actions, such as the three-dot menu for cancellation, where your account supports them.
If renewal fails
Inspect the customer’s default payment method and corresponding invoice, then follow your business’s recovery process. For custom services, developers must keep access aligned with invoice events.
Cancel using the available control
The Dashboard Tour shows a three-dot menu with lifecycle actions such as cancellation. Choose the cancellation action if available, review the presented effective date, then confirm.
Check the outcome
Refresh the record and verify whether cancellation is immediate or set for the period end. Communicate the actual end date to your customer.
For custom subscription systems
Ask your developer to synchronize cancellation and service access with Paypercut’s latest subscription and invoice states. Do not assume the success screen alone is authoritative.
How subscription invoicing works
At renewal, Paypercut creates a billing invoice, attempts collection from the saved method and records the outcome. An invoice can remain Open while a collection attempt has failed.
Common invoice states
| Status | Meaning |
|---|---|
| Open | Payment still due, possibly after an unsuccessful attempt |
| Paid | The invoice has been paid for the period |
| Void | The invoice has been cancelled/voided |
| Uncollectible | The amount is no longer expected to be collected in the ordinary flow |
When a renewal fails
- Open the customer and subscription records to identify the billing period and payment method.
- Determine whether the invoice is paid, open or otherwise unresolved.
- Ask the customer to update their payment method when necessary.
- For custom subscriptions, ask your developer to verify the invoice event and determine when access should be extended or limited.
Official Paypercut documentation
For advanced configuration and technical details, see the official Paypercut documentation.
Need more help?
Find the right support contact for your question.

