TiketCaribbean Merchant Agreement

In this Merchant Agreement, "Merchant" means the same person or entity as an "Organiser" under our Terms of Service, and the two terms are used interchangeably. Capitalised terms not defined in this Agreement have the meaning given to them in the Terms of Service.

This Merchant Agreement is incorporated into, and forms part of, the Terms of Service by reference. It should be read together with our Terms of Service, Refund and Cancellations Policy, and Trademark and Copyright Policy, each of which continues to apply in full to Merchants. Where this Agreement sets out a specific rule for merchant activity (for example, fees, payouts, or merchant-specific tax obligations) that rule governs. On every other subject, the Terms of Service, Refund and Cancellations Policy, and Trademark and Copyright Policy govern, and nothing in this Agreement narrows the rights TiketCaribbean holds, or the obligations a Merchant owes, under those documents.

This Merchant Agreement applies to any business or individual that lists events, sells tickets, or offers services through TiketCaribbean.

Listing free and external events is open to every Merchant. Selling paid tickets is opened business by business: a Merchant requests access from Create Event, and our team reviews each request. We can only approve a business whose payout bank account is in a country we can currently pay out to (see Payouts below). We may decline a request, and access can be suspended or withdrawn under the Termination section of this Agreement.

Before a paid event can be published, the Merchant must also complete payout onboarding with Stripe. Each paid event must show a refund rule before tickets go on sale, as required by the Refund and Cancellations Policy.

We check Merchants in stages. Each stage opens up more of the platform, and we may ask for more information at any stage. Some checks are ours and some are carried out by Stripe, as follows.

• Account: the email address on the account is verified, either with a one-time code we send to it or by Google or Apple when the Merchant signs in with them.
• Organiser onboarding: the Merchant verifies a phone number with a one-time code sent through Twilio Verify, and completes the business profile, including the business name, type, category, country, contact details and logo.
• Business review by our team: every new business is reviewed by our team before its events can be published or it can be paid out. Reviewers can see, among other things, whether the email address and phone number have been verified, whether the phone number is an internet (VoIP) number or is from a different country than the business, and whether the account name appears in the email address. These are prompts for a closer look; none of them decides the outcome on its own. We may approve or reject a business, and may contact the Merchant for more information before deciding.
• Business email (optional): a business email address can be verified with a one-time code we send to it, for the Business Verified badge described below.
• Paid ticketing: needs a separate request for each business, reviewed by our team, and a payout bank account in a country we can currently pay out to, as set out under Paid Ticketing Access and Payouts.
• Identity, business and bank checks by Stripe: before a paid event can be published, the Merchant completes payout onboarding on Stripe's hosted pages. Stripe carries out identity, business and bank account verification (know-your-customer and know-your-business checks) for the connected account under its own terms, and may ask the Merchant for documents, for details of the people who own or control the business, or for further checks at any time. We receive the status of that onboarding and an account identifier. We do not collect or store identity documents or bank details ourselves.
• First payout: the first payout for each business is reviewed by our team before it is released.

The Merchant must give us and Stripe accurate, complete and current information, and tell us promptly if anything material changes, such as the business name, who owns or runs it, its contact details or its payout bank account. If a check is not completed, fails, or relied on information that turns out to be inaccurate, we may decline or withdraw paid ticketing, decline to publish or remove events, hold payouts, or suspend the account under the Termination section. Stripe may also restrict or close a connected account under its own terms, independently of us; while a connected account cannot receive transfers, we cannot pay the Merchant out.

Passing these checks does not mean we vouch for a Merchant or its events. Badges confirm only the checks described under Verification and Trust Badges below.

• Free and external events: no fees for the Merchant, and no booking fee for attendees on free or RSVP events.
• Platform fee: on the Starter plan (the free plan), 2% of the ticket face value, deducted from ticket revenue at settlement. The fee that applies is shown in the organiser dashboard before a paid event is published, and the current rates are on the Ticketing Fees page. The Pro and Scale plans are not available yet. Enterprise terms are offered by agreement under an annual licence; contact us to discuss them. Founding Organisers pay a reduced platform fee for a limited period, as described on the Organiser Badges page and in the Founding Organiser terms in the organiser dashboard.
• Booking fee: buyers pay our booking fee of 6.5% of each ticket's price, with a minimum per ticket of 50p or a set equivalent in other currencies, shown as its own line before payment. It is our fee and is never deducted from what the Merchant receives, except as follows. If the Merchant cancels a paid event, or refunds or removes a ticket on its own initiative, the booking fee refunded to buyers under the Refund and Cancellations Policy is deducted from the Merchant's settlement, because the decision was the Merchant's. If we remove an event because the Merchant broke our rules, every buyer is refunded in full, booking fee included, and the whole amount is deducted. Where a refund is because of our error, we bear the booking fee.
• Costs we carry: Stripe card processing fees, currency conversion, Stripe payout and Connect fees, the processing fee Stripe keeps when a payment is refunded, and card-network dispute fees are paid by us and are not deducted from the Merchant's payout. On refunds and chargebacks the Merchant is not charged our platform fee on the money that went back.
• Changes: we will give Merchants notice by email before changing fees, as set out in the Changes to this Agreement section below.

