Skip to main content
Talk to an expert
PayPal logo

PayPal payment integration for ecommerce

Payments captured, settled and reconciled with governed exception handling iWeb integrates PayPal into your commerce estate with auth-capture-settle flows, reconciliation to ERP invoices and real-time alerts for payment exceptions. Works with Adobe Commerce, Magento Open Source, Shopify Plus, BigCommerce and other storefronts.

Also searched as: payment connector, checkout plugin, app, extension.

PayPaliWeb integration layeryour storefront
Talk to an expertSee the estate map ↓
Works with - Adobe Commerce · Magento Open Source · Shopify Plus · BigCommerce · Other storefronts
On this pageGet a brief reviewed
01 · What you get

What a PayPal integration gives you.

Checkout does not fail when PayPal is slow

Request timeouts and circuit breakers prevent hung transactions. Orders queue for asynchronous payment with clear customer communication instead of a blank error page.

Settlement reconciles to invoices within SLA

Daily or real-time feeds from PayPal are matched to ERP orders and invoices. Reconciliation exceptions are flagged for immediate resolution instead of discovering mismatches at month-end.

Refunds and chargebacks flow back to customer accounts

Payment reversals automatically create corresponding credit notes or order cancellations in the ERP. Customers see refund status in real time instead of receiving manual follow-up messages.

Stored payment tokens reduce repeat-purchase friction

Logged-in customers see their vaulted cards and wallets; one-click checkout works reliably. Token expiry and revocation are detected gracefully with fallback to manual entry or alternative method.

Finance has visibility into payment state across channels

Dashboard shows auth, capture, settlement and refund status by order, channel and currency. Anomalies like pending captures or orphaned refunds surface automatically instead of requiring spreadsheet hunts.

02 · When it's worth it

Where a PayPal integration earns its place.

If two or more of these are true, the integration usually pays for itself quickly.

Accept card, PayPal wallet and local alternative payment methods in a single checkout flow
Split authorisation and capture to manage order verification and stock before charging the customer
Vault and reuse customer payment tokens for subscription and one-click repeat orders
Reconcile PayPal settlement files against ERP invoices and detect payment exceptions
Route refunds, chargebacks and payment disputes back to the ERP and issue customer credits
Switch between sandbox and live PayPal environments without manual code changes
03 · The limits

Where off-the-shelf connectors fall short.

Vendor connectors are fine for simple cases. Here's where the real ones need more.

Platform-native modules lack reconciliation logic

Adobe Commerce, Magento and Shopify modules handle auth and capture but do not automatically match settlement files to orders or detect reconciliation drift. Manual invoice lookups or custom batch jobs become necessary.

Fallback behaviour is not standardised

If PayPal is unavailable during checkout, most platform modules fail the transaction. There is no built-in logic to queue orders for manual payment or route to an alternative processor.

Multi-currency and multi-region edge cases

PayPal modules may not handle currency conversion fees, regional payment method restrictions or localised 3DS rules consistently across markets. Manual overrides or separate merchant accounts per region become necessary.

Chargeback and dispute handling is incomplete

PayPal notifies of chargebacks via webhook, but most platform modules do not automatically create credit notes, reverse invoices or notify the ERP. Disputes require manual investigation and order correction.

Tokenisation and vaulting have weak lifecycle management

Stored payment tokens may expire or be revoked by the customer in PayPal's account without the commerce platform knowing. Retry logic and fallback prompts are often manual or missing.

04 · The real work

Payment processing often silently fails at reconciliation: amounts match in staging but diverge in production once fees and currency conversion enter the picture, and disputes filed weeks later reveal that chargeback notifications were never wired into the ERP.

05 · Where it sits

Where this integration sits in your estate.

PayPal holds the commercial record. The iWeb integration layer manages the rules, mappings, monitoring and exceptions. The commerce platform presents the customer-facing experience. The estate map helps agree ownership before anything is built.

Storefront independent. PayPal feeds stock, pricing, orders and customer data into your chosen platform.

System of record
Source / owner
PayPal
System of record for payment authorisation, capture and settlement
  • Payment method availability and region rules
  • Authorisation and capture transaction IDs
  • Settlement files and fee deductions
  • Refund and chargeback events
  • Tokenised payment vault
