Andorpay
Back to the blog

Published on · Updated on

Membership fees and management in Andorra

Organise signups, membership fees, failed payments and cancellations. Connect payment records to member profiles, service periods and access.

Membership card organiser beside a calendar and an access key.

Managing memberships in Andorra means connecting three things: who belongs to your organisation, which fees they owe and which services they can use. Online payments cover part of that journey. To make daily administration work, the payment result must reach the right member record and trigger the intended update.

A member might have an outstanding fee while temporarily retaining access. One person might pay for several family members. Another might request cancellation today but remain entitled to a service until their paid period ends. Reducing all those situations to an “active” checkbox leads to phone calls, separate spreadsheets and inconsistent answers.

This guide explains how to organise signups, renewals, payment issues and cancellations, then connect payments to your membership administration.

Define what membership means in your organisation

An association, professional community and learning membership can all collect regular fees without managing the same relationship. Before selecting software, describe what each member receives and the decisions your team needs to make.

In an association, membership and its associated rights may depend on the organisation's own rules. A digital library might provide content access for a defined period. A club could include certain activities in its fee while charging separately for other bookings.

Create a brief for each membership type covering eligibility, start date, service period, included benefits, renewal and cancellation. If someone must approve applications, identify who does that and whether payment happens before or after approval.

Do not automatically turn every payment into an admission. Where an application requires approval, there are two decisions: accepting the person and confirming their payment. Plan the order so you do not collect a fee that cannot be attached to a valid membership.

Separate the member record, fee and access rights

The member record identifies the person and their relationship with the organisation. The fee describes what is payable for a period. Access rights determine what that person can use today. Keeping these separate lets you handle exceptions without rewriting the history.

Element Information worth keeping
Member Stable reference, contact details and membership type
Fee Purpose, covered period, due date and payment status
Access Available services and the date entitlement ends
Change Request, effective date and reason
Payment Transaction reference and received confirmation

Generating a fee notice does not prove that it has been paid. Cancelling a subscription does not necessarily mean immediately removing access that has already been paid for. Your system needs to interpret each signal according to your rules.

The WooCommerce Memberships documentation distinguishes memberships and content restrictions from subscriptions that can fund that access. The distinction is useful when designing a journey, even if you use different software.

Identify the member and the person paying

They are often the same person, but not always. A company might fund a professional's membership. A parent might cover several family memberships. Creating a new member record whenever money arrives eventually produces duplicates and mixes up activity histories.

Give each member a stable reference, then link the payer and the fees they cover. If one payment covers several memberships, make the allocation explicit. A free-text note that only its author understands is not enough for reliable follow-up.

Imagine two family members attending different activities. They share a payer, but each has a membership type and dates of their own. If one leaves, you need to stop the relevant fee without cancelling the other person's service.

Before launching a family option, check that your administration can represent that relationship. Software designed around one subscription per account may need adaptation. Several email addresses do not, by themselves, establish the relationship between members and a shared payer.

Design signup through to service activation

The application form should collect what is needed to create the member record and assign the correct fee. When an existing member books another activity, avoid asking for their entire profile again. That creates an opportunity for a second identity to appear.

A signup journey can follow these steps:

  1. The person chooses a membership and reviews what is included.
  2. They provide their details and accept the applicable terms.
  3. The application is approved if that membership requires it.
  4. Payment starts against the member record and service period.
  5. The payment result is confirmed.
  6. The intended access is enabled and the member is informed.

There may be a delay between starting payment and receiving confirmation. If the browser closes after payment, the result should still be able to reach your application. Someone should not need to sign up again because they never saw the final page.

Also prepare for an unfinished payment. The application can remain pending without creating an active member whose fee appears to be paid. Provide a clear way to continue while keeping the original reference.

Choose a fee calendar people can understand

Some memberships begin on the signup date. Others follow a season, academic year or shared annual period. A monthly payment might be a renewable subscription or an instalment within a commitment of fixed duration. Those are different agreements.

For each membership type, define the service start, period covered, first payment date and renewal rule. If all fees fall due on the same day, decide what happens to people joining partway through the period. Do not promise a proportional adjustment before checking how it will be calculated.

