Skip to main content
The Payments tab is the record of every payment your organization has taken - manual payments logged by staff, card payments captured by a provider, wallet balance spent at checkout, and wallet top-ups. Use it to see what has been collected, which method was used, who recorded it, and to issue refunds. A payment pays one or more charges (what is owed); the payment carries an amount, a method, a status, and a link to the charges it paid. Front-desk staff record the money they take at the counter, and owners and admins review payments and issue refunds.

When to use it

Payments are created when a member pays online, when a stored card is charged automatically, or when a staff member records a manual payment at the front desk. You do not have to settle a balance in one go: take part now, combine a method with the member’s wallet balance, or give each player on a booking their own share. When money has to go back, you choose whether it returns to the card or to the member’s wallet. Typical uses:
  • A deposit now, the rest on arrival - a padel member pays half for an area booking at the desk and settles the remainder when they arrive.
  • A four-ball paying their own quarters - four members split a 60.00 area booking, each paying their own share, with a member on a membership covered at no charge.
  • A monthly fee partly from the wallet - a boxing member with 10.00 in their wallet owes 40.00, so you use the wallet balance and charge 30.00 to the card at the point of sale.
  • A cancelled tournament refunded to the card - you refund a 40.00 card entry back to the card, or return it instantly to the member’s wallet if they will book again.
See Worked examples for the details of each.

The payment list

Open Sales > Finance > Payments to review payments, filter by status, and drill into a single payment. The grid shows these columns:
  • Date - when the payment was recorded.
  • Type - what it paid for: the type of its charge (for example Membership or Booking), Top up for money paid into a wallet, or Invoice.
  • Contact - the member the payment is for.
  • Reference - what it paid: the first charge’s reference, with ”+ N” when it paid several, or the invoice number.
  • Amount - the payment amount and currency.
  • Payment Method - the method used (for example Cash, Card, or a card provider).
  • Status - the status chip. A pending payment reads Unpaid.
  • Created by - the staff member who recorded the payment.
Tabs across the top filter by status: All, Succeeded, Pending, and Failed, each with a count. Where you have the right permission, the row action menu offers Delete for eligible payments (see Deleting a payment) and Write off this payment for a stuck card reader payment (see Writing off a stuck card reader payment). The Created by column is empty for payments captured automatically by a provider (online checkout, automatic membership renewals) - those are recorded by the system. For payments recorded by staff (front desk, phone, bank transfer), it shows the staff member’s name.

The payment panel

Click a row to open the payment in a side panel over the list. It shows:
  • The payment’s reference (or Top up, or the invoice number) with its status, and a Test chip for a test-mode payment.
  • The Contact, Amount, Payment Method, and a link to the invoice when there is one.
  • What has been Refunded, and any Refund pending with the provider.
  • The provider’s references, for example the Stripe Payment Intent ID and Charge ID, the myPOS order ID and transaction reference, or the DatecsPay order and RRN.
  • Charges - every charge the payment paid. Click one to see it inside the panel.
  • Created by, and when.
The panel’s only action is Delete. Refunds are issued from the charge - see Refunds. Old links to /billing/payments/<id> open the same panel.

Payment status

A payment moves through these states:
  • Pending - Recorded but not yet settled (for example a manual payment awaiting confirmation, or an online payment mid-flow).
  • Processing - The provider is capturing the payment.
  • Succeeded - The money is in. This is the only state a payment can be refunded from.
  • Failed - The attempt did not go through.
  • Cancelled - The payment was called off before it settled.
  • Refunded - The full amount has been refunded.
  • Partially refunded - Part of the amount has been refunded.

Recording a payment

Most manual payments are recorded as part of a flow rather than from a blank form - completing an order, settling an invoice, or taking money at the point of sale all record a payment behind the scenes. When you record one, 1club needs:
  • Amount - How much is being paid.
  • Payment method - Which configured method the money came in on (see Payment methods).
  • What it settles - A charge, several charges, or an invoice.
For example, completing a draft order opens the Complete order dialog, where you pick a payment method; 1club then records a payment against each of the order’s unpaid charges with that method. See Orders.
Payments handled entirely by a provider’s own checkout (for example an online card payment via the hosted flow) are captured by that provider and cannot be re-recorded as manual payments. Log manual payments for money you collect yourself - cash, a card terminal, or a bank transfer.

Payment methods used

Each payment records the method it came in on. Methods belong to a channel:
  • Manual - Methods you take and log yourself, such as cash, an in-person card terminal, or a bank transfer. You define these under Payment methods.
  • Card provider - Online card payments captured through the connected provider’s checkout.
  • myPOS - Payments taken through a myPOS terminal or link. See myPOS.
  • Wallet - The member’s wallet balance, spent towards what they owe (see Wallet).
