Payment Terms & Stripe Connect

BLOCO's payment terms, payout models, and the Stripe Connect addendum.

1. Overview of Payment Models

BLOCO offers two payment models for Organisers:

• BLOCO-Managed Payments:ticket sale proceeds are collected by BLOCO and paid out to the Organiser after the event, net of BLOCO's Booking Fee.
• Stripe Connect (Organiser-Managed Payments):ticket sale proceeds are paid directly into the Organiser's own Stripe account. BLOCO's Booking Fee is automatically deducted at the point of each transaction before funds reach the Organiser.

Both models use Stripe as the underlying payment infrastructure.

2. BLOCO's Booking Fee

2.1 The Booking Fee is a fixed per-transaction fee set by BLOCO. The current Booking Fee is displayed in the Organiser dashboard and at the point of event setup.

2.2 Any deviation from the standard Booking Fee must be agreed in writing by BLOCO as a formal partnership arrangement. Verbal or informal agreements do not bind BLOCO.

2.3 The Organiser may choose to absorb the Booking Fee or pass it on to the Customer. In either case, BLOCO deducts its full Booking Fee from every transaction.

3. BLOCO-Managed Payments

3.1 Where BLOCO manages payment processing, all ticket sale revenue is collected by BLOCO via Stripe on behalf of the Organiser.

3.2 Payouts to the Organiser will be made available within 5 working days following the conclusion of the event. Payouts are made net of: BLOCO's Booking Fee; any approved Customer refunds processed during the sale period; any chargeback amounts withheld or recovered; and any other amounts owed by the Organiser to BLOCO.

3.3 BLOCO reserves the right to delay or withhold a Payout where:

• there is a reasonable suspicion of fraud or unlawful activity;
• a significant volume of chargebacks or refund requests has been received;
• the Organiser has not completed required KYC verification;
• there is an outstanding balance owed by the Organiser to BLOCO.

3.4 BLOCO reserves the right to set and retain a reserve amount from any Payout to cover the assessed risk of chargebacks, fraud, or financial exposure. BLOCO's determination of the reserve amount is final.

4. Stripe Connect - Organiser-Managed Payments

4.1 To use Stripe Connect, the Organiser must:

• have an active Stripe account in good standing;
• have completed Stripe's own onboarding and identity verification requirements;
• have been approved to use Stripe Connect by BLOCO.

4.2 When a Customer purchases a ticket using Stripe Connect: the full ticket price is charged to the Customer's payment method; BLOCO's Booking Fee is automatically deducted at the point of payment; and the net proceeds are transferred directly to the Organiser's connected Stripe account.

4.3 Where Stripe Connect is used, the Organiser is the merchant of record. The Organiser's name will appear on Customers' bank statements, and all financial, regulatory, and legal obligations in connection with the receipt of customer funds fall solely on the Organiser.

4.4 The Organiser accepts sole and full responsibility for:

• processing all Customer refunds through the BLOCO platform;
• ensuring sufficient funds are available to cover any approved refunds, chargebacks, and Stripe fees;
• responding to all Customer payment queries and complaints;
• all chargebacks and payment disputes;
• compliance with Stripe's terms of service and connected account requirements;
• compliance with all applicable financial services, consumer protection, and payment regulations.

5. Chargebacks and Disputes

5.2 The Organiser is solely and entirely responsible for all chargebacks arising from their events, regardless of which payment model is in use.

5.3 BLOCO-Managed Payments - Chargeback recovery:

• BLOCO will notify the Organiser of any chargeback received;
• BLOCO will deduct the full chargeback amount plus Stripe's dispute fee from the Organiser's Payout, current balance, future earnings, or reserve;
• If no funds are held, BLOCO will invoice the Organiser for the full amount, payable within 14 days;
• Failure to pay an invoice within 14 days may result in account suspension.

5.5 Dispute fees charged by Stripe are non-refundable even where the chargeback is successfully contested. These fees are passed through to the Organiser in full regardless of outcome.

6. Fraud Prevention

6.1 The Organiser is responsible for the integrity of their own sales channels, marketing materials, and ticketing operations.

6.2 The Organiser must notify BLOCO immediately if they become aware of any suspicious transactions, fraudulent activity, or unauthorised use of their account.

6.3 BLOCO reserves the right to suspend ticket sales for an event and withhold Payouts where fraud is suspected, pending investigation.

7. Taxes

7.1 The Organiser is responsible for accounting for and remitting all applicable taxes on ticket sales, including VAT, sales tax, or other local levies, in all jurisdictions in which they operate.

7.2 BLOCO's Booking Fee is exclusive of VAT. Where VAT applies to BLOCO's fee, it will be shown separately on any invoice.

7.3 BLOCO does not provide tax advice. The Organiser should seek independent advice regarding their tax obligations.

8. Currency and International Payments

8.1 The Platform operates primarily in GBP. Currency conversion for international transactions is handled by Stripe at the prevailing exchange rate. BLOCO is not responsible for exchange rate fluctuations or conversion fees.

8.2 Where BLOCO expands into international markets, country-specific payment terms may be issued as supplementary addenda to this document.

9. Governing Law

These Payment Terms are governed by the laws of England and Wales, and form part of the BLOCO Organiser Terms of Service.

10. Contact

For payment queries, Payout issues, or Stripe Connect enquiries: support@bloco.co.uk
Bloco Ltd | Company No. 12279811 | 3 Mary Street, Birmingham, B3 1UD