iWeb integration layer
Customer-facing commerce
Commerce platform
Adobe CommerceMagento Open SourceShopify PlusBigCommerceOther storefronts
  • Checkout payment method display
  • Order total and currency at transaction time
  • Auth and capture trigger logic
  • Refund initiation and customer confirmation
  • Real-time payment status dashboard
Connected neighbours
Integration layer
ERP
Invoice generation, credit note issuance and payment-to-invoice matching for reconciliation
Integration layer
OMS
Order capture and dispatch trigger based on payment status; refund or cancellation based on chargeback outcome
Integration layer
WMS
Stock release and dispatch confirmation are contingent on payment capture confirmation
Integration layer
CRM or CDP
Customer payment history and saved tokens inform repeat-purchase workflows and segment targeting
Integration layer
BI and reporting
Payment events feed warehouse for revenue recognition, cash flow and customer lifetime value analysis
Integration layer
Tax compliance system
Tax rates and VAT treatment are applied before payment; fees and chargebacks are tracked separately
Two-way sync where relevant
06 · Surrounding systems

Systems this integration usually sits next to.

Examples, not a closed list. iWeb is platform-agnostic on both sides: we wire this integration into whatever ecommerce platform and surrounding systems your estate already runs.

Ecommerce platforms (examples)
  • Adobe Commerce
  • Magento Open Source
  • Shopify Plus
  • BigCommerce
  • Other storefronts
Surrounding systems (examples)
  • ERP (SAP, Netsucker, Sage, Axapta)
  • OMS or order management system
  • WMS or 3PL fulfillment platform
  • Customer data platform or CRM
  • Subscription or billing engine
  • Tax compliance and VAT system
  • Dispute and chargeback management tool
  • BI and financial reporting warehouse
Not sure?

Not sure if this works with your stack?

Tell us what you’re using and what needs to connect. We’ll give you a straight view on what’s possible, what might be awkward, and the safest way to approach it.

07 · Data flows

The data flows we wire.

Each flow has a direction and an owner. We agree both before a line of code is written.

→Into PAYPAL & ERP
←From PAYPAL
↔BOTH WAYS
Payment intent and auth request: Checkout initiates a payment intent containing order total, currency, customer token and 3DS / SCA requirements
PayPal returns an authorisation ID and status, which commerce stores against the order.
Capture, refund and settlement events: Capture events confirm funds are reserved; settlement events confirm funds have transferred to merchant account
Refund events are triggered by commerce and confirmed by PayPal; refund status feeds back to the ERP and customer account.
Payment and settlement reconciliation: Daily or real-time settlement feeds from PayPal contain transaction IDs, amounts, fees and timestamp
Commerce matches these against orders and invoices in the ERP to detect missing, duplicate or partial payments.
Chargeback and dispute workflow: PayPal notifies commerce of chargebacks and disputes via webhook; commerce logs the event in the ERP and updates order status
Finance or customer service responds through PayPal's dashboard; outcome events flow back to the ERP for reconciliation.
Tokenisation and customer vault: Checkout stores customer payment tokens securely in PayPal's vault; commerce retrieves tokens for logged-in customers
Token validity and expiry are checked against PayPal on each transaction; revoked tokens trigger fallback to manual entry or alternative method.
08 · How we build it

How iWeb configures the integration around your business.

Same method on every integration. The decisions come before the code.

  1. 01
    Design auth-capture flow for your order lifecycle

    We map auth timing to stock reservation, capture to dispatch trigger and settlement to invoice reconciliation. Multi-currency and regional payment method switching are handled without checkout branching.

  2. 02
    Build reconciliation pipeline and exception dashboard

    We ingest daily or real-time PayPal settlement files, match them to ERP orders and invoices, and flag missing, duplicate or partial payments. Finance gets a single source of truth instead of three spreadsheets.

  3. 03
    Implement fallback and retry logic

    If PayPal is unavailable, orders move to a queue for manual payment or alternative processor. Timeouts and circuit breakers prevent checkout hangs; staff alerts trigger immediate investigation.

  4. 04
    Orchestrate chargeback and refund workflows

    Chargebacks and disputes from PayPal webhook trigger automatic credit note or order cancellation in the ERP. Finance is notified of outcome so they can track disputes and respond appropriately.

  5. 05
    Manage payment token lifecycle and fallback

    We detect expired or revoked tokens on checkout, prompt the customer for a new method and log the event. Vaulted tokens are cleaned up on customer request without orphaned records in PayPal or commerce.

09 · Ownership