Payouts are made through Stripe Connect, using an Express connected account for each Merchant business. We use separate charges and transfers: ticket money is received into TiketCaribbean's UK Stripe platform account, held for the Merchant, and transferred to the Merchant's connected account when the event is settled. Stripe then pays it to the Merchant's bank account.

During Stripe onboarding the Merchant accepts Stripe's Connected Account Agreement, and Stripe carries out its own identity and bank checks on its hosted pages. We receive the status of that onboarding and an account identifier.

• Where we can pay out: we can currently pay out to bank accounts in the United Kingdom, the United States, the 27 member states of the European Union, Iceland, Norway, Switzerland and Canada. This list depends on Stripe's cross-border payout rules and our own configuration, and may change.
• Caribbean bank accounts: payouts to bank accounts in the Caribbean are not available yet. A Merchant whose only bank account is outside the countries above can run free and external events, but cannot sell paid tickets yet. We may add another payout provider, such as Payoneer, for Caribbean bank accounts later.
• When: each event is settled after it ends. Unless early settlement has been agreed under the Early Settlement section below, a settlement is released no earlier than 72 hours after the event ends. The first payout for each business is reviewed by our team before it is released; later payouts are released automatically within internal limits.
• Holds: we may hold a payout while there are open disputes or refund requests, or while we carry out a fraud or compliance review, as set out in sections 11, 14 and 15 of the Refund and Cancellations Policy.
• Arrival: once a payout is released, Stripe pays it to the Merchant's bank on Stripe's own schedule. We do not guarantee a payout date or the date money arrives in the Merchant's bank.

We may agree in writing to release part of a settlement before an event takes place. Unless that written agreement says otherwise:

• we decide how much is released and may keep the rest until the event ends and the usual settlement period has passed;
• the Merchant must hold event cancellation insurance naming CaribraConnect Technology Ltd as loss payee for the amount released, and show us proof of it on request;
• we may ask for a guarantee from a parent company or from the business's owners before releasing anything;
• if the event is cancelled, postponed or not delivered as described, every amount released becomes a balance the Merchant owes us immediately, which we may recover as described under Refunds and Disputes After a Payout and from any other money we hold for the Merchant; and
• we never release more than the ticket sales the event itself has taken, less refunds and chargebacks already made.

Early settlement is at our discretion. Agreeing it for one event does not oblige us to agree it for another.

If a refund or chargeback happens after an event has been paid out, the amount becomes a balance the Merchant owes us, and we recover it from that business's next payout or payouts. If the balance is still outstanding after 30 days, we may reverse the original Stripe transfer for that event. We may write a balance off at our discretion. We do not keep a rolling reserve against future refunds.

When a buyer's bank reverses a payment (a chargeback), the amount of the chargeback is recovered from the Merchant in the same way; the card network's dispute fee is paid by us.

We use the following measures to reduce fraud against buyers, Merchants and us. They lower the risk; they do not remove it, and we do not guarantee that every fraudulent order or account will be caught.

• At checkout: the website checkout runs a Cloudflare Turnstile bot check; reserving and buying tickets is rate-limited per account and per IP address; each account may hold only a limited number of tickets for an event (or fewer, if the Merchant sets a lower cap), counting issued tickets, open orders and tickets on hold; and tickets are held for a short time while the buyer pays, then released if the payment is not completed.
• Card payments: buyers enter card details on Stripe's hosted pages, and Stripe screens payments with its own fraud tools (Stripe Radar), which may block a payment or flag it for review.
• Tickets and entry: ticket QR codes are signed so that altered codes are refused, scans are recorded so that a ticket already used can be refused, and tickets on an order under a chargeback are flagged.
• Merchants: the verification and review steps set out under Verification of Organisers and Businesses, a manual review of each business's first payout, and internal limits on payouts released automatically.
• Chargebacks: when a chargeback is opened, the unpaid settlement for that event is held until the dispute is resolved.

