Automating payment collection for a business in Andorra means making sure a confirmed payment is correctly reflected in the order, customer record and administrative work. The bank payment gateway handles its part of the transaction. The full workflow comes together when connected systems know what to do with the result and which cases a person needs to review.
If you currently check the bank, find the order, update a spreadsheet and email the customer, you have a specific sequence to improve. Start by identifying the information each task needs. Adding reminders before fixing that connection can create more messages without removing work.
This guide offers a practical order for choosing your first automations, assigning responsibility and checking whether the complete workflow works.
Start with a task you repeat after payment
Choose something frequent and easy to describe: marking an order as paid, activating a membership, recording a fee or flagging a problem. Write down what someone currently does between learning the payment result and finishing the task.
For example, a monthly training service might involve checking payment, finding the learner and extending access. If the learner's reference is missing, payment speed is not the problem. The transaction lacks a reliable link to the account it belongs to.
Describe the workflow in one sentence: “When this payment is confirmed, update this account, for this period, using this reference.” Add the exception: “If the account cannot be found, create a review task.” That lets you evaluate a specific improvement without replacing every tool you use.
Start with a process you already understand. If you have not decided which service the customer is buying or when it starts, settle those rules first. Automating a decision that changes every week moves the uncertainty into your software.
Use this map to set priorities
The automations below are outcomes you can plan for your integration. Their availability depends on your business tools and their connections. The map helps define what you need before asking someone to implement it.
| Priority | Starting signal | Expected outcome | Exception and owner |
|---|---|---|---|
| Confirm the purchase | Confirmed payment and identified order | Order updated once | Reference without an order: operations |
| Enable the service | Valid payment and service period | Access for the correct period | Incompatible account or plan: service owner |
| Prepare the next charge | Current schedule and subscription | Renewal attached to the right period | Pending cancellation or change: administration |
| Handle failure | Confirmed failed result | Useful next step for the customer | Uncertain result: payments support |
| Prepare the period close | Recorded payments and settlement data | Matched amounts and listed differences | Unmatched movement: administration |
You do not need to start five projects at once. If the team spends more time searching for paid orders than dealing with failed payments, begin with the first row. If payments are recorded correctly but customers remain locked out, the second row is the priority.
In a small business, one person may fill several roles. What matters is that every exception has somewhere to go, and that “automated” does not become shorthand for “nobody checks it”.
Link each payment to references you can follow
The customer reference tells you who is buying. The order or fee reference identifies what they are paying for. The transaction identifier lets you check what happened on the payment side. All three relationships matter, and none should depend solely on a name entered by hand.
Keep those references when someone resumes payment or contacts support. Creating a new order whenever a page is slow can break up the history and leave several apparently valid operations for a single purchase.
Imagine a customer says: “I have been charged, but my account is still locked.” Your team should be able to find the fee, check the payment result and review activation. If payment is already confirmed, the answer may be to finish updating the service without collecting money again.
AndorPay's API reference documents a stable external customer reference and the information needed to start checkout. The integration must preserve that relationship in the application delivering the service as well.
Make each confirmation produce one update
Customers can close their browser after paying. A notification may arrive late or be delivered more than once. The success page therefore should not be the only signal that activates an order or an account.
The receiving system needs to recognise the operation and know whether its effect has already been applied. Receiving the same information again should not extend access twice, send two fulfilment requests or record two separate payments.
This is part of notification handling. Adyen's webhook event documentation accounts for duplicate deliveries. At AndorPay, our webhook guide explains verification and handling repeat deliveries.
For the business owner, the requirement is straightforward: one confirmed purchase should produce one outcome, even if its message arrives more than once. The technical team can implement that behaviour without exposing the details to the buyer.
A missed update also needs a recovery path. Repairing an order's status and starting a new payment are different actions. They should not become interchangeable simply because both appear during a payment support incident.
Specify what changes in the order and the service
A paid order may still need fulfilment. A collected membership fee may enable the next month without changing the customer's other services. A paid booking may require another confirmation if a remaining availability condition has not yet been resolved.
WooCommerce's order statuses distinguish a paid order being processed from a completed order. That distinction is a useful reminder that collecting payment and finishing delivery do not always happen at the same moment.
For each automation, specify which field changes, how long the effect lasts and which message the customer receives. “Activate the customer” is too broad if one account can contain several memberships or purchases with different dates.
A more precise rule would be: “Enable the purchased library until the end of the period attached to this fee.” If the customer also has a consulting session booked, that entitlement should not change because of the library payment.
Keep administrative documents separate from the payment result too. Creating an invoice or receipt does not, by itself, establish that the money has been collected. Whoever handles the documents needs a way to identify the related transaction.
Base recurring collection on a current schedule
A subscription's next charge depends on the agreed terms, service period and pending changes. Before adding reminders, check that the schedule is consistent and that cancellations or plan changes reach the system initiating renewal.
With AndorPay, subsequent charges require the bank terminal's tokenisation and recurring payment capabilities. Our payment lifecycle documentation explains the distinction between payment confirmations, subscription changes and generated documents.
The business outcome is that the next fee reflects the terms still in force. If someone requests cancellation at the end of their period, the system needs to preserve the agreed access and respect the renewal cancellation under the applicable rule.
Pay particular attention to changes near the due date. Before modifying the schedule, establish whether the next operation has already started and what state it is in. A request received by support does not prove every system has applied it.
Our guide to recurring Redsys payments in Andorra develops the requirements to check when preparing that part of the journey.
Automate the next step when something goes wrong
A useful automation does not need to solve every failure independently. It can identify the case, prevent an inappropriate action and route the issue to whoever has the information needed to resolve it.
Distinguish at least three situations. If payment is confirmed but access is missing, review the service update. If payment has definitively failed, prepare the permitted recovery step. If the result remains pending, check its status before asking the customer to repeat the purchase.
The message must match the situation. “We are checking your payment result” and “This payment could not be completed” describe different states. Do not send an overdue-payment reminder simply because an integration has not yet updated the customer record.
Keep a reference, owner and next action for every issue. If technical help is needed, that information lets the team investigate the journey without disconnected screenshots or asking the customer to explain everything again.
Recovery attempts need limits and follow-up too. Receiving a failure event does not automatically define when another charge should be attempted. That policy must be agreed and supported by the integration's capabilities.
Prepare the close without confusing payment and settlement
At the end of a period, administration needs to connect sales, payments and money arriving in the bank. These do not necessarily happen on the same day or appear at the same level of detail. A settlement can group transactions and contain adjustments that need identifying.
Prepare a relationship that takes you from order to payment and then to its settlement. If something does not match, keep the difference open for review. Do not force a match by changing the customer's status before understanding where the discrepancy came from.
Useful automation may simply prepare the data and highlight exceptions. It does not require assuming there is already a complete accounting connection to any application. Check which exports or integrations each tool supports before promising that connection.
If a transaction is corrected or refunded, retain its relationship to the original payment and record the procedure used. Having statuses that represent a refund does not establish that your integration can execute one automatically.
Measure unfinished work and complete outcomes
Track the time between confirmed payment and updated order, the number of unmatched payments and the cases requiring intervention. Separate them from declined payments: access that has not been updated is a different problem from a card that cannot complete a transaction.
Look at the age of open issues as well. A short list of cases nobody resolves can be more concerning than a longer list cleared every day. The measure should help you decide where to act.
When comparing before and after, use similar periods and note changes in activity. A week with fewer sales or renewals does not, by itself, demonstrate that automation has improved the process.
A short review can answer four questions: what completed without intervention, what remains pending, who owns it and which rule needs adjusting? That is more useful than counting how many notifications were sent.
Finish one workflow before extending it
Choose a membership type or order category and document its starting point. Connect payment confirmation to the expected outcome, prepare the exception route and make sure the team knows where to find unresolved cases.
The TPV integration testing guide goes deeper into technical scenarios. The operational decision here is recognising a ready workflow: payment completes, the customer receives what they bought and administration can explain what happened.
Keep a way to review the first transactions and recover missed updates without duplicating charges. Then extend the process to other plans that share the rule or need a clearly defined variation.
If you want to automate payment collection from Andorra, tell us what happens after each payment today and which task you repeat most often. At AndorPay, we will review the journey, available connections and the first improvement that can complete the work from start to finish.
