← Back to the directory

Payment channel profile

PayPal

PSP / aggregator · Netherlands

NetherlandsPrimary marketMain service market
PSP / aggregatorRole / typeDigital wallet
Lower, verify standard documentsEntity requirementOnboarding conditions
T+1SettlementPayout timing

Overview

PayPal is listed as digital wallet in the LocalPayMap public directory. Use this page to prepare due-diligence questions; product availability and terms must be verified directly.

This is a market-specific PayPal record, not a duplicate of the brand overview and not the only official onboarding or pricing route. The brand page aggregates related countries and PSP contact leads; this page keeps the local payment scenario visible.

Role in the payment stack

PSP / aggregator

This is closer to a provider route than a buyer-facing payment method. Confirm which local methods it can enable, where your merchant entity can be onboarded, and who handles settlement, refunds, and disputes.

Merchant usage and connection route

PayPal in the payment stack

PayPal is useful when merchants want a widely recognized wallet and checkout brand for cross-border or domestic buyers, but the decision should be made by market, entity, product category, and payment mix. Evaluate checkout conversion, buyer funding sources, disputes, reserves, refunds, account risk, and how PayPal sits beside cards and local methods.

Connection route

Merchants may connect directly to PayPal, through an ecommerce platform, marketplace, PSP, orchestration layer, or checkout plugin. Confirm whether the route creates a direct PayPal merchant account relationship, a platform-managed flow, or a PSP-managed integration, and who controls onboarding, settlement, reporting, and disputes.

Verification questions

  • Which PayPal product, country, legal entity, currency, and checkout surface are in scope?
  • Is the merchant contracting directly with PayPal or using a platform, PSP, plugin, or marketplace route?
  • How are buyer disputes, refunds, reserves, account reviews, chargebacks, and reporting handled?
  • Does the provider support the merchant's category, transaction model, recurring needs, and customer geography?
  • How will PayPal transactions reconcile with card acquiring, local payment methods, tax, and order management systems?

Merchant caveats

  • PayPal account availability and product scope vary by country, entity, and merchant category.
  • Buyer familiarity does not remove the need to review disputes, reserves, and account-risk processes.
  • Platform or marketplace routes may limit direct control over reporting and settlement.
  • Provider examples are discovery examples only, not recommendations or support evidence.

Provider examples to verify

PayPalMollieOpayoTelrNoon PaymentsPayComet

Related markets

AustraliaAustriaBrazilCanadaEuropean Economic AreaMexicoUnited KingdomUnited States

Keep researching

This explanation separates payment methods, PSPs/aggregators, acquirers/banks, wallets, and networks/schemes. It does not publish coverage, eligibility, pricing, settlement timing, or onboarding guarantees.

Sources

What merchants should confirm

  • Whether the product is available to merchants incorporated outside the target country.
  • Whether a local entity, local bank account, licence, or local tax registration is required.
  • Supported checkout flows, currencies, refunds, disputes, reconciliation fields, and payout options.
  • Industry restrictions, reserve policies, onboarding documents, and implementation support.

Merchant eligibility

The initial application may be relatively accessible, but eligibility still depends on market, industry, and risk review.

Pricing and settlement

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.

Settlement timing, payout currency, foreign exchange, reserves, and withdrawal rules must be confirmed with the provider.

Capability verification checklist

Use this public checklist before you ask for a quote or implementation access. Treat unknown fields as questions to verify, not as unsupported features.

  • Confirm who owns onboarding, KYB review, pricing, settlement, refunds, disputes, reconciliation, reserves, and support for the route you will use.
  • Open the official pricing, developer, support, or website links where available, then verify the exact production terms with the provider or PSP.
  • Do not treat public notes as final approval, final pricing, settlement timing, or a guarantee that your merchant entity can go live.

Official links to open

Commercial terms to confirm

Pricing modelwallet acceptance or psp priced
Pricing basisofficial public pricing or terms
Fields still to confirm
  • Fee range: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • FX markup: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • Chargeback fee: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • Payout fee: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • Reserve policy: confirm with the provider, acquirer, PSP, or official documentation before launch.

Integration route to confirm

API / checkout routeREST API (PayPal Orders v2; JavaScript SDK v6)
SDK languagesJavaScript, Server SDKs to be confirmed
Sandboxyes
Webhooksyes
Fields still to confirm
  • Idempotency: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • PCI scope: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • 3-D Secure: confirm with the provider, acquirer, PSP, or official documentation before launch.

Operational features to confirm

Recurring billingyes
Marketplace splityes
Partial refundyes
Preauth / captureyes

Public pricing signals are for initial screening only. Actual quotes can vary by country, industry, transaction volume, settlement currency, integration route, and contract terms.

Visit the official website