The method shown on a payment tells you where the money physically came from, which matters when you reconcile the till or a bank statement.

Partial and split payments

You do not have to settle a balance in one payment.
  • Partial payment (one charge) - Record less than the full amount against a single charge. The charge moves to partially paid and keeps an outstanding balance you can collect later.
  • Settling several charges at once - You can record one payment against multiple charges, but only when the payment covers all of them in full. A single lump sum cannot be split partially across several charges, so a multi-charge payment must equal the sum of their outstanding balances.
  • Dividing a booking between its players - Give each player on a booking their own share and their own way of paying it. See Splitting a booking across its players.

Splitting a booking across its players

Four people book a padel area and each want to pay their own quarter. Rather than one person paying and chasing the others, split the bill so each player owns their own charge. On the booking’s detail page, use Split payment (or Edit split if one already exists). The dialog explains:
Divide between the players. Each one can pay their own way. Shares are shown before tax.
For each player you set:
  • Share - their slice of the price, before tax.
  • Pays with - how they are covering it: paying directly, a membership, or an external program. Until they choose, the row reads Not chosen yet.
A player covered by a membership or program shows as Covered and is charged nothing - their entitlement is used instead, exactly as it would be on a booking of their own.

Even and custom splits

  • An even split divides the price equally and re-divides it whenever the roster changes. Add a fifth player and all five shares rebalance, rather than leaving a gap.
  • A custom split takes the amounts you enter. Because the shares are the price in that case, changing them reprices the booking, and 1club tells you so before you save: “This changes the booking price from to .” That is intended - charging the four players more or less than the area’s list price is a legitimate thing to do at the desk.
Two rules are enforced on save: no share may be negative, and everyone holding a share needs a payment method.

Collecting each share

Each player’s share becomes their own charge, so you collect them independently from the players list on the booking, or from Charges like any other charge. A player who has settled is marked as such even while others still owe. This also drives entry: the check-in gate asks whether this player has paid their own share, so three players who have paid are admitted while the fourth is still outstanding.

Re-splitting after money has changed hands

You can edit a split after players have paid. Anything already collected goes to the player’s wallet, not lost:
Anything already paid goes back to that player’s wallet, so they can settle their new share from it.
Memberships and program entries consumed by the old split are given back before the new one is applied, so re-splitting twice never quietly drains a member’s allowance.

Splitting across a method and the wallet

You can combine a primary method with the member’s wallet balance in one checkout:
  • Member portal - The wallet balance is used automatically. The order deducts the wallet balance (up to the amount due) and the member pays only the remainder by card or on arrival. The breakdown shows a Wallet line (for example Wallet: -10.00) above the total, and the Pay button reflects the post-wallet amount.
  • Admin point of sale - When you take a payment with a primary method (card, cash, and so on), you can also use the wallet as a second payment with the Also apply wallet balance ( available) checkbox and an Amount from wallet field. The split is shown as “Wallet + via primary method”. The wallet toggle is hidden when the wallet already covers the full amount (you can then pay entirely from the wallet).
The amount drawn from a wallet is always capped at the member’s balance and the outstanding amount.

Refunds

Refunds are issued from the charge, not from the payment, and you choose where the money goes. Open the charge in Charges and use Refund.

Issuing a refund

  1. Open the charge from Sales > Finance > Charges.
  2. Choose Refund from the charge’s row menu. The Refund dialog opens.
  3. Answer Where should the money go? (see the destinations below). Each option shows how much it can return, because they differ. The question is only asked when there is more than one place the money can go.
  4. Set Amount to refund. It defaults to everything still refundable, and cannot exceed what the destination you picked can return.
  5. Optionally add a Reason (optional).
  6. Click Issue refund.
Refunds need the billing.delete.club permission.

Choosing a destination

Only options the original payment supports are offered. Back to the card appears only for payments taken through Stripe: money collected through myPOS, DatecsPay, or Hype cannot be reversed through those providers from 1club yet. The wallet is offered only when the payment was taken by your default billing entity, which holds the wallet. When neither is possible, the dialog says “This charge can’t be refunded here: the money can’t go back to the card or to the member’s wallet. Return the money to the member directly.” What each destination can return is calculated per payment. A charge paid partly by card and partly from the wallet can return only the card part to the card.

Card refunds are not instant

