Unzer vs Stripe is a decision that affects margins, checkout conversion and regulatory risks for UK merchants. The comparison below presents actionable benchmarks, country-level payment coverage, migration steps and cost examples updated for 2025–2026. The aim is a practical, technical and legal reference for selecting a European-friendly payments stack.
How fees, acquiring and pricing models differ
Both providers use merchant-level pricing, but the structure and flexibility diverge.
Pricing model and transparency
- Stripe publishes standard rates and offers add-ons (Radar, Billing, Connect). Standard UK card pricing in recent public docs shows 1.4% + 20p for European cards and 2.9% + 20p for non‑European cards for card acceptance, with extra fees for currency conversion and optional offerings. See Stripe pricing: Stripe pricing.
- Unzer uses negotiated merchant contracts with variable acquiring fees, often bundled with local acquiring or value‑added services (subscriptions, paylater partnerships). Public pricing is less standardized; sample merchant rates seen in market surveys range typically between 1.2%–2.0% + fixed cent fees depending on volume and acquiring partner.
Example cost comparison (UK merchant, £50 ARPU, £50k monthly volume)
| Item |
Stripe (example) |
Unzer (example negotiated) |
| Card acceptance - domestic (per tx) |
1.4% + £0.20 → £0.90 |
1.25% + £0.15 → £0.78 |
| Cross-border / FX premium |
+1.5% + FX markup |
Could be lower with local acquiring partners |
| Monthly platform fees |
None (basic) / add‑ons extra |
Possible monthly gateway or risk fee |
| Estimated monthly cost |
~£750 |
~£625 (negotiated) |
Numbers are illustrative based on public Stripe tiers and typical Unzer merchant deals in 2025; exact figures depend on contracts, chargeback rates and payment mix.
Settlement, reserves and chargeback policy
- Settlement times: Stripe standard payouts for UK merchants generally settle in 1–2 business days; instant payouts are available with fees. See Stripe payout docs: Stripe payouts.
- Unzer settlement depends on the acquiring partner and contract; common terms include next‑day or 2–3 business day settlement, with potential rolling reserves for higher‑risk sectors.
- Reserves & holds: Both providers may apply rolling reserves or longer holds for new merchants or high‑chargeback verticals; contract terms and underwriting rules determine thresholds.
Technical benchmarks: latency, uptime, SDKs, and reconciliation
Performance metrics matter for conversion, troubleshooting and reconciliation.
Latency and authorization times
- Authorization latency: Typical card authorization times across modern gateways average 200–600 ms. Benchmarks collected from public status pages and independent monitors in 2025 show Stripe authorization median ~250–400 ms under normal load; Unzer authorization medians vary by acquiring path but commonly range 300–700 ms in European routes.
- Impact on UX: Each 100 ms additional latency can reduce conversion, especially on mobile. Prioritize server‑side optimizations and local endpoints.
Uptime and SLAs
- Stripe publishes a public status and historical uptime data on status.stripe.com and maintains high availability SLAs for enterprise customers.
- Unzer also exposes operational information via the corporate site; uptime depends on the integration (direct gateway vs partner acquirer). For mission‑critical merchants, enterprise contracts should include SLA language and financial remedies.
SDKs, APIs and languages
- Stripe: mature SDKs for JavaScript (Checkout, Elements), mobile (iOS, Android), server libraries for Node, Python, Ruby, Java, PHP and webhooks. Extensive docs support test suites and troubleshooting.
- Unzer: provides SDKs for common stacks and supports local payment methods; some integrations rely on partner plugins (Shopware, Magento). Evaluate support maturity and update cadence for the chosen SDK.
Local payment methods matrix (UK + major EU markets)
The checkout mix influences acceptance rate and fees. The table indicates typical availability (✔ = supported commonly).
| Method |
UK |
Germany |
Netherlands |
Austria |
Spain |
Sweden |
| Card (Visa/Mastercard) |
✔ |
✔ |
✔ |
✔ |
✔ |
✔ |
| SEPA Direct Debit |
✔ |
✔ |
✔ |
✔ |
✔ |
✔ |
| iDEAL |
✖ |
✖ |
✔ |
✖ |
✖ |
✖ |
| Sofort / Giropay |
✖ |
✔ |
✖ |
✔ |
✖ |
✖ |
| Klarna / Paylater |
✔ (via partners) |
✔ |
✔ |
✔ |
✔ |
✔ |
| Apple Pay / Google Pay |
✔ |
✔ |
✔ |
✔ |
✔ |
✔ |
- Stripe supports a broad set of local methods across Europe via native integrations and partners. See supported payment methods: Stripe payment methods.
- Unzer emphasizes local acquiring relationships and integrated local methods in Germanic markets; it can be advantageous for merchants focusing on DACH or Benelux regions.
Migration and integration: step‑by‑step checklist and mapping
Moving between providers requires planning for webhooks, customers, refunds and reconciliation.
Pre-migration assessment
- Map all payment flows: subscriptions, one‑time sales, marketplace payouts, and stored payment methods.
- Extract full transaction history and reconcile pending settlements and disputes.
- Audit PCI scope and tokenization approach.
Migration steps (technical)
- Provision account and test credentials in parallel.
- Implement tokenization: ensure existing card tokens can be migrated or prompt customers for re‑authentication (SCA considerations).
-
Map webhooks: match event names, idempotency keys and signature verification. Example mapping:
-
Stripe event: payment_intent.succeeded
-
Unzer equivalent: payment.completed (verify exact name in the merchant portal)
-
Run shadow traffic in test mode or route a small percentage of live traffic to the new gateway and compare outcomes.
- Switch settlement cutover during low volume and monitor chargebacks and refunds closely.
Webhook & API snippet (conceptual)
- Example webhook signature verification (pseudocode):
if verify_signature(header_sig, payload, stripe_secret) == true:
process_event(payload)
if verify_signature(header_sig, payload, unzer_secret) == true:
process_event(payload)
- Ensure idempotency keys and retry logic match provider semantics.
Case studies, quantitative examples and migration ROI
Concrete merchant examples highlight practical outcomes.
Example A — UK digital subscription service (50k monthly volume)
- Before (Stripe standard): Gross fees ~£1,200/month with some cross‑border FX charges.
- After (Unzer negotiated + local acquiring for EU): Gross fees reduced ~15% and local payment acceptance increased EU conversion by 6% over three months. Settlement terms tightened to next‑day in key markets.
Example B — DACH e‑commerce brand
- Switching to Unzer improved access to local paylater providers and reduced local acquiring fees, improving checkout conversion by 4–7% in Germany and Austria. Risk: migration required re‑auth of recurring customers due to tokenization differences.
Case study numbers are anonymized composites of merchant reports and market benchmarks for 2025–2026.
Legal, compliance and PSD2 considerations
Regulatory posture influences choice, especially for EU merchant onboarding.
Licensing and PSP responsibilities
- Both providers operate under European payment regulations and interact with acquiring banks. Merchants must confirm whether the provider acts as the PSP/Acquirer or routes via third parties.
- For regulatory guidance, consult the European Banking Authority: EBA and UK FCA: FCA.
PSD2 and SCA
- Both providers support Strong Customer Authentication (SCA) flows and 3‑D Secure. Migrating recurring payments will require attention to recurring use exemptions and SCA re‑authentication rules.
Decision matrix: when to choose Unzer vs Stripe
- Choose Stripe when: global rollout, mature developer platform, extensive SDKs, predictable public pricing and built‑in products (Billing, Connect) matter.
- Choose Unzer when: focus is on European markets (especially DACH/Benelux), need for negotiated acquiring rates, or tight integrations with local paylater providers.
Frequently asked questions
What are the core cost drivers when comparing Unzer vs Stripe?
Core drivers are transaction fees, cross‑border/FX fees, monthly gateway or service fees, chargeback rates, and settlement reserve policies. Payment mix (cards vs local methods) materially changes effective cost.
Can stored card tokens be migrated from Stripe to Unzer?
Direct migration of card tokens is generally not possible due to tokenization and PCI constraints. Typical approaches are: merchant‑initiated re‑authentication, tokenization migration services offered by processors, or prompting customers to re‑enter card details.
Which provider has better coverage for German local methods like Sofort and Giropay?
Unzer often offers stronger regional acquiring and local method bundling in Germanic markets, while Stripe supports those methods globally via native integrations or partners. Confirm the exact method availability in the merchant portal: Unzer.
How long does migration typically take?
A straightforward migration can range from 2–8 weeks. Complex setups with subscriptions, marketplaces and stored payment methods may require 2–4 months including testing and cutover.
Do either provider hold rolling reserves for new merchants?
Both providers may require reserves based on underwriting and vertical risk. Reserve amounts and durations are specified in merchant contracts and underwriter policies.
Are there differences in chargeback management?
Chargeback processes are similar in principle but differ in tooling, automation and dispute rates based on acquiring partners. Evaluate the dispute management UI, evidence upload APIs and automated representment features.
Which option reduces FX costs for EU expansion?
Local acquiring and currency acceptance rules matter. Unzer can reduce FX fees when leveraging local acquirers in target markets; Stripe offers multi‑currency accounts and conversion tools but may charge FX margins.
Is PCI compliance scope reduced by either provider?
Both providers offer tokenization and hosted checkout to reduce PCI scope. The chosen integration (hosted vs direct) determines merchant PCI requirements.
Run parallel processing for a percentage of live transactions, monitor authorization latency, decline rates and reconciliation mismatches. Request SLA commitments in contracts.
Conclusion
Selecting between Unzer and Stripe depends on market focus, technical requirements and negotiation leverage. Stripe excels in developer experience, global reach and predictable public pricing. Unzer can provide cost and conversion benefits for merchants prioritizing European acquiring, local payment methods and bespoke contracts. The optimal choice follows a measured assessment: review payment mix, run a shadow migration, confirm SCA handling, and include SLA and reserve terms in the contract.
