Market finder

Find PSPs by market

Browse PSPs, acquirers, wallets and gateways by country. Add your industry and entity context for the questions to ask, or contact LocalPayMap if you cannot find a suitable route.

Selected market: GermanyPublic contact leads: 4

Decision summary

Germany: who to contact and what to ask

4 public leads: 2 with public email, 2 form-only, 0 official-page-only.

Route groups: Local PSP / aggregator: 3 · Local acquirer / bank merchant services: 1

Entity status is still unclear. Write down company jurisdiction, settlement currency, target customers, industry, and expected volume before asking providers about eligibility.

No industry selected. If this is gaming, short drama, SaaS, travel, or marketplace activity, state it clearly before asking for pricing.

Regional planning

Planning more than one country?

Use a regional hub to narrow the provider categories first, then verify each country route before implementation.

Curated market guide

Germany PSP routes to verify first

Which PSPs, acquirers, gateways, and local payment routes should a merchant ask first for Germany?

6
psp_or_aggregator · curated

PSP / aggregator shortlist

Prioritize this when you need one onboarding path for cards, SEPA methods, hosted checkout, fraud tooling, and reporting.

Do not assume a German company is always required. Ask each PSP, acquirer, or bank whether your current entity can onboard, whether an EU or German entity or local bank account is required, and confirm the answer with counsel before committing engineering work.

  • Can my current merchant entity onboard for German customers, or do you require a German/EU entity or bank account?
  • Which SEPA credit transfer, SEPA Direct Debit, card, wallet, and invoice flows are available for my business category?
  • Which public form, sales route, or partner manager should I use if no sales email is listed?
acquirer · curated

Acquirer / merchant-services route

Prioritize this when card authorization control, domestic acquiring configuration, or enterprise risk review matters more than fastest launch.

Do not assume a German company is always required. Ask each PSP, acquirer, or bank whether your current entity can onboard, whether an EU or German entity or local bank account is required, and confirm the answer with counsel before committing engineering work.

  • Do you acquire directly in Germany or route through another licensed/acquiring partner?
  • How are scheme choice, 3DS, chargebacks, refunds, reserves, and settlement currency handled?
  • What documents are required for KYB and website/app review?
bank · curated

Bank merchant-services route

Prioritize this when SEPA Direct Debit, bank transfer collection, treasury reconciliation, or a local banking relationship is central.

Do not assume a German company is always required. Ask each PSP, acquirer, or bank whether your current entity can onboard, whether an EU or German entity or local bank account is required, and confirm the answer with counsel before committing engineering work.

  • Can you support merchant collection use cases rather than only ordinary business banking?
  • Who owns mandate storage, failed payment handling, returns, and customer references?
  • Is access direct, through a technical PSP, or through a banking partner?
cards_plus_sepa_via_psp · curated

Cards plus SEPA via PSP

This is the practical first shortlist for ecommerce because it lets the merchant compare card acceptance, SEPA bank flows, checkout localization, and operational reporting in one conversation.

Do not assume a German company is always required. Ask each PSP, acquirer, or bank whether your current entity can onboard, whether an EU or German entity or local bank account is required, and confirm the answer with counsel before committing engineering work.

  • Use official sales form/contact page; do not assume eligibility.
  • Can my current merchant entity onboard for German customers, or do you require a German/EU entity or bank account?
  • Which SEPA credit transfer, SEPA Direct Debit, card, wallet, and invoice flows are available for my business category?
sepa_direct_debit_for_recurring_or_invoice_heavy_flows · curated

SEPA Direct Debit for recurring or invoice-heavy flows

German customers and businesses often expect account-based payment options for recurring, invoice, and utility-style use cases, but mandate and return rules need provider confirmation.

Do not assume a German company is always required. Ask each PSP, acquirer, or bank whether your current entity can onboard, whether an EU or German entity or local bank account is required, and confirm the answer with counsel before committing engineering work.

  • Ask for the SEPA mandate model, return handling, reconciliation fields, and whether a local bank account or EU entity is required.
  • Can my current merchant entity onboard for German customers, or do you require a German/EU entity or bank account?
  • Which SEPA credit transfer, SEPA Direct Debit, card, wallet, and invoice flows are available for my business category?
