Your event

Payments

Every way this one event takes money: card, bank transfer, PayPal, and the currencies buyers pay in.

Your eventSettings

What you can do here

Everything on this page applies to this one event. You connect Stripe and PayPal once for the whole account, and these settings control what this event does with them.

go.tito.io/acme/summer-fetes-summer-fete/admin/settings/payment

Card payments

Card payments go to appears when your account has more than one Stripe account connected. It picks which one this event's new card payments go into. Orders already paid stay with the account they were paid into, and their refunds go back through it. An event with no account picked takes no card payments until you choose one. See Take payments into more than one Stripe account.

Where buyers pay is the card payment page, and it offers two:

  • On Stripe’s page sends them to Stripe.
  • On your pages keeps them on your own site, in a Tito form around Stripe's own card fields. That is what lets it show a buyer prices in their own currency where Stripe offers that.

Where the form on your pages can't run, the buyer gets Stripe's page instead.

How long a payment link works for is how long a payment link you send holds its tickets. After that the order is canceled and the places go back on sale.

In a widget, a buyer paying on your pages stays in the widget. A buyer sent to Stripe's page, to PayPal, or to a payment method with its own page, such as Klarna, comes back to your page with the widget open.

Prices in a buyer's own currency are Stripe's Adaptive Pricing. Stripe works out the currency, converts at a rate held for 24 hours, and adds a conversion fee of 2 to 4 per cent to what the buyer pays. You are paid the same either way, and a buyer who chooses your currency pays no fee. Whether it appears at all is a setting in your Stripe dashboard.

Create Stripe customers for paid orders makes every buyer who pays appear as a customer in your Stripe dashboard, with all their payments recorded in one place. It's on to start with, and leaving it on is what lets a returning buyer's card details prefill at checkout. Off, payments show up in Stripe as one-off guest payments.

Apple Pay, Google Pay, Link and PayPal appear as one-tap buttons at the top of the card form, with the corners you chose for every button in Button shape. They appear above the step that asks a buyer's name and email too. On that step a button opens only once every question you require is answered, and the answers are saved with the order.

Offer express checkout for this event turns that row of one-tap buttons on or off for every page of the event, including its widgets and landing pages. Off, the whole row goes, including Amazon Pay or Klarna if Stripe shows them there. Ways to pay inside the card form, like card and Klarna, stay. When a buyer pays on Stripe's page, Stripe still shows them Apple Pay and Google Pay. If PayPal is the only way your account takes payment, buyers still see it. An audience can also turn express checkout off for the buyers on its own page, but it can't turn it on while the event has it off. See Give a group their own booking page.

The buttons only show on web addresses Stripe has been told about, each address separately, including every subdomain. We register your account’s addresses for you, and every website you approve for your widgets. With express checkout on, Wallets on your pages lists each one with the wallets that are live on it. A wallet listed as not showing gives Stripe's own reason. Quote that reason if you contact Tito support about it.

Bank transfer

Allow payment by bank transfer lets a buyer choose to pay by transfer instead of card, and the order stays pending until you mark it paid. On your pages it's offered under the card form. On Stripe's page the buyer chooses between card and bank transfer before either opens. Days to pay after they book sets how long they have. Under it you choose whether an order that still isn't paid is canceled automatically, and under Reminders the days they're reminded before the due date and chased after it.

It needs an account to wire to, from your account's Invoicing page or from Stripe, and the panel tells you when there's neither. See Bank transfers and invoices for the whole flow.

Bank transfer is enough on its own. An account with Account holder and IBAN filled in can sell paid tickets with no payment service connected. Where both that and Stripe are set up, Where transfers go on the Invoicing page chooses which one buyers are sent to.

PayPal

Allow payment by PayPal puts PayPal alongside card at checkout. It needs PayPal connected on the account first. It shows only in the currencies PayPal supports. On your pages it is a button at the top of the card form, beside Apple Pay and Google Pay. On Stripe's page the buyer chooses between card and PayPal before either opens.

Anything a buyer pays for after their order is already paid, such as upgrading a ticket or adding to their order, is charged on its own, and they choose how to pay it the same way. Bank transfer covers these too, and the change gets its own invoice with its own number and due date. A change to an order whose own money hasn't arrived yet still needs Stripe or PayPal. Money sent back later goes back the way it came in, so an add-on bought with PayPal on an order paid by card is refunded through PayPal.

Currencies

Every price on the event is in the currency you chose when you created it, and that choice stays. Currencies lets the event hold prices in more currencies as well.

Selling in shows the ones you sell in now, your own currency among them and marked as the event's. Add a currency lists the rest by code and name.

Tick one to add it, then set the price in it on each ticket type, extra and fixed-amount discount. The price field on those screens becomes a row with a column per currency. Untick a currency to stop selling in it.

Leave a column blank and the ticket or extra is not offered in that currency. Your Ticket types list says which currencies each row sells in. A donation takes any amount, so it is offered in every currency you tick, with its own suggested and minimum amounts per currency. A ticket with a ladder of prices takes the boxes on each tier instead, and on its bridge price if it keeps selling between tiers.

An add-on you offer with a ticket type at its own price is sold at its price in each currency, wherever you’ve given it one. If you give it a different price on that ticket type, that price is in your event’s own currency only, so a buyer paying in another currency isn’t offered the add-on with that ticket. An add-on that’s free with a ticket is free in every currency the add-on is sold in.

A currency nothing is priced in yet is named in a warning above the list, because no buyer can pay in it until something has a price. Once part of the event is priced in it, a line under the list says how many ticket types and extras that is.

How a buyer gets a currency sets which of them someone arrives in:

  • They pick it on the event page shows a small switcher beside the language one.
  • Tito picks it from the country set in their browser goes by the country in the browser's language settings, not where the buyer is. A browser set to United States gets US dollars wherever the buyer is, and one set to Sweden gets Swedish krona, if you priced it. Only the first country the browser lists counts. If it has no country set, or you haven't priced the first one, the buyer gets your event's own currency.
  • The link they followed picks it shows nothing, and only a link you share chooses.

Any link with ?currency= in it chooses the currency whatever the setting says. Whatever a buyer ends up in, they see only what has a price in that currency, and the order is in that currency from checkout to refund.

On an event selling in more than one currency, the money figures on your event overview and your Sales report appear in one box: a converted total in your event's own currency, with what you actually took in each currency beside it. See Currency conversion for where that rate comes from and what reaches your bank.

Good to know

  • Whether this account is taking real money depends on which Stripe account it's connected to. A test connection shows a Test mode badge in the account bar, and there's no per-event switch. To test without touching live sales, turn on Test mode in the account switcher. Paying in there is simulated until an owner or admin connects a Stripe sandbox of their own, which is also what puts the one-tap wallets in front of you. See Try things out in test mode.
  • Account type on the Stripe card in Connections says which kind of Stripe account is connected: a live one, which takes real payments, or a Stripe sandbox, which takes test payments only.
  • A refund issued directly in the Stripe dashboard reaches this admin only when it's a full refund. For anything partial, use Refund or cancel… on the order. It asks what to refund before it asks anything else, so you can pick the whole order or one line on it.
  • A buyer can't cancel a whole PayPal order from their own order page, so those buyers come to you for the rest.

Still stuck?

You can let someone at Tito sign in to your account for a set time, and see every visit they made.

Let Tito support in →