Online payments for federations: Stripe, bank transfer or physical POS

Collecting license fees seems like it should be simple. A member owes a fixed amount, they pay it, and the federation records the payment. In practice, the collection method you choose affects everything downstream: how much staff time goes into reconciliation, how quickly you know who has paid, how many members complete the process without friction, and how much money you actually keep after fees.

Most federations use one of three methods, or some combination: an online payment gateway (Stripe, Redsys, or similar), traditional bank transfers, or physical POS terminals at events and offices. Each has real strengths and real costs that go beyond the fee percentage printed on the contract.

This article compares all three with actual numbers, explains when each method wins, and proposes a hybrid approach that gives federations the best of each world.

The three options at a glance

• Online payment gateway (Stripe, Redsys, etc.): The member clicks a payment link and pays by card. Funds arrive in 2-7 business days minus a percentage fee. Reconciliation is automatic.
• Bank transfer: The member initiates a transfer. No percentage fee, but the federation must match each incoming transfer to a member manually. References are often garbled or missing.
• Physical POS terminal: Card payment at the federation office or an event. Low per-transaction fee, but requires staff presence and manual reconciliation.

Real cost comparison: a 3,000-license federation

Let’s model the true cost for a federation with 3,000 licenses at an average fee of 45 euros (135,000 euros total volume). Staff cost is loaded at 20 euros per hour.

Cost component	Gateway (Stripe)	Bank transfer	Physical POS
Direct transaction fees	2,775 EUR	0 EUR	1,245 EUR
Terminal rental	—	—	300 EUR
Staff reconciliation hours	~0 h (auto)	~200 h	~120 h
Staff reconciliation cost	0 EUR	4,000 EUR	2,400 EUR
Total annual cost	~2,775 EUR	~4,000 EUR	~3,945 EUR
Auto-reconciliation	Yes	No	Partial

The gateway is the cheapest total option despite having the highest direct fees, because it eliminates reconciliation labor. The transfer’s zero-fee headline is misleading: 200 hours of manual matching — opening bank statements, chasing garbled references, identifying mystery payments — costs more than the gateway’s percentage.

When each method wins

No single method is best in every situation. Context determines the right choice.

Gateway wins when: volume exceeds 500 annual transactions (reconciliation savings dominate); membership is geographically distributed; you run renewal campaigns with embedded payment links.

Transfer wins when: individual amounts exceed 500 euros (the percentage fee becomes significant); members are older demographics who prefer familiar bank processes; regulatory requirements mandate specific bank account traceability.

POS wins when: you collect at events, competitions, or assemblies where members are physically present; your federation has fewer than 200 members and a staffed office; the community operates heavily in cash alongside card.

Redsys vs. Stripe: a closer look

For federations operating in Spain and the EU, the two most common gateway options are Redsys (the Spanish banking consortium’s platform) and Stripe. Here is how they compare on the dimensions that matter for federations.

Criterion	Redsys	Stripe
Setup	Requires agreement with your bank; can take 2-4 weeks	Self-service signup; active in 1-2 days
Transaction fee	Negotiated with bank (typically 0.5-1.2%)	1.5% + 0.25 EUR (standard EU cards)
International cards	Higher fees, sometimes declined	Handles 135+ currencies natively
API quality	Functional but dated; documentation in Spanish	Modern REST API; extensive documentation
Recurring payments	Limited support	Built-in subscription and recurring billing
Refunds	Processed through bank; can take days	Instant from dashboard; reflected in 5-10 days
Dashboard	Basic; varies by bank	Comprehensive analytics, real-time
PSD2/SCA compliance	Mandatory 3D Secure	3D Secure with smart exemptions (Radar)
Payout schedule	Varies by bank (T+1 to T+3)	T+7 standard (T+2 available)
Integration effort	Moderate; bank-specific variations	Low; well-documented SDKs

Bottom line: Redsys offers lower transaction fees if your bank negotiates well, and it has strong brand trust among Spanish users who recognize the payment page. Stripe offers a superior developer experience, faster setup, and better tooling for automation. For federations that prioritize low fees and operate exclusively in Spain, Redsys is attractive. For federations that want faster integration, international support, or advanced features like smart retry and subscription billing, Stripe is the stronger choice.

