Payment Options

This page describes the payment options available for race entries and how to configure them.

Contents

Payment methods overview

Each race can be configured to accept one or more of the following payment methods:

Not all methods may be available for every organisation, depending on your organisation plan and enabled features.

Method Description Requires setup?
Stripe Online payment via Stripe — supports card, bank transfer, Pay by Bank and Direct Debit Yes — Stripe account required
PayPal Online payment via PayPal Yes — PayPal merchant account required
SumUp Online payment or card reader via SumUp Yes — SumUp merchant account required
Invoice Entries submitted now; organiser must follow up to send invoice via Stripe or manually Stripe setup required only for Stripe invoicing
Pay later Entries submitted now; payment collected on the day of the race No additional setup required

You can enable multiple payment methods for a race; competitors will choose at checkout.

Online payments

Stripe

Stripe is the recommended option for collecting payments online. Competitors pay at the time of checkout and payment is processed immediately.

Setting up Stripe:

  1. A connected Stripe account must already be configured for the owner of the race:
    • by your organisation admin if the race was created directly within the organisation
    • by your subaccount admin if the race was created under a club or subaccount
  2. For organisation-owned races, see the Organisation Admins Guide.
  3. For subaccount-owned races, see the Club and Subaccount Admins Guide.
  4. Once Stripe is connected, go to your race settings.
  5. Enable Allow Stripe online payments.
  6. Set the entry fee(s) for each race class.

Payments are processed via Stripe’s secure payment infrastructure. Competitors will see a payment form at checkout where they can complete their payment.

Alternative online payment methods via Stripe

In addition to card payments, Stripe supports several other online payment methods that competitors can use at checkout. These include:

Method Description
Bank transfer Stripe provides a virtual account number; competitors pay by bank transfer and Stripe reconciles the payment automatically
Pay by Bank Competitors pay directly from their bank account via an open banking link — no card details required
Direct Debit Competitors authorise a Direct Debit; Stripe collects the payment automatically

To enable these methods for your races:

  1. Log in to your Stripe dashboard.
  2. Go to Settings > Payment methods.
  3. Enable the methods you want to offer (e.g. BACS Direct Debit, Pay by Bank).
  4. Save your changes.

The payment methods enabled in your Stripe account will then be available to competitors at checkout for any race that uses Stripe.

PayPal

PayPal allows competitors to pay using their PayPal account or a debit/credit card via PayPal’s checkout.

Setting up PayPal:

  1. A connected PayPal account must already be configured for the owner of the race:
    • by your organisation admin if the race was created directly within the organisation
    • by your subaccount admin if the race was created under a club or subaccount
  2. For organisation-owned races, see the Organisation Admins Guide.
  3. For subaccount-owned races, see the Club and Subaccount Admins Guide.
  4. Once connected, go to your race settings and enable Allow PayPal online payments.

SumUp

SumUp can be used in two ways:

  • Online payments — competitors pay by card online at checkout (similar to Stripe).
  • Card reader — a SumUp card reader is used to take payment in person, for example at race registration on the day.

Setting up SumUp:

  1. SumUp is only supported for races created under a club or subaccount.
  2. A club or subaccount admin must connect a SumUp merchant account to the platform.
  3. See the Club and Subaccount Admins Guide.
  4. Go to your race settings and enable Allow SumUp online payments.

Invoice payments

The Invoice payment option allows competitors to submit entries without paying at checkout. Invoices are not generated automatically. The race organiser must follow up to issue an invoice or record payment manually.

To enable invoice payments:

  1. Go to your race settings.
  2. Enable Allow payments by invoice.

When a competitor selects invoice at checkout, the order is submitted with payment still due. You then have two options:

  • Stripe invoice: Use the Create Invoice action from the orders page (requires Stripe to be configured).
  • Manual process: Send an offline invoice outside the platform and then use Add Manual Payment when payment is received.

Stripe invoicing has a major operational benefit: once the competitor pays, the order is updated automatically and payment records are created automatically.

Note: If you do not use Stripe invoicing, reconciliation remains manual. You will need to share your payment instructions (for example bank details) and then record the payment.

Pay on the day

The Pay later option allows competitors to submit entries without paying at checkout, with payment collected at the race venue on race day. This is sometimes called “on-the-day payment”.

To enable pay on the day:

  1. Go to your race settings.
  2. Enable Allow entries without payment.

When a competitor selects “Pay later” at checkout they are shown a message explaining that payment is due on the day.

Specifying race fees

Entry fees are set per competitor group. To set fees:

  1. Go to your race settings.
  2. Navigate to the pricing section.
  3. For each competitor group, enter the fee amount for each pricing tier.

Fees are specified in the currency configured for your organisation (for example, GBP, EUR).

Where multiple pricing tiers are defined for the race type, you must supply a fee for each tier.

Pricing tiers

Entry pricing is based on pricing tiers, which are defined as part of the race type by your organisation administrator. Each tier specifies a time window during which a particular price applies. Common tiers include early-bird, standard and late entry pricing, but the exact tiers available depend on your race type configuration.

When setting up pricing for a race class, you select which pricing tiers apply and set the fee for each. All selected tiers except the last must have an end date and time specified:

  • If an end date is left blank for a tier that is not the last, this will be flagged as an error.
  • The last pricing tier does not need an end date — it automatically ends at the race entries deadline. If you specify a different end date and time for the last tier, this will be flagged as an error if it conflicts with the entries deadline.

Tip: If you only want to charge a single fixed fee with no late pricing, select just one pricing tier and leave its end date blank.

Free events

If there is no entry fee, leave all fee fields set to zero and do not enable any payment methods. The payment step will be skipped during checkout and competitors will be taken directly to the confirmation screen.

This site uses Just the Docs, a documentation theme for Jekyll.