KYB prep

Documents to prepare

  • Company registration certificate and operating entity details.
  • Beneficial-owner, director, and signatory identity documents.
  • Business website/app URLs, product description, refund policy, terms of service, and restricted-category explanation where relevant.
  • Bank account, settlement currency, tax/VAT/GST information, and expected processing volume.
Due diligence

Questions to ask

  • Can my current merchant entity onboard, or is a local company or bank account required?
  • Which local payment methods are live for my business category and customer flow?
  • What documents are required for KYB, technical review, and production approval?
  • How are refunds, chargebacks, reconciliation files, reserves, FX, and payout currencies handled?
  • Which public email, form, dashboard, or partner manager should be used for merchant onboarding?
Contact route fallback

If the official contact route is unclear

Use official form/contact page first; if there is no public sales inbox, use LocalPayMap WhatsApp fallback for routing help.

  • Which local payment methods are live for my business category and customer flow?
  • What documents are required for KYB, technical review, and production approval?
  • How are refunds, chargebacks, reconciliation files, reserves, FX, and payout currencies handled?
  • Which public email, form, dashboard, or partner manager should be used for merchant onboarding?

Local PSP / aggregator

Start here when you need a provider route for local wallets, bank transfer, cards, or aggregated checkout.

3
Germany · Payment gateway · Public email

Computop

card paymentsalternative payment methodshosted payment pagePOS

German PSP providing Computop Paygate for online, mobile, and point-of-sale payment acceptance across markets.

Computop is a Germany-origin payment gateway; local contracting requirements must be confirmed with Computop.

Germany · PSP / aggregator · Public email

PAYONE

card paymentsSEPAwalletsinvoice payments

German PSP and acquiring provider offering online, mobile, and POS payment acceptance for merchants.

Official pages identify PAYONE as a German merchant payment provider, but merchant eligibility and entity requirements must be confirmed with PAYONE.

Germany · PSP / aggregator · Official form only

Unzer

card paymentsSEPAinvoice paymentsinstallments

German payment platform combining ecommerce, BNPL, POS, and merchant management tools for European businesses.

Official onboarding documentation describes compliance and risk checks; final requirements must be confirmed with Unzer.

No public sales email found yet. Open official form or ask LocalPayMap to help verify.

Local acquirer / bank merchant services

Use this route when a local entity, merchant account, or acquiring relationship may be required.

1
Germany · Acquirer / merchant services · Official form only

Nexi Germany

cardsmerchant acquiringonline payments

Nexi Germany official merchant contact route for Germany; verify merchant fit, eligibility, and local requirements directly with the provider.

Official source identifies Nexi Germany GmbH and German merchant contact routes; onboarding requirements must be confirmed.

No public sales email found yet. Open official form or ask LocalPayMap to help verify.

Wallet / mobile-money route

Use this route when local customers rely on wallet or mobile-money checkout, then confirm the provider route.

0

No public candidates in this group yet. Check other groups or submit requirements.

Global PSP with local methods

Useful for cross-border teams, but each market, method, entity, and payout route still needs confirmation.

0

No public candidates in this group yet. Check other groups or submit requirements.

Contact-first / needs manual verification

Use these leads to ask official questions before treating the option as an onboarding path.

0

No public candidates in this group yet. Check other groups or submit requirements.

Questions to ask before integration

  • Does this provider support my merchant entity location, industry, and transaction model?
  • Is a local company, local bank account, tax registration, licence, or local contact required?
  • Which local wallets, bank transfers, card acquiring, refunds, and dispute flows are actually supported?
  • What settlement currency, timing, reserves, chargeback fees, and contract fees apply in writing?
  • Are API, plugins, webhooks, sandbox, reconciliation exports, and go-live support available?

Pricing and settlement caveat

Published pricing is suitable for initial screening only. Actual pricing can vary by country, industry, volume, settlement currency, integration model, and contract terms. Confirm the official pricing page or a provider quote before going live.