The smart hybrid: best of all worlds

Rather than choosing a single method, the most effective federations design a hybrid collection strategy that uses each method where it performs best.

Default: online gateway

Make online card payment the default and primary method. Every renewal email, every registration form, and every invoice includes a payment link that takes the member directly to a card payment page. This handles 65-80% of all transactions with zero manual reconciliation.

Fallback: bank transfer with auto-generated references

For members who cannot or will not pay by card, offer bank transfer as an explicit alternative. The critical detail is to generate a unique, structured transfer reference for each member (e.g., “LIC-2026-04521”). When the transfer arrives, the system matches it automatically using the reference string. This semi-automatic reconciliation reduces manual matching to only those transfers where the member entered the reference incorrectly, typically 10-15% of transfers.

Events: physical POS

Keep a POS terminal for events, open days, and office walk-ins. This covers the small percentage of transactions that happen in person and provides immediate confirmation to the member. Log each POS transaction against the member record on the spot to avoid reconciliation later.

The result

With this hybrid model, a typical federation achieves:

• 70-75% of payments by online gateway (fully automatic).
• 15-20% by bank transfer with generated references (semi-automatic).
• 5-10% by physical POS at events (manual but immediate).
• Less than 5% requiring manual reconciliation.

This reduces total collection administration by 80-90% compared to a transfer-only approach, while accommodating every member’s preferred payment method.

Legal and tax considerations

Payment collection operates within specific regulatory frameworks. While this is not legal advice, these are the key areas to be aware of.

• PSD2 and SCA. European regulation requires Strong Customer Authentication for most online payments (two-factor verification via the member’s bank app). Both Stripe and Redsys support SCA through 3D Secure. Ensure your integration enforces it.
• VAT exemption. In many EU countries, sports license fees from recognized federations are exempt under the sporting services exemption (EU VAT Directive, Article 132). Consult your accountant, as rules vary by country.
• Tax reporting. In Spain, federations must file Model 190 (withholdings) and Model 347 (third-party transactions above 3,005.06 euros). Your payment system should export data in compatible formats.
• PCI DSS. By using a certified gateway, your federation never handles raw card numbers, keeping you outside PCI scope. Never store card data in your own systems or spreadsheets.

Pre-migration checklist

If you are moving from a transfer-only or cash-based model to an online payment system, work through this checklist before going live.

• Confirm your federation’s legal entity can contract with the chosen payment gateway.
• Open a Stripe account or request Redsys activation through your bank. Test the full payment flow with a real (small) transaction.
• Configure unique reference generation for the bank transfer fallback.
• Update your privacy policy to reflect payment data processing and name the gateway as a sub-processor.
• Sign the Data Processing Agreement (DPA) with the gateway provider.
• Verify that your accounting software can import transaction data from the gateway.
• Train staff on the payment dashboard: how to issue refunds, how to check payout schedules, how to handle disputes.
• Prepare a brief FAQ for members explaining the new payment options. Anticipate questions about security, refunds, and receipt availability.
• Configure payment confirmation emails so members receive immediate proof of payment.
• Plan a parallel run: accept both old and new methods for one renewal cycle before discontinuing manual-only collection.

Moving from cost center to strategic advantage

Most federations think of fee collection as a necessary administrative chore. But the method you choose has strategic implications beyond accounting.

A seamless online payment experience improves member satisfaction and renewal rates. Members who can pay in two clicks at 11 PM on a Sunday are more likely to renew than those who must remember to make a bank transfer during business hours. Automatic reconciliation frees your staff to spend time on sport development, club support, and member services instead of matching bank statements.

The combination of lower total cost, higher renewal rates, and freed staff capacity turns your payment infrastructure from a cost center into a genuine competitive advantage. It is one of the highest-return investments a federation can make, and one of the simplest to implement with modern tools.

Start with the hybrid model. Measure the results after one season. The numbers will speak for themselves.