Imagine a community with a shared membership year. Someone joins shortly before it ends. They need to know whether their fee covers the remaining year or starts twelve months of their own. Both models can make sense. Confusion arises when the signup form implies one and the payment schedule follows the other.

Show specific dates in the confirmation. “Annual membership” alone does not explain whether renewal is automatic, when another payment will happen or which period the customer has bought.

Connect payments to the tool you already use

If your current software handles member records, activities and communications well, first examine how it receives payment results. Replacing your entire administration to fix payment collection alone can create unnecessary migration work.

Check the links between the member reference, fee reference, payment initiation, confirmed result and status update. Integration may be required. Having a field called “customer” in two tools does not mean that they exchange the right information.

At AndorPay, we help connect payment collection to your business journey. Our payment lifecycle documentation distinguishes confirmed payment from subscription changes and document creation. That lets your application decide which update belongs to each event.

If you want recurring card payments from Andorra, the bank payment terminal configuration and enabled capabilities also need checking. Our guide to subscriptions on an existing TPV explains that preparation. Bookings, membership cards and member rights need to be covered by your membership software and the agreed connections.

Handle failed payments without losing context

A failed payment might require updated card details, an action from the cardholder or further investigation. It does not automatically mean the person wants to leave, and it does not erase their relationship with your organisation.

Define who reviews the issue, when the member is contacted, how long they have to resolve it and which services remain available meanwhile. That period should follow the membership terms, rather than whoever happens to answer the phone making a new decision.

The message should identify the fee and period, explain that payment is not confirmed and give the next step. Avoid a broad accusation of unpaid debt while you are still investigating a pending transaction.

Before asking for another payment, check the previous attempt. If confirmation already exists, correct the member record. Repeating payment to solve a synchronisation problem can produce a second charge.

Give cancellations and changes an effective date

A cancellation has a request date and an effective date. Keep both. It may stop a future renewal while leaving the paid service period unchanged, or follow another rule specified for that membership.

Tell the member when their access ends and whether any fee still needs clarification. “Your cancellation has been processed” may not answer whether they can attend an activity next week.

For a membership change, record the old type, the new type, the effective date and the treatment of fees already issued. Changing a label on the profile without reviewing the schedule can leave an old charge running.

Pauses need their own rules too: duration, access during the break and the return date. Our guide to pausing a subscription helps define those decisions before looking for a particular software feature.

Organise a daily review and a period close

The daily review should highlight exceptions requiring action: paid signups without access, unmatched payments, failed fees and cancellations approaching their effective date. It should not require you to inspect every member record one by one.

Give each issue a next action and an owner. A list of incidents without a pending decision soon becomes another spreadsheet that nobody maintains. When closing a case, keep the payment or change reference explaining its resolution.

At the end of the period, compare expected fees with confirmed payments and the corresponding settlement movements. The payment date and the date money reaches the bank can differ. Do not mark a member as unpaid because you are looking at the wrong record.

If you accept payments through other methods, include them with a reference and date. They belong in the membership overview without being presented as transactions processed by a channel that did not handle them.

Migrate without collecting the same fee twice

Before changing software, prepare a member list with stable references, membership type, paid service period, next fee and pending changes. Distinguish a genuinely unpaid fee from payment history that simply has not reached the new system yet.

Choose a cutover date and assign every renewal to one system. Two active schedules for the same fee can create duplicate collection. Your migration needs to identify which system will charge before and after that date.

Do not assume that a saved card can be transferred to another provider. Check what is actually possible and, when needed, prepare a process for members to update their payment method. Explain what they need to do and whether any dates will change.

Start with a small set of representative cases: new signup, normal renewal, family payer, payment issue and scheduled cancellation. Check the profile, fee, messages and access. Successfully importing names is only one part of verifying the migration.

Prepare the information for your next decision

Bring together your membership types, fee calendar, current software, payment methods and the problems that consume the most time. A complete example of the member journey is often more useful than a long list of desired features.

The outcome is specific: explain why a person has access, which period they have paid for and what will happen at their next renewal. When those answers are connected, handling a signup or a support request requires less manual reconstruction.

If you manage an association or membership service in Andorra, tell us how you organise fees and which part of collection makes daily work harder. At AndorPay, we will review the connection to your current administration and the payment journey you need to complete.

WhatsApp