Which payment methods should you offer for events in Spain?

A buyer lands on your sales page, picks two general admission tickets and one VIP, fills in their details and reaches the payment step. They can't see Bizum. They can't see Apple Pay. All they see is a credit card form with 16 fields. They hesitate. They close the tab. Gone. You have lost 95 euros because you didn't offer the way of paying they use every day.

This scenario repeats thousands of times a day in ticket sales in Spain. The payment method is not a technical detail: it is one of the decisions with the biggest impact on your conversion rate. In the Baymard Institute cart abandonment study, which averages an abandonment rate of 70.22% across 50 studies, 9% of people who abandon during checkout do so because there aren't enough payment methods. Not because the price was too high, nor because they didn't want to buy: they couldn't pay the way they wanted to.

This guide analyses each payment method relevant to ticket sales in Spain in 2026: when it makes sense to offer it, which type of event it suits best, what conversion rate it delivers and what the technical and cost implications are. The aim is for you to make an informed decision about which methods to offer at your checkout.

Credit and debit card: the standard that isn't enough on its own

Card is still the most widely used payment method in Spanish e-commerce. Visa and Mastercard are the dominant networks, and every payment gateway accepts them.

Advantages of cards for ticket sales

• Universality: practically everyone has a debit card linked to their bank account.
• Immediate processing: the transaction is confirmed in seconds, so the ticket can be issued instantly.
• Buyer protection: the chargeback system protects the buyer against fraud or cancellations, which builds trust.
• Support for recurring payments: useful for season tickets or subscriptions.

The problem with card alone

Offering only card as a payment method is like having a shop with a single entrance. It works, but it limits the flow. The specific problems:

• Friction on mobile: typing 16 digits, an expiry date and a CVV on a 6-inch screen causes errors and abandonment.
• 3D Secure: the strong authentication required in Europe by the Directive (EU) 2015/2366 (PSD2) adds an extra step that can redirect the buyer to their bank's app. If that app is slow to load or the buyer doesn't remember their password, the purchase is lost.
• Expired cards or insufficient funds: a share of transactions fails simply because the card saved in the browser has expired or doesn't have enough balance.

Conversion data

Not everyone who reaches the card payment step completes the purchase: buyers are lost to data entry errors, 3DS failures, declined cards or abandonment during the process. In Baymard's study, 10% of checkout abandonments are due to a declined card. Check in your gateway how many payments are started and how many are completed: that is your number.

Why does Bizum work so well for selling tickets?

Bizum is no longer an app for sending money to friends. According to Bizum's 2025 review, more than 30.6 million users made 1,237 million transactions that year, and e-commerce payments grew by 82.1%, to 105.6 million transactions. It has become a legitimate payment method for e-commerce. And in ticket sales it has enormous potential, especially for certain audience profiles.

Why Bizum works so well for tickets

• No bank details: the buyer pays with their phone number and confirms in their bank's app. They don't need to have their card to hand, remember the CVV or go through 3D Secure.
• Native mobile experience: the payment flow is to confirm in the bank's app and come back. On a mobile device, this is faster and more natural than filling in a card form.
• A habit among young people: it is the method many young people already use to pay each other, and that is exactly the segment that buys tickets for concerts, festivals and nightlife.
• Trust: the buyer doesn't share card details with a website they don't know. They simply confirm a payment in their banking app, which they already have installed and trust.

Where Bizum fits especially well

Limitations of Bizum

• Transaction limit: according to the Bizum FAQs, the general maximum is 1,000 EUR per transaction and 5,000 EUR sent per month, and each bank may set lower limits; for online purchases it refers you to each bank. For high-priced VIP tickets or large group purchases, it may not be enough.
• Only customers of Spanish banks: tourists and residents with foreign banking cannot use Bizum. If your event has a significant international audience, you need alternatives.
• Technical integration: not all ticketing platforms have Bizum built in. Some offer it through gateways such as Redsys, others don't support it at all.

Key conversion data

We have not found a public study that quantifies how much conversion rises when Bizum is added. The logic is clear, and you can measure it on your own checkout: the point is not that someone who was going to pay by card switches to Bizum, but that someone who would have abandoned because they didn't have their card to hand or didn't trust the form now completes the purchase.

Why enable Apple Pay and Google Pay?

Mobile wallets remove the biggest friction point in online payment: entering details manually. With Apple Pay or Google Pay, the buyer confirms the payment with Face ID, a fingerprint or the device PIN. The whole transaction takes less than 5 seconds.

Penetration in Spain

• Apple Pay: available to all iPhone users with a compatible card linked.
• Google Pay: available on Android devices. Active use for online payments is lower than for Apple Pay, but it is growing fast.

Real impact on conversion