When you refund to the card, 1club tells you:
The refund is sent to Stripe now and usually reaches the member’s statement within 5-10 days. It is drawn from your Stripe balance.
Some card refunds settle asynchronously, so you may see a refund reported as awaiting confirmation:
Refund sent to Stripe - awaiting confirmation. It is not back with the member yet.
That is a normal intermediate state, not a failure. The amount is confirmed once the provider settles it, and the charge’s status updates then. A partial confirmation reads as “X refunded, Y sent to Stripe and awaiting confirmation” - treat only the confirmed part as money the member has back.
Refunding to Wallet balance is immediate and never has a pending state, because no money leaves your account. It is the right choice when the member is standing in front of you and will book again.

Partial refunds

Enter any amount up to the ceiling. Each refund is recorded individually with its amount, destination, reason, and who issued it, so a charge refunded in three instalments has three records rather than one status flag. You can keep refunding until the refundable balance is exhausted.

Nothing to refund

If no money was ever collected on the charge, Refund tells you so:
Nothing was collected on this charge, so there is nothing to refund. Void it instead if it was raised by mistake.
See Voiding a charge for that path.

Automatic refunds to the wallet

Some flows refund a member automatically to their wallet rather than to the original payment, without asking you to pick a destination:
  • A booking is cancelled under its cancellation terms. Only what was paid beyond the cancellation charge is refunded - see Deposits and cancellation charges and Booking policies. When staff cancel a paid booking, they choose Refund in full or Apply the cancellation policy.
  • A member’s entrance method changes at check-in (they paid directly, then a membership or program is used to admit them instead). 1club marks the original payment refunded and credits the amount to their wallet.
  • A booking’s split is edited. Anything already paid goes back to each player’s wallet so they can settle their new share from it - see Splitting a booking across its players.
Cancelling a paid order is different: the Cancel order dialog asks you to pick Original payment method or Wallet balance under Refund to. See Cancelling an order.
Booking cancellation refunds go to the wallet when the booking was sold by your default billing entity. For any other company’s sale, the refund is left owed so you can return it from the charge. To return money to the member’s card, refund the charge and choose Back to the card.
When you send a member a link to pay an outstanding amount, the link opens a branded payment launcher on your organization’s member-facing site. The launcher shows your organization’s logo and theme colours, the amount due, the reference, and the date, with a Continue to payment button that hands off to the payment provider (myPOS) to complete the payment. The launcher resolves to your member-facing site automatically - it uses your verified custom domain, then your published website, then the member portal, then the network, so members land on a branded page rather than a generic one. The launcher also reflects the link’s state, for example:
  • “This payment link has expired”
  • “This payment has already been completed”
  • “Thank you, your payment was received”
  • “Payment cancelled”
Payment links for charges (such as a booking or membership charge) show the charge’s reference. Only genuine invoices are labelled “Invoice #”.

Deleting a payment

Only manually recorded payments can be deleted. That means every method on the manual channel - Cash, an in-person card terminal, a bank transfer, or whatever else you have defined. Those rows are just a record of money taken at the counter, so removing the record is the whole correction. Everything else must be refunded instead, because the money sits somewhere a deleted row cannot reach:
  • Card provider, myPOS, DatecsPay, Hype - the provider is holding the funds.
  • Wallet - the member’s wallet was debited.
Attempting it tells you:
Only manually recorded payments can be deleted. This one was collected through a payment provider or the wallet, so refund it instead.
A manual payment may settle several charges at once - a multi-line invoice, a booking split across an area and an instructor, a point-of-sale order. Deleting it recalculates every affected charge back to paid, partially paid, or pending based on what remains, so you do not have to unpick them yourself. Deletion needs the billing.delete.organization permission.
A payment recorded on a manual method that nonetheless carries a provider reference is also refused. This catches a Cash or Terminal row that actually went through a provider, where the funds genuinely are with that provider despite the method chosen.

Writing off a stuck card reader payment

A payment taken on a card reader can get stuck in Pending when the provider never confirms how it ended. When nothing can resolve it any more, an admin can write it off from the row action menu on Sales > Finance > Payments with Write off this payment. The action appears on pending payments taken on a payment terminal. The dialog asks What did you check? Explain in at least a sentence what you verified. The reason is recorded on the payment with your name, for whoever reconciles the statement. If the payment is still recent enough for the system to resolve on its own, the write-off is refused and you are told why.
Only write off a payment that can no longer be resolved with the provider. A card may in fact have been charged, so check the provider statement before and after. A write-off cannot be undone.
Writing off needs the billing.manage.organization permission, which only admins and owners hold by default.

Worked examples

Padel booking paid half now, half on arrival

A member books a padel area and pays half at the desk, settling the rest when they arrive.
  • Record a partial payment for half against the booking charge; it moves to partially paid.
  • On arrival, record a second payment for the remainder to bring it to paid.

Boxing gym monthly fee split across card and wallet

