Pausing a subscription means deciding what happens to the next payment, the current period and service access. You also need a return journey: when the service becomes available again, when payment resumes and whether the schedule changes. The word “pause” is useful only when customers understand its practical effects.
For a business in Andorra, that policy needs to fit the subscription system and payment integration. At AndorPay, we review collection and the statuses your application receives. Before offering a pause, establish which actions your installation actually supports and how they coordinate with the service.
Pausing collection and pausing service are different decisions
A business might let a customer temporarily stop using the service, prevent the next collection attempt or interrupt the whole relationship for an interval. These options have different consequences. Retaining an account does not necessarily mean retaining every feature.
| Decision | What changes | What to clarify |
|---|---|---|
| Stop future attempts | Collection schedule | Treatment of periods and documents |
| Suspend access | Service use | Whether any payment obligation continues |
| Interrupt a period | Delivery and dates | Previously purchased service time |
| End continuation | Future renewals | Final date and possible new signup |
The Stripe collection-pause documentation illustrates that stopping collection can differ from changing subscription status. This is a conceptual example from another system. Your integration determines the applicable behaviour, rather than the name of someone else's feature.
Start with the customer's current period
Check the start, end and confirmed payment for the period. A pause request does not erase that history. Establish which service has been used and what remains valid before changing the calendar.
Imagine a membership with access from 1 to 31 October. The customer requests a pause on the 18th. You might design a policy that takes effect at period end. Access then continues until the stated date, with the next stage starting afterwards. Any other behaviour needs an explicit definition and implementation check.
Do not infer an automatic period extension or financial adjustment. Stopping use, carrying days forward and changing a payment are different actions. The commercial policy needs to specify which apply, and the integration needs to represent them.
Define a start date and a way back
A pause with an end date needs an explicit schedule. Explain when current access ends, when it can resume and when the next payment would happen. Avoid “come back next month” when a specific date is available and matters to the customer.
If duration depends on a later request, assign who receives it and how it is confirmed. Keeping an account on hold does not establish automatic reactivation. Customers need to know their next action, and your team needs to be able to find the case.
Include changes of mind. If someone wants to return early, review the effect on the period and next payment. Sales, support and the application should be able to explain the same rule. Our subscription plan guide helps organise these conditions.
Review actions already scheduled
Before applying a pause, check for an outstanding renewal, an operation in progress or an unresolved earlier issue. A new instruction does not make an already initiated transaction disappear.
If payment awaits confirmation, check its result before another financial action. If confirmed, associate the period with that payment. Our failed renewal guide explains how to distinguish states and avoid duplicate charges during review.
Check messages and tasks as well. A renewal reminder may remain scheduled even after the policy changes. The application should stop announcing a charge that no longer applies, or clearly explain an operation still outstanding from the earlier period.
Explain the effects before confirming
The confirmation should answer four questions: when the pause begins, what access remains, what happens to the next payment and how to return. Use dates where available instead of relying on a status label.
For example: “Your pause will begin when the current period ends. You can use the service until the date shown. To return, request reactivation and we will confirm the new schedule.” That wording is appropriate only when it describes the policy you will actually apply.
After implementation, confirm the observed result. “We received your request” and “Your pause is in effect” describe different states. Customers need to know whether review remains outstanding, particularly when the next due date is close.
Verify the return journey separately
On return, identify the correct plan, period and payment method. If the customer needs to take an action on their method, prepare that journey. Do not assume that an earlier reference will always support a later charge without intervention.
Decide when access is restored under your policy. If confirmed payment is required, use the corresponding financial outcome. If there is a stage without collection, define and represent it in the system. Reactivating an account is not itself payment confirmation.
Our payment lifecycle documentation separates subscription and payment events. That distinction lets you check what actually changed and prevents a status update being interpreted as money received.
Test a pause from request to return
Prepare a test with an active period and a known next renewal. Request the pause under the designed policy, then inspect the schedule, access and messages. A “paused” label does not establish that all three parts are correct.
Test the return too: effective date, new period, payment where applicable and correct access. Add a repeated request to detect duplicate actions. Include cancellation during the pause to ensure the system does not restart a relationship the customer already ended.
The AndorPay API documents available operations. A status appearing in a list does not demonstrate a complete pause-and-resume journey. We review the specific scope before turning this policy into a feature offered to your customers.
Record expected dates before testing. Otherwise, a changed renewal date can look plausible without matching the intended policy. A short expected-versus-observed record gives the team a concrete basis for deciding whether the setup is ready.
Prepare your policy with five facts
Describe the need you want to meet, the pause start, treatment of the current period, how the customer returns and the resulting calendar. That description supports both communication and integration review.
If the desired pause does not yet fit the available operation, define a concrete, verifiable process for handling requests. Do not promise an instant action the team cannot carry out and check.
Tell us how you want to handle subscription interruptions. At AndorPay, we review collection, periods and the access connection to prepare a proposal matching your installation.
Frequently asked questions
Does access remain available during a pause?
That depends on the policy and implementation. It may continue until the current period ends or follow another explicit rule. Confirmation should say what the customer can use and until when.
Does pausing refund an earlier payment?
It should not be interpreted that way. A pause governs continuation; handling an earlier payment is a separate financial process with its own requirements.
Does the subscription resume automatically?
Only where that behaviour is planned and verified. If a request or payment-method update is required, explain it before applying the pause.