The reason to enable them is simple: there is no form to fill in, there are no typing errors, there is no abandonment out of laziness. The conversion uplift figures in circulation are published by the payment providers themselves; compare your checkout before and after.

For ticket sales, where a large share of purchases happen on mobile, this conversion improvement can mean tens or hundreds of additional tickets sold without doing anything more than enabling these payment methods.

Technical considerations

• Cost: Apple Pay and Google Pay fees are usually included in the payment gateway's fee (Stripe, Adyen, Redsys). There is no additional surcharge for the merchant in most cases.
• Compatibility: they work in Safari (Apple Pay) and Chrome (Google Pay) on their respective devices. In other browsers or configurations, the button simply doesn't appear.
• Integration: most modern payment gateways (Stripe, Adyen, Checkout.com) support them natively. The technical implementation is usually trivial.

When does it make sense to offer PayPal for selling tickets?

PayPal is neither the fastest nor the cheapest method, but it serves a specific purpose: building trust with buyers who don't want to share card details with a website they don't know.

When it makes sense to offer PayPal

• Events with an international audience: PayPal works in more than 200 countries and accepts multiple currencies. If your event attracts tourists or foreign visitors, PayPal removes the "I don't have Bizum or a Spanish bank" barrier.
• First editions or unknown events: if the buyer doesn't know your brand, paying with PayPal gives them the reassurance that they can make a claim if something goes wrong. PayPal's buyer protection is well known and reassuring.
• High-priced tickets: for VIP tickets or premium packages above 100 EUR, a hesitant buyer has more incentive to use a method they know and trust.

The cost of PayPal

PayPal's standard rate in Spain for domestic commercial transactions is 2.90% + 0.35 EUR. That is more expensive than card through a gateway such as Stripe, which publishes 1.5% + 0.25 EUR for standard cards from the European Economic Area. It is worth it if the carts it recovers cover the difference: work it out with your own data.

The debate: PayPal redirects, and is that bad?

Yes, PayPal redirects the buyer to its own page to authenticate. This breaks the purchase flow and can cause abandonment. The redirect is not ideal, but for the segment that chooses PayPal, trust outweighs the friction.

SEPA and bank transfer: for the niche that needs it

Bank transfer is not a usual payment method for general consumer tickets. But it has its place in certain very specific scenarios.

When it makes sense

• B2B purchases: a company buying 50 tickets for its team may prefer to pay by transfer and receive an invoice. The process is slower, but it fits their administrative procedures.
• High-ticket events: professional conferences with tickets of 500 EUR or more, where the buyer wants a formal invoice before paying.
• Sports clubs' season tickets: one-off high-value payments that the buyer prefers to make from their online banking.

Clear limitations

• Not instant: a transfer can take anywhere from a few hours (SEPA Instant) to 1-2 working days. This means you cannot confirm the ticket immediately.
• Manual handling: someone has to check that the payment has arrived and assign the ticket. At scale, this doesn't work.
• Not suitable for urgent sales: if tickets sell out quickly, transfer doesn't work because the buyer cannot secure their place until the payment is processed.

For the vast majority of general consumer events, transfer should not be in the checkout. But if you sell B2B tickets or handle large amounts, having the option available on request can close sales you would otherwise lose.

Financing: Klarna, Sequra and pay-in-instalments

"Buy now, pay later" (BNPL) has reached ticket sales. And it makes sense for certain types of event, though not for all.

When financing works for tickets

• Festivals with a pass above 100 EUR: a 180 EUR pass split into 3 instalments of 60 EUR with no interest is easier to swallow for a university student than a single payment.
• VIP packages or premium experiences: tickets bundled with a hotel, transport or backstage access that exceed 200-300 EUR.
• Sporting events with season tickets: an annual season ticket of 400 EUR paid in 10 instalments of 40 EUR hugely widens the audience that can afford it.

The main providers in Spain

None of them publishes a single rate for merchants: it depends on the term, the volume and the agreement. Ask for the rate in writing before enabling it and compare it with your margin per ticket.

Impact on sales

The figures for average ticket value increases with BNPL that circulate are published by the financing providers themselves, so treat them with caution. Applied to events, the idea is that offering financing can lead a buyer who was only going to buy general admission to consider VIP if they can pay for it in instalments.

Risks to consider

• Cost for the organiser: the BNPL provider's fee is added to the ticketing platform's fee. Add the two fees together before deciding: your margin shrinks.
• Refunds: if the event is cancelled, refunds on BNPL are more complex to handle than on card.
• Regulation: the Bank of Spain is increasingly supervising BNPL services. It is important that the provider you use complies with current regulations.

Does it make sense to accept cryptocurrencies to sell tickets?

Does it make sense to accept Bitcoin or Ethereum to sell tickets? The short answer for the vast majority of events in Spain is: no, not as a main payment method.

