Cards & wallets
Pay by debit or credit card, with Apple Pay or Google Pay where available.
A PRACTICAL GUIDE FOR CLUB ADMINISTRATORS
Set up cards, Pay by Bank and Stripe Bank Transfer for match fees, memberships, donations and sponsorship payments.
Pay by debit or credit card, with Apple Pay or Google Pay where available.
Choose a supported bank, approve the payment and return to checkout.
Send money to the bank details Stripe provides. Stripe matches the funds.
Published standard processing rates, not a quote for your account. Other card types, international payments, conversion, refunds and platform services can cost more. Check Stripe pricing ↗
02 / COMPARE COSTS
Enter a single payment amount to compare the published domestic processing fees. The £5 bank-payment charge is a maximum, not a flat fee.
For £500, you could lead with cards and wallets for convenience, while keeping both bank options available.
Pay by Bank normally has a £10,000 payment limit. The fee above is illustrative; higher amounts need Stripe approval. Offer another eligible method.
Fees rounded to pennies per payment. Excludes optional Stripe services, Connect/platform charges, refunds and account-specific pricing. This tool sends no payment and does not collect financial details.
A starting policy: cards/wallets up to £500; Pay by Bank above £500 up to £10,000; Stripe Bank Transfer above £10,000. These are convenience thresholds, not the amounts at which bank payments become cheaper.
Keep other eligible choices available. Clubs can recommend a method, and members can choose. Pay by Bank already costs less than a standard UK card at smaller amounts; grouping several match fees into one payment can also reduce repeated fixed charges.
At £1,000 and above, both bank methods reach their £5 processing cap under these domestic rates. Choose between them for the payer experience and eligibility, not extra percentage savings.
03 / CLUB ADMIN · LIVE STRIPE SETUP
These steps configure the club’s live Stripe account. No developer commands are needed for these settings. Have an account owner or administrator with access to payment settings complete them.
Choose the club’s account, not a personal or another organisation’s account. If a website or platform manages the payment settings, confirm which configuration it uses. Changes to a shared live configuration can affect existing checkouts immediately.
Go toStripe Dashboard›Account selector›Your club · Live
Do this: Sign in to Stripe Dashboard. Choose your club’s account. Switch to the live account view and make sure test mode is off.
Check before continuingThe club’s name is correct, and you are viewing live payments and settings.
Go toSettings›Payments›Payment methods
Do this: Open Payment methods. If there is a configuration selector, choose the one your website uses. This is often called Default. Use Dashboard search for “Payment methods” if the menu labels differ.
Check before continuingYou can see the list of payment methods and their current status for the right configuration.
SelectPay by Bank›Enable
Do this: Confirm Cards is enabled. Find Pay by Bank, select Enable and complete any account requirements Stripe shows.
Check before continuingBoth Cards and Pay by Bank show Enabled. If Stripe says Pending or Unavailable, resolve its requirements or contact Stripe before offering that method.
SelectBank Transfers›Enable
Do this: Find Bank Transfers and select Enable. If Stripe shows its delayed-payment notice, read it and continue. Your website provider must confirm payment only after the funds arrive.
Check before continuingBank Transfers shows Enabled, and your website provider has confirmed support. A Payment Link alone cannot offer this method.
Search SettingsCustomer emailsPayout settings
Do this: Review successful-payment and refund receipt emails. Check the club’s business name, support contact and payout bank details. Keep the existing club payout bank if it is already correct.
Ready for the next stepThe club’s details are correct, the intended methods are enabled, and your receipt settings are ready. Now send the handover to your implementation team.
They appear only on eligible devices and browsers and with a supported integration. Your website provider should check any domain-registration requirements. There is no need for members to see developer settings.
Domain-registration guidance for your website provider ↗CONFIGURATION COMPLETE · HAND OVER TO US
Send the details below privately to your agreed implementation contact. For Dartford CC, this is the Bytecode Consulting / ClubOS team. We will use them to prepare the sponsorship website integration or the relevant ClubOS payment setup.
acct_…. This identifies the account; it is not an API key.A written status list is enough. If you send screenshots, crop them to the relevant settings and remove customer information, balances, bank details and credentials.
We will confirm whether your setup needs a Stripe team invitation or a ClubOS connection step.
If an invitation is needed, first confirm the exact developer email and permissions with us, then invite that person through Stripe’s team settings. Grant only the permissions needed for the agreed integration; keep the club as account owner.
Do not email or message passwords, login codes, secret or restricted API keys, or webhook signing secrets. If integration credentials are needed, we will arrange secure storage and access with you.
Stripe’s guidance on safe access and keys ↗
Once the handover and access are ready, we handle the agreed website or ClubOS integration, secure credentials, payment confirmations and technical testing. We will confirm when the club can review the finished journey and share it with members.
Fill in these non-secret details and send them through your usual agreed contact channel:
04 / CHOOSE YOUR WEBSITE ROUTE
The difference matters: a Payment Link can offer cards and Pay by Bank. Stripe Bank Transfer needs a supported integration such as Checkout with a Customer, or Invoicing. It is not supported on Payment Links. Stripe compatibility ↗
Suitable for a quick donation-page pilot.
An existing live link may only need a payment-method configuration change for Pay by Bank. Check the actual link before announcing it.
Suitable for donations and agreed sponsorship amounts.
card, pay_by_bank and customer_balance; configure GBP bank-transfer funding.Invoice payments are another route for agreed sponsorship. Check any Stripe Invoicing fees in addition to payment processing costs.
For your website provider: use the correct club’s live Stripe account, Customer and webhook endpoint. This configuration shape needs server-side integration; it is not an instruction for the club admin to paste into Dashboard.
mode: 'payment',
customer: customerId,
payment_method_types: ['pay_by_bank', 'customer_balance', 'card'],
payment_method_options: {
customer_balance: {
funding_type: 'bank_transfer',
bank_transfer: { type: 'gb_bank_transfer' }
}
},
line_items: [{
price_data: {
currency: 'gbp',
unit_amount: validatedAmountInPence,
product_data: { name: 'Club donation' }
},
quantity: 1
}],
success_url: yourConfirmationUrl,
cancel_url: yourReturnUrlValidate amounts on the server. For match fees and membership bills, load the amount from the club’s records. Store the club, payer and payment references securely, use idempotency, and keep API keys on the server. In a platform, scope Customer IDs and payment lookups to the correct club and Stripe account.
Do not assume the method array controls visual order: our hosted checkout showed Card first even though Pay by Bank was listed first. Put an amount-based recommendation on your website before checkout, or use Stripe’s supported ordering controls for your integration.
Do not mark a bank transfer paid from the return page or checkout.session.completed alone. Our transfer session was complete with payment_status: unpaid. Process checkout.session.async_payment_succeeded and verify the payment status before confirming funds. Handle failed/expired attempts, duplicated events and refunds.
This guide covers one-off collections, including an annual membership paid once. Automated recurring collections need a separate Billing/direct-debit design. Do not assume a one-off Pay by Bank checkout can automatically debit next month.
05 / CLUB ADMIN · CHECK THE PAYMENT JOURNEY
Your technical team handles simulated payments and failure scenarios separately. As club admin, review the live payment page and confirm the club is ready to receive genuine payments.
Follow the same website button a member will use. Check the club name, description, currency and amount. For a donation, check the amount entry works.
You should seeThe correct club and payment details, with no test-mode label.
Review Cards and Pay by Bank. If your provider added Bank Transfer, confirm that it is offered too. Check wallet availability on supported Apple Pay and Google Pay devices. You do not need to submit a payment to review the page.
You should seeThe methods your club intends to offer. If one is missing, ask your website provider to check the integration and Stripe configuration.
Ask them to confirm they have tested successful, failed and cancelled payments, card fallback, delayed bank transfers and refunds. These simulations are their technical work.
You should receiveConfirmation that payments update the right club record once, and that Bank Transfer stays “Awaiting payment” until funds are confirmed.
Nominate who will review the first genuine member payment or donation after launch. Check the amount, payment status, receipt, fees and payout reporting. Handle a refund through the club’s normal process if one is needed.
You should haveA named club contact who can reconcile payments and follow up on anything unexpected.
Live payments move real money and incur fees. Stripe requires simulated payment testing to use its test environment; do not make artificial live payments or use test card numbers on a live page. Stripe testing guidance ↗
06 / BEFORE YOU SHARE A PAYMENT PAGE
When these checks are complete, publish the payment button and share it with members. Your live Stripe settings are already active; “launch” means opening the finished journey to members. Ticks are saved only in this browser and can be cleared.
07 / COMMON QUESTIONS
Use the admin handover checklist and message template. Send the live account ID, payment-method status, existing link and club payment contact privately. We will confirm the access route and handle the agreed integration. Do not send passwords or secret keys.
Stripe provides bank details for the Customer, matches incoming funds to payments and keeps them in the same reporting system. Our test also handled an underpayment and left excess funds in the Customer cash balance. Direct transfers may avoid Stripe processing charges, but the club needs its own matching, confirmation and refund process.
No. Cards and Pay by Bank can work on a Payment Link. Bank Transfer needs a supported integration such as a server-created Checkout Session with a Customer. Simply enabling Bank Transfers in Dashboard is not enough.
No. The payment method does not determine tax treatment or Gift Aid eligibility. Keep genuine donations separate from sponsorship arrangements that provide benefits. A separate Gift Aid declaration still needs matching to the confirmed donation; enabling another payment method does not automate that.
HMRC sponsorship and VAT guidance ↗Stripe may need the payer’s bank details to return funds. A refund request can remain pending or require action, so track its final status. Stripe lists a 50p fee per successful GBP Bank Transfer refund; refunding a payment to the Customer’s Stripe cash balance is a different operation from returning money to their bank.
Stripe refund instructions ↗Check the account and payment-method configuration, currency, amount, integration support and the payment link’s allowed methods. Stripe normally limits Pay by Bank payments to £10,000, with increases subject to approval. Test the actual checkout rather than relying only on an Enabled label.
Stripe eligibility and limits ↗This guide explains how a club configures its live Stripe account. Availability in ClubOS depends on the payment flow and the club’s integration. Clubs using ClubOS should confirm their platform’s current support before changing settings or promising a new method to members.
Sandbox testing is technical work for the implementation team. Club admins follow the live setup steps above; they do not need to recreate our sandbox.
WHAT WE VERIFIED
28 September 2026 · synthetic transactions only
Not yet verified: a club’s live eligibility or negotiated pricing, real bank settlement/payouts, Apple Pay/Google Pay completion, receipt email delivery, Bank Transfer refunds, or a club website’s webhook processing. The tests validate Stripe’s sandbox behaviour, not a deployed ClubOS integration.
Use Stripe’s sandbox tools for failure, cancellation, refund and partial-funding scenarios. Keep test keys, test Customers and simulated funds separate from the live account. Stripe testing guide · Bank Transfer test helper