If we reasonably suspect fraud, money laundering, misuse of the platform, or a breach of this Agreement or the law, by a Merchant, a buyer or anyone else, we may do any of the following, in addition to our other rights:

• refuse or withdraw paid ticketing, decline to publish an event, or remove an event;
• suspend or close the account, under the Termination section;
• hold a payout, as described under Payouts and in sections 11, 14 and 15 of the Refund and Cancellations Policy;
• cancel and refund orders, including where a No refund rule applies, as section 15 of that Policy allows, with the amounts refunded treated as set out under Fees and Refunds and Disputes After a Payout;
• recover amounts owed after a payout, as described under Refunds and Disputes After a Payout; and
• share information with Stripe, and report matters to the police or other authorities where the law requires or allows us to.

The Merchant must not buy, or arrange for others to buy, its own tickets in order to inflate sales or move money, and must not use payment details it is not authorised to use. The Merchant must tell us promptly about any fraud it suspects on its events, and give us the information we reasonably ask for to investigate a suspected fraud or to answer a chargeback, such as proof of entry or of contact with the buyer.

Merchants must comply with local laws, provide accurate event information, and ensure tickets sold are valid and delivered as described.

What the Merchant receives. Through the attendee list, exports and the scanner, the Merchant sees, for each person registered for or holding a ticket to its event: their name, the ticket type, the amount paid for the ticket, the order reference and purchase date, and whether the ticket has been checked in or refunded. The Merchant also receives the person's email address and phone number where that person has "Share contact details with organisers" switched on in their Settings. The Merchant never receives card details.

Responsibility. Each of us is responsible under data protection law for our own use of that data. We are responsible for how the platform collects and handles it, as described in our Privacy Policy. The Merchant is responsible for what it does with the data it views, exports or downloads, and for meeting the data protection law that applies to it, including the UK GDPR and Data Protection Act 2018 where they apply and any registration with a data protection authority.

How the Merchant may use it. The Merchant must:

• use the data only to run the event the person registered for or bought a ticket to (for example admission, telling attendees about changes or cancellations, customer service, and safety at the event) and to meet its own legal obligations;
• send marketing to a person only where the law allows it and in line with that person's choices, and stop when they opt out;
• not sell, rent or trade the data, not give it to anyone else except service providers acting on the Merchant's behalf under suitable contracts or where the law requires, and not use it to harass anyone or for any unlawful purpose;
• keep the data secure, limit access to the team members who need it, and use scan team access rather than sharing account sign-in details;
• keep the data only for as long as it needs it for the purposes above or as the law requires, and then delete it securely, including when its account closes;
• tell us promptly if it receives a request or complaint from a person about data that came from TiketCaribbean and that we need to act on, and give us reasonable help with requests and complaints about that data; and
• tell us without undue delay, at security@tiketcaribbean.com, if data it obtained through TiketCaribbean is lost, stolen or accessed without authorisation, and cooperate with us in dealing with it. The Merchant remains responsible for any notice it must give to a regulator or to the people affected.

We may restrict a Merchant's access to attendee data, or suspend the account under the Termination section, if we reasonably believe the data is being misused. People can turn contact sharing off in their Settings at any time; after that, their email address and phone number are no longer shown to the Merchant, but the Merchant remains responsible for any copy it already holds.

Regardless of where a Merchant is incorporated, resident, or primarily operating from, the Merchant is solely responsible for:

• Registering their business with the relevant company registry, tax authority, or licensing body applicable to their event or trade, where required by local law;
• Accounting for and remitting any applicable income tax, corporation tax, value-added tax (VAT), or equivalent sales or goods-and-services tax on ticket sales and event income, including, for Merchants operating in the Republic of Trinidad and Tobago, any VAT administered by the Board of Inland Revenue and any obligations arising under the Trinidad and Tobago Companies Act;
• Obtaining any permits, licences, or approvals required to host or promote their Event in the applicable jurisdiction (for example, entertainment, liquor, or public assembly licences);
• Complying with applicable anti-money laundering and know-your-customer requirements to the extent these apply to the Merchant's own business activity. TiketCaribbean itself does not collect identity documents; identity and bank verification for payouts is completed directly with Stripe on its hosted pages; and
• Complying with applicable data protection law where the Merchant independently collects personal data from Attendees (for example, through custom registration forms or their own mailing lists), as described in section 9 of our Privacy Policy, including registration with a national data protection authority where required (for example, the Office of the Information Commissioner in Jamaica or the Data Protection Commissioner in Barbados).

