Få betalt
Take ticket money with a payment processing account
An agency taking on a new client links a payment processing account to the brand before a ticket can be paid for, and so does a promoter setting up a first brand. Every new event under that brand then uses it. The brand owner is the person who can link it.
Link the account that takes card payments for your brand, make it the one new events use, and know when it is ready to take money.
- För
- Setting up the account that takes card payments for a brand
- Tar
- 6 minuter
Innan du börjar
- You're the owner of the brand. An admin opens Payments and reads the accounts on it, and gets a message naming the brand owner when they try to change one.
- Your brand exists. Create the brand, link its payment processing account, then create events under it.
- You have what the payment company asks for: your business or personal identity, your bank details, and the name of the person responsible for the account.
-
Open Payments on your brand
Open your brand and select Payments. Connected payment methods lists every account linked to the brand, with the one new events use marked Default.
Obs: A brand with no account yet shows No payment methods connected instead of the table.
Brand, Payments, Connected payment methods. -
Start a new account and pick who takes the payments
Select Add Payment Method and choose a Payment method provider.
Obs: If your brand is in Indonesia or the Philippines, Xendit is the only choice offered. Managed Account appears where Ticket Fairy has enabled it for your brand.
Payments, Add Payment Method. -
Finish the setup with the payment company
Answer the identity, business and bank questions the payment company asks. A managed account asks them inside Ticket Fairy, and Stripe (classic) and Xendit ask them on their own sites.
Obs: Leaving part way through is safe. The account waits on the table with Continue setup on its row.
Managed accounts and standard accounts
Managed means the account is read and managed from your Ticket Fairy dashboard, so there is no second sign-in to keep. Standard means the account has its own sign-in with the payment company, and the row carries a Manage action that opens it.
-
Choose which account new events use
On the row of a second or later account, select Make default from the actions menu and confirm it. The first account on a brand becomes the default on its own, and its row carries no Make default.
Obs: Events you have already created keep the account they were created with. Change one of those on the event, under Payments.
-
Check the account is ready to take money
Read Status on the row. Active means the account can take payments and can be put on an event.
Varning: An account that is not yet Active cannot be made the default or put on an event. Finish its setup before your tickets go on sale.
Prova de här stegen på ditt eget evenemang
Skapa ett gratis konto, bygg ditt evenemang och följ stegen ovan i din egen instrumentpanel. Det tar några minuter och du behöver inte boka något säljsamtal.
Inga startavgifter. Ingen obligatorisk månadsavgift. Inget kreditkort krävs.
Eller låt det göras åt dig
Fai, the assistant inside your dashboard, lists the accounts linked to a brand, renames an account, makes one the default, archives one, and puts a first account on every event that has not sold yet, if you ask for that as she links it. She starts a Stripe (classic) account or a Xendit invite; a Managed Account is started here, on the Payments page. She asks you to approve every change first, and a new account still needs you to open the link and finish the setup with the payment company.
I din instrumentpanel, med Fai
List the payment processing accounts on <BRAND NAME>, say which one new events will use, and tell me whether any of them still needs its setup finished
Från din terminal
Installera CLI:t från vår CLI-sida, logga in med ticketfairy auth login och välj varumärket du arbetar med via ticketfairy brand use <BRAND_ID>. ticketfairy brand list och ticketfairy event list visar de ID:n som de andra kommandona använder.
The CLI reads the same list the Payments page reads. Linking an account is done in the dashboard, because the payment company needs a person at the keyboard.
List the payment processing accounts on a brand, with the account type, status and which one is the default.
ticketfairy api /api/organizations/<BRAND_ID>/brand-payment-methods --output json
Låt Fai göra det åt dig
Fai arbetar inuti din Ticket Fairy-instrumentpanel. Skapa ditt konto, öppna Fai och klistra in instruktionen ovan.
Inga startavgifter. Ingen obligatorisk månadsavgift. Inget kreditkort krävs.
Finish a setup you started earlier
Select Continue setup on the row and answer what is left. The row turns Active when the payment company is satisfied.
Obs: A Xendit account carries no Continue setup. The person you invited finishes it from their invitation email, and the row turns Active when they do.
Fai tells you which accounts on a brand are still unfinished. Finishing one is done here, on its row: a link she starts opens a new account rather than the one waiting on the table.
I din instrumentpanel, med Fai
Which payment processing accounts on <BRAND NAME> still need their setup finished?
Give an account a name your team recognises
Select Rename from the row's actions menu and enter the name. Buyers never see it, and it makes a brand with several accounts much easier to read.
Fai renames a payment processing account for you and pauses for your approval first. She reads the current names back so you can pick the one you meant.
I din instrumentpanel, med Fai
Rename the payment processing account ending <LAST DIGITS> on <BRAND NAME> to <NEW NAME>
Stop using an account you have finished with
Select Archive from the row's actions menu. The account stops being offered to new events, and events already using it are untouched.
Obs: The default account carries no Archive action. Make another account the default first, then archive the old one.
Varning: Ticket Fairy refuses the archive while a live event with ticket sales still uses the account, and names those events. Those events keep it until they have ended, because an event with a paid order cannot change account.
Fai archives an account for you and pauses for your approval first. She archives the default too, which the Payments page does not offer, so check which account you are naming before you approve.
I din instrumentpanel, med Fai
Archive the payment processing account named <ACCOUNT NAME> on <BRAND NAME>
Put a different account on one event
Open the event, select Payments and choose one of the brand's active accounts. Ticket Fairy refuses the change once the event has taken a paid order.
Fai reads which account an event uses and changes it, with your approval, while the event has no paid orders.
I din instrumentpanel, med Fai
Which payment processing account is <EVENT NAME> using, and what else could it use?
Frågor du kanske har
- Which of the choices should I pick?
- A managed account, where Ticket Fairy offers it. You set it up and read it in your Ticket Fairy dashboard, there is no second sign-in for your team to keep, and it carries Ticket Fairy's managed pricing. Pick Stripe (classic) when you already run a Stripe account you want the money to land in.
- Can a team member link the account instead of me?
- Only the brand owner. A team member with admin rights opens the Payments page and reads the accounts on it, and a change they try is answered with a message naming the brand owner. Ticket Fairy staff helping with a payout can also do it.
- What happens to the events I have already created?
- They keep the account they were created with. Making an account the default only decides what an event created afterwards starts with, so change an existing event on its own Payments page while it has no paid orders. Fai can put a first account on every event that has not sold yet at the moment she links it, and changes one event at a time after that.
- Is this the same as my payout details?
- No. The payment processing account is who takes the money from the buyer. Payout Details, under the brand's Details, is the bank account Ticket Fairy sends your money to after the event.
- Why is Xendit the only choice offered to me?
- Your brand's country is Indonesia or the Philippines, where Xendit takes the payments. The invitation goes to the email address of the person who owns the Xendit account, and they finish the setup.
- Can I have more than one account on a brand?
- Yes, on a Managed Account or on Stripe (classic). Link as many as you need, mark one as the default for new events, set a different one on an individual event before it takes a paid order, and give each a name your team recognises. A brand in Indonesia or the Philippines holds one Xendit account, and Ticket Fairy refuses a second.
- My account is linked but still not Active. What is missing?
- The payment company has not finished checking it. On a Stripe account, select Continue setup on the row to see what it is still asking for, which is usually an identity document, a bank account or a business detail. A Xendit account carries no Continue setup, and the person you invited finishes it from their invitation email.
- Where do I see what an account has paid out?
- On a Managed Account, select View on its row for payouts and balance, and Payments from its actions menu for the individual payments. Stripe (classic) opens its own payouts page from that same View, and a Xendit account uses Manage, which opens the Xendit dashboard the invited person signs in to.
Har du fortfarande en fråga?
Boka en demo så svarar vi på den i ett samtal, utifrån din typ av evenemang. Eller skapa ditt konto och se själv.
Inga startavgifter. Ingen obligatorisk månadsavgift. Inget kreditkort krävs.
Relaterade guider
Gör det på ditt eget evenemang
Skapa ditt konto, bygg evenemanget och följ stegen i din egen kontrollpanel. Du behöver inte boka ett säljsamtal.