A one-off payment settles a purchase. Instalments divide that purchase into several due payments. A subscription renews a service or access under agreed terms. All three may use a card, but they change what the customer buys, what remains outstanding and when the relationship ends.
Choose the model by starting with delivery: what do you provide, and for how long? Then define the payment schedule. At AndorPay, we connect that journey with your business operations from Andorra. The configuration needs to represent the offer you sold so that payment, access and customer messages tell the same story.
Three models that need different explanations
A monthly payment date does not automatically make a sale a subscription. You might collect one part of a completed purchase each month, or collect payment for a new service period. The calendar looks similar, but the commercial relationship and required follow-up differ.
| Model | What the customer buys | What you track | How the journey ends |
|---|---|---|---|
| One-off payment | A defined product or service | Payment and delivery | Purchase completed under its terms |
| Instalments | One purchase spread across due dates | Payments and outstanding balance | Schedule completed or an exception resolved |
| Subscription | A service continuing through periods | Renewal, access and cancellation | Continuation ends under the agreed policy |
Use clear language on the sales page. “Buy the course” and “Subscribe to the library” describe different commitments. Calling instalments for a fixed purchase a “membership” may lead customers to believe that cancelling removes the remaining scheduled payments.
One-off payment: one purchase and a delivery outcome
A one-off payment fits a defined purchase, such as a product, session, report or specific piece of content. Operationally, associate the payment with that purchase and deliver what was promised when the relevant conditions are met.
Define when delivery is complete. Downloading a file, receiving a physical item and booking an appointment need different checks. Confirmed payment may start the process, but does not establish that the entire service has already been provided.
Do not confuse one-off payment with unlimited access. A course bought outright may still have a stated access duration. A report may include a limited review scope. The payment model explains when money is collected; the offer explains what entitlement the buyer receives.
What happens after payment
Prepare a confirmation identifying the purchase and next action. If the customer needs to book a time, sign in or provide information, say so. A generic screen leaves them searching for instructions and may look like a problem even when payment succeeded.
For a straightforward selling journey, read our guide to payments without building your own checkout. Choose the integration approach after establishing how the purchase will be delivered.
Instalments: one purchase with several due dates
With instalments, the customer buys a defined service and spreads payment across a schedule. Retain the purchase amount, planned instalments, confirmed payments and remaining balance. Paying one instalment does not necessarily mean the purchase is fully settled.
Explain the number of payments, their dates and their relationship with delivery from the beginning. If access starts after the first instalment, make that rule visible. Where work or delivery has milestones, connect them to the agreed conditions rather than leaving the buyer to infer the relationship.
The WooCommerce payment plan documentation illustrates that instalment schedules require their own management. Software supporting subscriptions does not automatically establish support for a finite payment plan. Check the specific capability and its integration with your payment method.
Example: a course with a payment schedule
Imagine a complete course with its sessions already defined. Students can pay for the purchase at once or divide it across several due dates. The course they buy remains the same; the schedule and balance tracking change.
If an instalment fails, identify the purchase it belongs to, which payments are confirmed and what remains due. The operational response is not simply to cancel a monthly renewal: an existing purchase needs to be reviewed under the conditions explained to the customer.
Also prevent collection after the final due payment. Completion of the schedule must be a verifiable condition. An indefinitely renewing configuration does not accurately represent a purchase split into a limited number of payments.
Subscription: a service that continues
Subscriptions fit an ongoing or renewed service: an application, a resource library, regular professional support or participation in an activity. Each period relates to something the customer can use during that time.
Define the start, frequency, continuation and cancellation rules. For monthly access, explain what renewal does and how long someone keeps the service after deciding to leave. Access policy and financial scheduling need to work together.
A subscription does not guarantee future revenue. Customers can cancel, payments can fail and plans can need changes. The operational goal is to organise an ongoing relationship; the outcome still depends on the service, demand and how it is managed.
Example: a library adding new material
Imagine a library adding resources and sessions regularly. The customer buys access during each valid period. Renewal extends that access; cancellation determines when continuation ends under the agreed policy.
This journey needs both payment and service-state management. A subscription may be recorded while its first payment is awaiting confirmation. An account can still exist after access expires. Separating those states helps explain what the customer can do at each point.
Our guide to selling a digital service by subscription develops the connection between the offer, collection and access.
Choose according to what you promise to deliver
Ask three questions. Does the purchase have a defined end result? Does the customer receive a new or continuing service each period? Does the schedule stop after a number of payments, or continue under renewal terms? The answers usually clarify the model you are selling.
Then check how customers understand it. If they expect a complete product, an unexpected subscription can create objections. If they expect to use a service while they need it, instalments for a fixed purchase may not match that intention.
You do not need the most complicated model to start. A defined service can be sold with a one-off payment. An ongoing relationship can begin with a straightforward subscription. Add options when they meet a specific need and you can support their operation.
This also helps keep the offer consistent across channels. A sales conversation should describe the same commitment as the landing page. When different wording changes what customers think they are buying, the issue belongs in the offer before it becomes a payment configuration problem.
How day-to-day management changes
For a single sale, check confirmed payment and completed delivery. For instalments, also track due dates and balance. For subscriptions, coordinate periods, renewals, changes and cancellation.
| Situation | One-off payment | Instalments | Subscription |
|---|---|---|---|
| Confirmed payment | Deliver the purchase | Update the instalment and balance | Apply the relevant period |
| Pending payment | Check the same transaction | Review the affected due payment | Review the affected renewal |
| Request to stop | Review purchase terms | Review the purchase and balance | Apply the cancellation policy |
| Planned ending | Completed delivery | Final payment resolved | Service end date |
In every case, check the financial outcome before requesting another payment. A browser without confirmation does not prove a decline. If payment is confirmed but delivery is missing, resolve delivery using the existing transaction.
Keep the person's request distinct from the action performed. “Customer asked to stop” is a useful record, but it does not establish which scheduled actions have actually ended. Your team should be able to see both the request and its verified effect.
Keep the website and checkout consistent
The product name, selected model and frequency need to agree. Customers should not choose a one-off purchase and encounter renewal terms they did not understand. They should not select instalments and lose sight of how many payments make up the schedule.
Explain delivery timing and the next step before purchase completion. Clear information prevents a commercial decision from becoming a support question later. Review the mobile journey, where important terms may be far from the payment button.
The confirmation should repeat the essentials: what was purchased, which payment is confirmed and how to receive or access the service. If payments remain, the customer needs to recognise that the schedule continues. If there is renewal, they need to know where to check the period and manage continuation.
Verify technical fit before advertising a model
One-off payments, recurring payments and finite schedules need different capabilities. Our API documentation describes available contracts; subscription enablement depends on the merchant configuration. An integration must be reviewed against the particular rules you want to sell.
If a tool offers payment only through Stripe and blocks onboarding for your Andorran company, we can review how to connect the journey through your setup with AndorPay. Our page about taking payments from Andorra explains that approach.
Do not present a model as available until purchase, confirmation, tracking and completion have been checked. An example from another tool does not prove that your installation has the same functions. Scope should reflect the behaviour of the chosen integration.
Test the differences that matter
For a one-off purchase, test confirmation, abandonment and delivery. For instalments, add an intermediate due payment, a failed one and the last payment. For subscriptions, add renewal, cancellation and access at the end of the period.
Check that a repeated notification does not deliver twice or update the balance twice. Maintain a clear relationship between purchase, transaction and period or instalment. That makes it possible to handle exceptions without improvising new financial operations.
Before configuration, prepare a short description of the service, model, schedule, delivery and exception handling. Tell us what you sell and how you want to collect payment. We can review the journey with AndorPay and prepare a private proposal for the setup.
Frequently asked questions
Does paying monthly mean someone has a subscription?
Not necessarily. Monthly payments may be instalments of a fixed purchase. A subscription is distinguished by the service relationship and continuation agreed with the customer, rather than payment frequency alone.
Can I offer both a one-off purchase and a subscription?
You can design distinct offers if buyers understand what each provides. Define the content or service belonging to each model and verify that the integration maintains those entitlements without confusing them.
Does cancellation mean returning previous payments?
These are separate operations. Cancellation governs future continuation under the applicable terms; handling a previous payment requires a separate process. The system needs to represent both accurately.