The real numbers

Payment with cryptocurrencies in Spanish e-commerce is residual. Even at tech or crypto-focused events, adoption as a real payment method (rather than an ideological statement) is marginal.

When it might make sense

• Blockchain or Web3-themed events: if your target audience is cryptocurrency enthusiasts, not offering crypto as a payment would be contradictory. But even here, most people will buy by card.
• Events with a high share of international attendees: cryptocurrencies remove the friction of currency conversion and the need to have a local card.

How to implement it if you decide to

Use a processor such as BitPay, Coinbase Commerce or NOWPayments that automatically converts to euros at the time of the transaction. That way you take on no volatility risk. The buyer pays in Bitcoin, you receive euros.

But let's be clear: the implementation effort and the additional support it requires are rarely justified for general-audience events in Spain. Resources are better invested in integrating Bizum or Apple Pay, which have a measurable impact on conversion.

Stripe or Redsys: which payment gateway should you choose?

The buyer doesn't see the payment gateway, but you do. It is the infrastructure that processes the transactions and pays you. The two dominant options in Spain for ticket sales are Stripe and Redsys.

Stripe: the tech-first option

• Fee: 1.5% + 0.25 EUR per standard EEA card transaction, according to its pricing page. Bizum does not appear among its methods.
• Integration: excellent API, impeccable documentation, SDKs for every language. Ideal if you have a technical team or your ticketing platform uses Stripe by default.
• Payment methods: card, Apple Pay, Google Pay, PayPal (via Link), SEPA, Klarna. Broad international coverage.
• Settlement: after 7 days in standard mode, with an instant settlement option (at additional cost).
• Dashboard: a powerful control panel for managing transactions, disputes and payment analytics.

Redsys: the Spanish banking option

• Fee: you negotiate it with the acquiring bank you work with; there is no single public rate, and it may be lower than Stripe's.
• Integration: technically more complex than Stripe. The documentation has improved but is still less developer-friendly.
• Payment methods: card (Visa, Mastercard, Maestro) and Bizum. Strong local coverage, limited international coverage.
• Bizum: Redsys is the gateway that supports Bizum natively. If Bizum is a priority for your audience, Redsys is the way to go.
• Settlement: depends on the acquiring bank. Some settle in 1-2 working days, others take longer.

The practical decision

For ticketing platforms that already have a gateway integrated, your decision is partly made: you will use the gateway your platform supports. But if you can choose or influence, the ideal combination for the Spanish market is Stripe for the main coverage + Redsys for Bizum. Some organisers use both in parallel.

To understand how gateway fees add up with those of the ticketing platform, see our guide on how much it costs to sell tickets online.

Which methods should you offer, depending on your event type and audience?

Not all events need the same payment methods. Offering too many can confuse the buyer (the paradox of choice). Offering too few can make you lose sales. The key is to choose the right ones for your case.

Recommended setup by event type

Concert in a venue / Party / Clubbing (average ticket 15-40 EUR, audience aged 18-35):

• Card (essential)
• Bizum (highly recommended)
• Apple Pay / Google Pay (recommended)
• PayPal (optional)

Music festival (average ticket 50-150 EUR, varied audience):

• Card (essential)
• Bizum (highly recommended)
• Apple Pay / Google Pay (recommended)
• PayPal (recommended, especially if there is an international audience)
• Klarna/Sequra financing (recommended for passes >100 EUR)

Professional conference / Congress (average ticket 100-500 EUR, professional audience):

• Card (essential)
• Apple Pay / Google Pay (recommended)
• PayPal (recommended)
• Bank transfer (for corporate purchases)
• Financing (optional for tickets >200 EUR)

Sporting event (average ticket 20-80 EUR, broad audience):

• Card (essential)
• Bizum (highly recommended)
• Apple Pay / Google Pay (recommended)
• Financing (for season tickets)

Children's / Family event (average ticket 10-30 EUR, buyers aged 30-50):

• Card (essential)
• Bizum (recommended)
• Apple Pay / Google Pay (recommended)
• PayPal (recommended, parents use it a lot)

The general rule

For the Spanish market in 2026, the minimum viable combination is card + Bizum + Apple Pay/Google Pay. With them you cover most buyers in Spain. PayPal and financing are add-ons that improve conversion in specific segments.

Payment security: what the buyer doesn't see but matters

The security of payment processing is not a differentiator the buyer appreciates directly, but it is what protects you from fraud, chargebacks and financial losses.

Minimum security requirements

