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: ItalyPublic contact leads: 2

Decision summary

Italy: who to contact and what to ask

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

Route groups: Local acquirer / bank merchant services: 1 · Wallet / mobile-money route: 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

Italy PSP routes to verify first

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

6
psp_or_aggregator · curated

PSP / aggregator shortlist

Prioritize this when you want one integration for cards, wallets, SEPA-related flows, checkout localization, refunds, and reporting.

Do not state that every merchant needs an Italian company. Ask whether the route supports your current entity, whether an Italian/EU entity or local bank account is required, and whether the use case has public-sector or tax-specific obligations.

  • Which Italian-relevant payment methods can you enable for my merchant category?
  • Can my current entity onboard, or do you require an Italian/EU company or local bank account?
  • How are refunds, disputes, payment references, and reconciliation exported?
payment_gateway · curated

Gateway / orchestration route

Prioritize this when you already have or expect separate acquiring and need technical routing, plugins, hosted pages, or multi-provider orchestration.

Do not state that every merchant needs an Italian company. Ask whether the route supports your current entity, whether an Italian/EU entity or local bank account is required, and whether the use case has public-sector or tax-specific obligations.

  • Which acquirers, wallets, and bank-payment routes can you connect in Italy?
  • What is your role in KYB versus the acquiring or payment-method partner?
  • Do you support recurring, payment links, refunds, and reporting for the required methods?
bank · curated

Bank merchant-services route

Prioritize this when local settlement, SEPA collection, business banking, or pagoPA-related institutional payment acceptance is relevant.

Do not state that every merchant needs an Italian company. Ask whether the route supports your current entity, whether an Italian/EU entity or local bank account is required, and whether the use case has public-sector or tax-specific obligations.

  • Is this route intended for ordinary ecommerce, public-sector payments, or bill/invoice collection?
  • Do you require an Italian IBAN, Italian company, or local tax registration?
  • Which technical PSP or certified partner should integrate the flow?
cards_and_wallets_via_psp_acquirer · curated

Cards and wallets via PSP/acquirer

This is the broad ecommerce baseline and gives merchants one place to validate card acceptance, 3DS, refunds, disputes, and reporting.

Do not state that every merchant needs an Italian company. Ask whether the route supports your current entity, whether an Italian/EU entity or local bank account is required, and whether the use case has public-sector or tax-specific obligations.

  • Use official sales form/contact page; do not assume eligibility.
  • Which Italian-relevant payment methods can you enable for my merchant category?
  • Can my current entity onboard, or do you require an Italian/EU company or local bank account?
sepa_payments_for_recurring_and_invoice_use_cases · curated

SEPA payments for recurring and invoice use cases

Italy is in SEPA, so recurring and B2B collection should be discussed with mandate and reconciliation details, not just checkout buttons.

Do not state that every merchant needs an Italian company. Ask whether the route supports your current entity, whether an Italian/EU entity or local bank account is required, and whether the use case has public-sector or tax-specific obligations.

  • Ask the provider about mandate ownership, return codes, references, and settlement account requirements.
  • Which Italian-relevant payment methods can you enable for my merchant category?
  • Can my current entity onboard, or do you require an Italian/EU company or local bank account?
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.

0

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

Local acquirer / bank merchant services

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

1
Italy · Acquirer / merchant services · Official form only

Nexi

card paymentsPOSecommerce gatewaydigital wallets

Italian merchant payment provider offering POS, ecommerce, card acquiring, and digital payment services.

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.

1
Italy · Wallet operator · Public email

Satispay Business

Satispay walletQR paymentsin-store paymentsonline payments

Italian wallet and merchant acceptance network enabling QR, in-store, and online payments for businesses.

Official help content mentions Italian VAT number, tax code, or fiscal representative context; final eligibility must be confirmed with Satispay.

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.