A member has 10.00 in their wallet and owes 40.00 for the month.
  • At the point of sale, take the primary method (card) and tick Also apply wallet balance (10.00 available).
  • The split shows “Wallet 10.00 + 30.00 via primary method”; the card is charged 30.00.

Cancelled climbing session refunded to wallet

A climber cancels a booked session within the free-cancellation window.
  • The booking is cancelled and, under its cancellation terms, the amount is refunded to the climber’s wallet automatically.
  • The original payment is reflected as refunded; the wallet balance is available for their next visit.

Front-desk cash payment recorded in error

Staff logged a cash payment against the wrong member.
  • Cash is a manual method, so delete the payment. Every charge it touched recalculates automatically, even if it settled several at once.
  • Record the payment again against the right member.
  • Had it been a card payment, deletion would be refused - refund it and re-take it instead.

Padel four-ball, each player paying their own quarter

Four members book a padel area for 60.00 and each wants to pay separately.
  • On the booking, click Split payment. An even split gives each player 15.00.
  • One player is on a membership: set their Pays with to that membership. They show as Covered and are charged nothing, and the other three still owe 15.00 each.
  • Collect each share from the players list as they pay. The two who have paid can check in while the third is still outstanding.

Cancelled tournament entry returned to the card

A member paid 40.00 by card for a tournament that you then cancel outright.
  • Open the entry charge in Sales > Finance > Charges and click Refund.
  • Choose Back to the card, leave the amount at the full 40.00, and add a reason.
  • The refund is sent to Stripe and may read as awaiting confirmation for a few days. Tell the member it typically lands on their statement within 5-10 days.
  • Had you wanted to keep the money with the gym, Wallet balance would have returned it instantly to the member’s wallet instead.

Tips & best practices

  • Refund, do not delete, anything a provider or the wallet touched. Only manual-channel payments can be deleted. Refund the rest so the money actually goes back and the audit trail stays intact.
  • Pick the refund destination deliberately. Wallet balance is instant and keeps the money with you; Back to the card is the right answer when the member is not coming back. Do not use the wallet to avoid a card refund the member asked for.
  • Read Created by to tell manual from automatic. A blank Created by means the provider captured it; a name means a staff member logged it. This is your first check when reconciling the till.
  • Match the method to the money. Record the payment on the method it actually came in on (cash, terminal, transfer) so your Payments tab reconciles against your bank and till.
  • Use partial payments for deposits. Take a deposit as a partial payment and collect the balance later rather than forcing payment in full up front.
  • Split the bill rather than nominating a payer. On a group booking, give each player their own share so each is collected and admitted independently.
  • Send a payment link for outstanding balances. Rather than chasing a member for card details, send the branded payment link and let them pay on your own site.

Troubleshooting

Issue: I cannot find a Refund action on the payment. Solution: Refunds are issued from the charge, not the payment. Find the charge in Sales > Finance > Charges and use Refund in its row menu. You also need the billing.delete.club permission. Issue: Back to the card is not offered as a destination. Solution: The payment was not taken through Stripe. Money collected through myPOS, DatecsPay, or Hype cannot be reversed through those providers from 1club yet - return it to the member’s wallet with Wallet balance, or refund it through the provider yourself. Issue: A refund says it is awaiting confirmation and the member says they have not received it. Solution: That is expected. Card refunds can settle asynchronously and typically reach the statement in 5-10 days. The amount is not back with the member until it is confirmed. Do not issue a second refund for the same money. Issue: Refund says there is nothing to refund. Solution: No money was ever collected on that charge. If it should never have been charged, void it instead - see Charges. Issue: The Delete action is refused on a payment. Solution: Only manually recorded payments (the manual channel: cash, terminal, bank transfer) can be deleted. Provider-collected and wallet payments must be refunded. A manual payment carrying a provider reference is also refused. Issue: A multi-charge payment is rejected. Solution: A single payment can settle several charges only when it covers them all in full. Record separate payments, or record a partial payment against each charge individually. Issue: The wallet toggle is missing at the point of sale. Solution: The wallet already covers the full amount due, so the secondary-tender toggle is hidden - you can pay entirely from the wallet. It reappears when the wallet only partly covers the balance. Issue: One player on a split booking cannot check in although the booking is paid. Solution: Entry is judged per player, not per booking. Check that player’s own share on the booking’s players list - the others having paid does not settle theirs.
  • Orders - Complete an order to record payment against its charges.
  • Charges - The charges a payment settles.
  • Invoices - Invoices generate payments when paid.
  • Payment methods - Configure which payment methods your organization accepts.
  • myPOS - The provider behind payment links and terminal payments.
  • Booking policies - Decide when payment is collected, and the tiered rules for cancellation refunds.