Who owns what.

The single most important table in any integration. One system owns each field; everything else reads it.

Data
Source / owner
Maintained by
Notes
DataPayment methods enabled
Source / ownerPayPal merchant account
Maintained byFinance or payment owner
NotesCommerce displays enabled methods; PayPal controls which cards, wallets and local schemes are available per region.
DataAuthorisation and capture status
Source / ownerPayPal transaction ledger
Maintained byCommerce platform (real-time sync)
NotesPayPal is authoritative for auth ID, amount and status; commerce stores reference for order lookup and reconciliation.
DataRefund and chargeback events
Source / ownerPayPal
Maintained byFinance and commerce jointly
NotesPayPal initiates and confirms refunds and disputes; commerce logs events and triggers corresponding credit or cancellation in ERP.
DataSettlement files and reconciliation
Source / ownerPayPal settlement export
Maintained byFinance (match to ERP invoices)
NotesPayPal provides daily or real-time settlement feed; commerce reconciliation layer matches amounts and flags discrepancies.
DataTokenised payment methods and vault
Source / ownerPayPal vault
Maintained byPayPal (customer manages tokens)
NotesTokens are stored in PayPal; commerce retrieves and uses them for transactions. Customer can revoke tokens in PayPal; commerce must detect and handle gracefully.
Data3DS / SCA authentication
Source / ownerCardholder bank and PayPal
Maintained byPayPal and commerce jointly
NotesPayPal coordinates 3DS challenge; commerce must present challenge UI and pass result back. Failure to complete challenge results in transaction decline.
DataFee and currency conversion tracking
Source / ownerPayPal transaction ledger
Maintained byFinance (reconciliation)
NotesPayPal applies fees and converts currency; settlement amount may differ from invoice amount. Finance must track fees separately for accurate GAAP reporting.
10 · Experienced integrator

Built payment reconciliation before

iWeb has integrated PayPal into multi-channel commerce estates alongside ERP, OMS and reconciliation pipelines. We understand where payment processing sits in the order-to-cash cycle and how exceptions propagate between systems.

We design auth and capture timing to align with stock reservation, order acknowledgement and dispatch workflows so payment state drives fulfillment.
We build reconciliation pipelines that match PayPal settlement feeds to ERP invoices and surface fees, chargebacks and currency conversion impacts.
We handle chargeback and refund events as bi-directional flows: from PayPal to commerce, then into the ERP for credit note and revenue reversal.
We implement fallback queues and circuit breakers so payment provider downtime does not stop checkout or orphan orders.
We manage tokenisation and vault lifecycle so repeat-purchase flows work reliably and expired tokens are detected before transaction failure.
11 · Before launch

What we test before launch.

Every one of these is rehearsed before a customer ever sees the integration.

Verify auth and capture complete within checkout timeout and order moves to correct fulfillment state.
Confirm settlement feed from PayPal matches ERP invoices within 1 hour and reconciliation dashboard flags mismatches.
Test refund workflow end-to-end: customer request in commerce, refund processed in PayPal, credit note created in ERP.
Simulate PayPal outage during checkout; verify order queues locally and staff receive alert without customer-facing error.
Validate vaulted token retrieval for repeat customer, fallback to manual entry if token revoked, and vault clean-up on customer logout.
Confirm chargeback webhook from PayPal triggers order reversal, credit note and finance alert without manual intervention.
Check multi-currency order: verify amount charged in order currency, settlement in merchant currency and exchange fee logged separately.
12 · Failure points

Common risks and where they bite.

We name these on day one. A risk written down is a risk you can plan around.

Capture delay causes checkout timeout

If PayPal capture endpoint is slow or returns late, checkout hangs waiting for confirmation. Customer abandons cart; order is stuck in pre-auth state with reserved stock and no backup plan.

Settlement reconciliation drift goes undetected

PayPal settlement amounts do not match ERP invoices due to fees, chargebacks or currency conversion. Manual reconciliation at month-end reveals thousands in mismatches; finance cannot audit which orders were paid.

Refund is captured in PayPal but not credited in ERP

Customer requests refund; payment is reversed in PayPal but order in ERP remains invoiced. Customer never receives credit note; accounting assumes unpaid invoice and pursues collection.

Vaulted token is revoked but retry uses expired copy

Customer removes payment method from PayPal account. Subscription or repeat order retries the old token, which PayPal rejects. Retry logic is absent; order fails silently without customer notification.