TiketCaribbean does not withhold or remit tax on behalf of Merchants in any jurisdiction, and does not provide tax, legal, or accounting advice. Merchants should obtain independent professional advice on their specific obligations.

CaribraConnect Technology Ltd is registered in Scotland. Merchants and Organisers who are incorporated in, or primarily operate from, the United Kingdom must additionally comply with the following:

• Companies Act 2006: UK-incorporated merchants must maintain accurate company records and statutory filings as required by Companies House.
• UK tax obligations: Merchants are solely responsible for accounting for any UK income tax, VAT, or corporation tax arising from ticket sales and event income. TiketCaribbean does not withhold or remit UK tax on behalf of merchants.
• Anti-money laundering (AML): Merchants must comply with the UK Money Laundering, Terrorist Financing and Transfer of Funds (Information on the Payer) Regulations 2017 where applicable to their business activity.
• Consumer rights: Merchants selling tickets to UK consumers must comply with the Consumer Rights Act 2015 and the Consumer Contracts (Information, Cancellation and Additional Charges) Regulations 2013.
• Data protection: Merchants who independently process personal data of UK attendees must comply with the UK GDPR and Data Protection Act 2018 and maintain their own ICO registration where required.

CaribraConnect Technology Ltd Trinidad and Tobago Registration Number: C2025101100002. UK Companies House Number (Scotland): SC889839. UK Registered Office: 48 West George Street, Glasgow G2 1BP, United Kingdom.

TiketCaribbean may display a "Verified", "Business Verified" or "Identity Verified" badge against a Merchant's profile once the Merchant has completed the corresponding checks described in our Organiser Badges page (verified email and phone number; a verified business email address; and, for Identity Verified, completion of the identity checks run by our payout provider). These badges confirm completion of those specific checks only. They do not certify a Merchant's tax status, licensing, insurance, financial standing, or ability to deliver an Event, and do not reduce or replace any obligation a Merchant owes under this Agreement, the Terms of Service, or the Refund and Cancellations Policy. TiketCaribbean may suspend, withdraw, or decline to grant a badge at any time, including where information supporting a prior verification is found to be inaccurate or out of date.

A Merchant retains ownership of the event listings, artwork, descriptions, and other content it uploads, subject to the licence it grants to TiketCaribbean to host, display, and promote that content as set out in our Trademark and Copyright Policy. Merchants are solely responsible for ensuring their content does not infringe any third party's intellectual property rights, and remain subject to the notice-and-takedown, counter-notification, and repeat-infringer provisions of that Policy.

We may change this Agreement, our fees or the policies it incorporates. Before a change takes effect we will tell Merchants by email, explaining what is changing, at least 15 days in advance. Where a change means Merchants need to make significant technical or business adjustments, for example to their pricing or payout set-up, we will give longer notice that is reasonable and proportionate to those adjustments.

A Merchant who does not agree with a change may end this Agreement, and close their organiser account, at any time before the change takes effect, without penalty. Obligations that arose before then, including refunds, chargebacks and payout holds for events already sold, still apply.

We may make a change with shorter notice, or none, only where we must do so to comply with the law or a regulator, or to deal with an unforeseen and imminent risk such as fraud, malware, spam, a data breach or another security risk. We will still tell Merchants about the change as soon as we reasonably can.

TiketCaribbean may suspend or terminate merchant access for breaches of this agreement, fraud, or legal non-compliance. Payouts may be withheld to cover outstanding obligations, chargebacks, or approved refund claims, in accordance with sections 7, 11, 14 and 15 of the Refund and Cancellations Policy and the Refunds and Disputes After a Payout section of this Agreement.

Except where suspension is required on an urgent basis (for example, suspected fraud, a live safety risk, or a legal or regulatory requirement), TiketCaribbean will endeavour to give the Merchant reasonable notice of, and the stated reason for, a suspension or termination. A Merchant who disputes an enforcement decision may request review by contacting support@tiketcaribbean.com. Termination does not extinguish any obligation, liability, or payout hold that arose before the termination date.

This Merchant Agreement is governed by the same governing law, jurisdiction, and dispute resolution process as the Terms of Service (section 20), namely the laws of the Republic of Trinidad and Tobago, subject to the mandatory protections available to consumers described in that section. This Agreement does not create any partnership, joint venture, agency, or employment relationship between TiketCaribbean and any Merchant.