• PCI DSS compliance: any platform that processes card payments must comply with the PCI DSS standard. If you use Stripe, Redsys or any certified gateway, the gateway handles compliance. Never process card data directly on your own servers.
• 3D Secure 2 (3DS2): the usual way of meeting the strong authentication required by PSD2 on most card payments; the exemptions (low amounts, risk analysis) are set by Commission Delegated Regulation (EU) 2018/389. It adds an authentication step, but drastically reduces fraud. Modern gateways implement 3DS2 with smart exemptions that allow authentication to be skipped on low-risk transactions, improving conversion.
• Tokenisation: card data is never stored in plain text. It is replaced by a token that only the gateway can decrypt. This protects against data breaches.
• SSL/TLS: the whole sales page must run over HTTPS. It sounds obvious, but there are still ticketing pages with expired certificates or insecure configurations.

Chargebacks: the hidden cost

A chargeback happens when a buyer disputes a transaction with their bank. The bank withdraws the money from your account and charges you a fee for the dispute (the amount depends on the gateway; Stripe publishes it on its pricing page). If your chargeback rate rises too high, the card networks and the gateway can place you in a monitoring programme, raise your fees or block you outright.

How to minimise chargebacks in ticket sales:

• Clear payment descriptor: make sure the buyer's bank statement shows the name of your event or your brand, not a cryptic code. If the buyer doesn't recognise the charge, they dispute it.
• Immediate confirmation emails: a clear email with the purchase details, the ticket attached and contact details for support.
• Visible refund policy: before paying, the buyer must know the cancellation and refund policy. This reduces legitimate chargebacks and protects you in illegitimate disputes.
• Anti-fraud system: detection of suspicious transactions before processing them, following the recommendations of OWASP. Bulk purchases from the same IP, cards from high-risk countries, abnormal purchase speed.

How should you present payment methods at checkout?

Having the right payment methods is not enough. They have to be presented in a way that maximises conversion.

Checkout design best practices

• Show the payment methods before asking for details: if the buyer sees the Visa, Bizum, Apple Pay and PayPal icons when they reach checkout, they know they will be able to pay however they like. This reduces anxiety before they fill in personal details.
• Detect the device and prioritise: if the buyer is on an iPhone, show Apple Pay first. If they are on Android, show Google Pay first. If they are in Spain, show Bizum in a prominent place.
• A single payment step: ideally, method selection and confirmation happen on the same screen. Every redirect or extra step is one more place where you lose the buyer: in Baymard, 17% of checkout abandonments are due to a long or complicated process.
• Remember the payment method for returning buyers: if someone has already bought with Bizum, offer Bizum as the default option next time.
• Show the total with a breakdown: the buyer wants to see the ticket price, the handling fees (if any) and the total before confirming. Price surprises at the last step cause abandonment and distrust.

The impact of the number of methods on conversion

A Baymard Institute study (2025) shows that checkout conversion is maximised when between 3 and 5 payment methods are offered. Fewer than 3 shuts buyers out. More than 5 causes decision paralysis and visual confusion. The key is to offer the right ones for your audience, not every possible one.

Summary: the payment setup that maximises your sales

The payment method is not a technical decision that you delegate and forget. It is a business decision that directly affects how many tickets you sell. Every method that is missing is a group of buyers you lose.

For the Spanish market in 2026, the winning formula is clear:

1. 1Credit/debit card: the foundation, with 3DS2 and tokenisation.
2. 2Bizum: the method Spanish audiences, especially young ones, already use every day.
3. 3Apple Pay / Google Pay: remove friction on mobile, where most purchases happen.
4. 4PayPal: for international audiences and buyers who prioritise perceived security.
5. 5Financing (Klarna/Sequra): for events with expensive tickets; as a rule of thumb, from around 80-100 EUR.

Implement these five methods, measure the usage split and the conversion rate of each through your metrics dashboard, and adjust according to what your data tells you. Don't copy another organiser's setup: what works for a festival of 20,000 people may not work for a theatre season of 200. Your data, your audience, your decision.

And Futura Tickets, what do we recommend?

To sell tickets in Spain with all of these methods without integrating gateway after gateway, we recommend Futura Tickets, which is our platform. Futura Tickets accepts card, Bizum, PayPal, Apple Pay, Google Pay, Klarna, Bancontact, MobilePay, EPS and iDEAL, depending on the country. It is the combination in this article, already set up. Futura Tickets charges no monthly fee: 0 € a month, just a commission per ticket sold, and with Futura Tickets the attendee database is 100% the organiser's. The price per ticket depends on the plan; we'll walk you through it in a demo.

Sources

• Baymard Institute: cart abandonment rate and its causes
• Bizum: 2025 review
• Stripe: pricing in Spain
• PayPal: business fees in Spain
• Directive (EU) 2015/2366 on payment services (PSD2) (EUR-Lex)
• Commission Delegated Regulation (EU) 2018/389, regulatory technical standards on strong customer authentication (EUR-Lex)
• Bizum: transaction limits
• PCI Security Standards Council
• OWASP Web Security Testing Guide