Chargeback in PayPal is ignored by commerce

Customer disputes charge in their bank; PayPal notifies of the chargeback but commerce platform has no webhook handler. Order remains invoiced and revenue is counted; chargeback becomes a finance surprise weeks later.

Multi-currency exchange fees erode reconciliation

Order is placed in GBP but PayPal settles in USD after conversion. Conversion fee reduces settlement amount below invoice total. Reconciliation logic treating GBP and USD as equal misses the gap and flags false positives.

13 · Where it applies

Relevant services and sectors.

14 · Questions

Common questions about PayPal integrations.

How do you handle the split between authorisation and capture?

We design the timing based on your order workflow. Typically, auth happens at checkout, capture is triggered at dispatch, and settlement is confirmed after payment clears PayPal. This reduces chargeback risk and allows you to cancel unpaid orders before shipping.

What happens if PayPal is down during checkout?

We implement circuit breakers and fallback queues. If PayPal is unavailable, the order is stored locally and marked for manual payment review. Customers are notified of the delay; staff receive alerts to process payments as soon as PayPal is back.

How do you reconcile PayPal settlements with ERP invoices?

We ingest PayPal's daily or real-time settlement feed, match transactions to orders by ID and amount, and flag discrepancies. Differences due to fees, chargebacks or currency conversion are tracked separately so finance has a clear audit trail.

How are refunds and chargebacks reflected in the ERP?

When PayPal confirms a refund or chargeback, we automatically create a credit note or order cancellation in the ERP. Finance is alerted; customer receives a credit on their account or receives an email confirmation depending on your workflow.

Can customers save their payment methods for one-click checkout?

Yes. We vault payment tokens in PayPal's secure storage. On repeat visits, logged-in customers see their saved cards and wallets and can complete checkout in one click. Expired or revoked tokens are detected and customers are prompted for a new method.

How do you handle 3DS and Strong Customer Authentication?

We integrate PayPal's 3DS flow into checkout. When required by the cardholder's bank, we present the authentication challenge to the customer. We handle both frictionless and challenge-required flows and pass the result back to PayPal for transaction completion.

What happens if a refund is processed in PayPal but not in the ERP?

Our reconciliation logic detects this mismatch. We automatically create a corresponding credit note in the ERP so the order is fully reversed. If the mismatch is discovered later, a reconciliation report flags the gap for finance to investigate.

How do you handle multi-currency orders and exchange fees?

We track the original transaction currency, PayPal's settlement currency and any conversion fees separately. Exchange rates and fees are logged against the order so finance can audit cross-currency settlements and reconcile to the general ledger.

What observability do you provide for payment exceptions?

We log every auth, capture, refund and chargeback event with timestamp, amount, status and error message. A real-time dashboard shows payment status by order, channel and day. Alerts fire for failed captures, pending chargebacks and reconciliation drift.

How do you manage the lifecycle of tokenised payment methods?

We periodically check token validity against PayPal. When a token expires or a customer revokes it in PayPal, we flag it and remove it from the vault. On the next checkout, the customer sees a prompt to enter a new method instead of a cryptic payment failure.

What happens if a chargeback is filed after dispatch?

PayPal notifies us via webhook. We update the order status and create a reversal event in the ERP. Finance is alerted so they can investigate the chargeback, file a response with evidence and track the outcome through PayPal's dispute workflow.

Can you handle different payment methods per region or currency?

Yes. We route checkout through PayPal's region and currency rules. Some regions restrict certain payment methods; PayPal enforces these restrictions and we respect them. If a method is unavailable, we offer alternatives or route to a regional payment processor.

How do you test the integration without risking real transactions?

We use PayPal's sandbox environment for all testing. Sandbox transactions do not affect live accounts or settlement. We run full auth, capture, refund and reconciliation cycles in sandbox before switching to live; both environments can be toggled without code changes.

What happens if a customer disputes a charge after refund?

If a chargeback is filed after a refund is processed, PayPal may reverse the refund or apply a chargeback fee. We track both events in the ERP and provide finance with a timeline so they can respond to the dispute with evidence of the refund.

Next step

Have a PayPal integration brief?

Send the brief, or tell us what is breaking. You will get a written response from a senior expert: the integration boundary, the realistic shape, the risks worth naming, and what it takes to support after launch.
Talk to an expertOr browse all integrations →