← Back

Country payment guide

Accept payments in Italy

Italy payment selection should begin with the checkout methods customers expect for the merchant's category, not with a provider logo list. Use the page to compare PSP routes such as local acquirers, wallet or account-based options, and hosted checkout providers against onboarding fit, signing entity, settlement currency, refund and dispute flows, reconciliation files, reserves, integration effort, support ownership, and written pricing.

Which PSPs and payment routes can you explore in Italy?

Start with the payment methods and provider directory below for Italy. Research does not cover every route; contact us if you cannot find a suitable option.

No local company, or no clear contact route?

These are research leads, not approval or industry-support guarantees. Tell us the market and your company location so we can help you explore further.

7Channel recordsPublic directory entries
EuropeRegionIT
Medium, verify entity and documents, Lower, verify standard documentsOnboardingFrom structured fields
T+1, Real-time / T+0SettlementVerify on detail pages

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?

How local customers usually pay

Italy 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, Cash voucher, Cash collection, 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.
  • Cash voucher acceptance through a provider that can onboard your merchant entity. Confirm customer experience, failed-payment handling, refund path and settlement impact before launch.
  • Cash collection 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 Italy, 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, Cash voucher, Cash collection, 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 Italy. 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 Italy 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 Italy 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 Italy 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 Italy, 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 Italy 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 Italy 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.

Next actions

Next actions for Italy

Use these internal paths to move from market research to provider outreach without assuming eligibility, pricing, settlement, or local-entity access.

Questions merchants ask

Which payment methods should a new merchant check first in Italy?

Start with Digital wallet, General commerce, Cash voucher, Cash collection, 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 Italy 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 Italy?

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.