Curated market guide
Germany PSP routes to verify first
Which PSPs, acquirers, gateways, and local payment routes should a merchant ask first for Germany?
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 / 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 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
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
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?
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.
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?
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?
Route comparisons
How local customers usually pay
Germany should be researched from the customer's payment habit first, not from a generic global checkout menu. Current public records point to Digital wallet, General commerce, Buy now, pay later, Card acquiring, Instant payment and Bank transfer, while provider discovery may include banks, PSPs, gateways, acquirers and regional aggregators. For a small merchant, the practical question is which of those routes a real customer recognizes and which provider can legally onboard the merchant entity. Cards may be enough for some cross-border testing, but local conversion often depends on domestic bank rails, wallets, QR, payment links, cash-style collection or local debit schemes. Ask providers to separate live local methods from roadmap items, then confirm payment status timing, refund mechanics, settlement currency and support coverage before committing engineering work.
- Digital wallet acceptance through a provider that can onboard your merchant entity. Confirm customer experience, failed-payment handling, refund path and settlement impact before launch.
- Buy now, pay later acceptance through a provider that can onboard your merchant entity. Confirm customer experience, failed-payment handling, refund path and settlement impact before launch.
- Card acquiring acceptance through a provider that can onboard your merchant entity. Confirm customer experience, failed-payment handling, refund path and settlement impact before launch.
Payment methods to check first
For Germany, begin with the methods that match real customer behavior, then map each one to a provider that can actually onboard your merchant. Current public records point to Digital wallet, General commerce, Buy now, pay later, Card acquiring, Instant payment and Bank transfer, but availability can vary by PSP, entity type and industry.
- Start with the payment method customers already recognize, not the provider with the longest logo wall.
- Check whether the method supports online checkout, payment links, QR, app redirects, refunds and clear transaction references.
- Keep one fallback method for buyers who cannot or will not use cards.
- Document which method is mandatory for launch and which can wait for phase two.
What to do if you do not have a local company
Do not assume a foreign company can use the same route as a local merchant in Germany. Some PSPs can onboard overseas entities, some require a local company and local bank account, and some support only selected industries. The cleanest first email states your incorporation country, product, website, expected volume, average order value, customer location, settlement currency and refund model.
- Ask whether foreign entities are accepted directly or only through a local subsidiary, distributor or merchant-of-record arrangement.
- Confirm local company, tax ID, local bank account, local director, licence and proof-of-address requirements.
- Ask which settlement currencies and payout countries are supported for your entity.
- Get the onboarding answer in writing before promising a local method to customers.
PSP and four-party provider screening
Use provider discovery to separate customer-facing payment brands from the companies that can legally process and settle funds. Public PSP/contact leads for Germany currently include local PSPs, banks, gateways and aggregators. Compare them by eligibility, method coverage, operational support and documentation quality rather than headline pricing alone.
- Ask regional PSPs and local banks which Germany methods are live for your merchant category.
- Request links to official onboarding, developer documentation, support and pricing pages.
- Do not rely on marketplace claims unless the provider confirms your entity and industry in writing.
Settlement, currency, refunds and disputes
Treat all pricing and settlement information for Germany as preliminary until confirmed by the official provider or contract. Fees, payout timing, rolling reserves, FX, chargeback costs and refund rules can change by industry, volume, risk review, settlement currency and integration route.
- Ask for transaction fee, fixed fee, refund fee, chargeback fee, payout fee, FX spread, reserve policy and minimum monthly or setup charges.
- Confirm payout timing, settlement currency, settlement account country, failed-payout handling and reconciliation file fields.
- Check whether refunds must return through the original method and whether partial refunds are supported.
- For cards, confirm dispute workflow, evidence deadlines, chargeback fees and fraud-monitoring rules.
Compliance and operating checks
Before launch in Germany, prepare KYB and risk material as if the provider will ask for it. Most delays for new merchants come from unclear ownership, unsupported industries, missing licences, incomplete websites, weak refund policies or settlement accounts that do not match the merchant record.
- Prepare company registration, ownership, director ID, website/app URL, product description, terms, privacy policy and refund policy.
- Disclose regulated products, digital content, subscriptions, marketplace activity, high-risk categories and cross-border fulfilment.
- Ask how the provider screens sanctions, fraud, AML risk, chargebacks and customer complaints.
- Keep sensitive or restricted markets at compliance-review level; do not use unofficial workarounds.
Questions to ask service providers
Send a concise written checklist to every Germany PSP or aggregator so responses can be compared side by side. The goal is to expose hidden entity, settlement, support and technical gaps before engineering work begins.
- Which payment methods are live today for my exact merchant entity, industry and customer geography?
- Do you support hosted checkout, API, plugin, payment links, webhooks, sandbox, refunds and reconciliation exports?
- Who is the merchant of record, who handles chargebacks and who owns customer support for failed payments?
- What documents are requested, how is approval reviewed, and what would cause rejection?
- Can you provide official links for pricing, settlement terms, developer docs and support escalation?
Common beginner mistakes
The most common mistake in Germany is treating payment acceptance as a logo checklist. Local conversion depends on customer habit, provider eligibility, settlement flow, refund support and operational reliability. A cheaper-looking route can become expensive if it cannot settle where you need, cannot refund cleanly or cannot support the methods buyers expect.
- Choosing cards only when wallets, mobile money, bank transfer, QR or cash-style routes are normal for local buyers.
- Building against an API before KYB, entity and settlement eligibility are confirmed.
- Ignoring refund and dispute flows until the first customer complaint arrives.
- Comparing providers without asking the same written questions of each one.
Questions merchants ask
Which payment methods should a new merchant check first in Germany?
Start with Digital wallet, General commerce, Buy now, pay later, Card acquiring, Instant payment and Bank transfer. Then confirm which provider can support your entity, industry, customer geography, settlement currency and refund model.
Can a foreign merchant accept local payments in Germany without a local company?
Sometimes, but it must be verified provider by provider. Ask whether a local entity, local bank account, tax ID, licence, local director or merchant-of-record route is required.
Which PSPs or aggregators are worth screening for Germany?
Public leads include local PSPs, banks, gateways and aggregators. Treat them as a shortlist for outreach, not as confirmed eligibility or complete market coverage.
Can I use public fee pages as a final quote?
No. Public fees are screening context only. Final pricing can vary by country, industry, volume, risk review, settlement currency, FX, reserves and contract terms.
What operational questions should I ask before integration?
Ask about onboarding documents, restricted industries, live payment methods, checkout flow, webhooks, sandbox, refunds, disputes, chargebacks, reconciliation files, settlement timing and support escalation.
What should I do if the provider has no public sales email?
Use the official contact form, support page or developer contact route, and send a short brief with your entity country, product, volume, currencies and required payment methods.