Skip to main content
Talk to an expert
Clearpay logo

Clearpay payment integration for ecommerce

Clearpay at checkout with settlement reconciled to your ERP Integrate Clearpay to offer pay-later checkout, capture authorisations in real-time and reconcile settlement files into your ERP's revenue and bank accounts. Works with Adobe Commerce, Magento Open Source, Shopify Plus, BigCommerce and other storefronts.

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

ClearpayiWeb 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 Clearpay integration gives you.

Checkout conversion uplift

Offering Clearpay removes a barrier for shoppers who prefer flexible payment terms over upfront card charge. Behavioural data shows pay-later adoption drives basket size and repeat purchase, particularly in younger demographics.

Simplified payment method management

Rather than negotiating multiple PSP contracts, Clearpay sits as one option alongside card, Apple Pay and Google Pay. You reduce PCI scope and simplify your payment method portfolio.

Clearer cash flow forecasting

Clearpay settlement reports give your finance team predictable visibility into when money lands. You can forecast cash weeks ahead instead of waiting for customer card reconciliation.

Reduced fraud and chargeback risk

Clearpay performs identity and credit checks before approving; your fraud and chargeback exposure shifts to them. You keep the transaction but avoid the review and dispute overhead.

Lower operational refund friction

Refunds flow back to Clearpay's system automatically; you don't chase failed card reversals or manage manual refund rejects. Shopper disputes with Clearpay are their problem, not yours.

02 · When it's worth it

Where a Clearpay integration earns its place.

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

Enable Clearpay as a checkout payment method alongside card and other providers
Capture and confirm payment authorisations in real-time during order placement
Issue full and partial refunds and reverse transactions in the Clearpay system
Reconcile Clearpay settlement files against ERP bank and revenue accounts
Handle declined authorisations and fallback to alternative payment methods
Report Clearpay transaction volume and value for cash flow forecasting
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.

Limited shopper identity verification

Clearpay performs its own identity and credit checks during authorisation; your commerce platform has no visibility into why an authorisation failed or what the shopper can do to retry. You must create a fallback UX that doesn't expose Clearpay's decline reasons.

Refund timing and notification gaps

Clearpay may take 3-5 working days to process and settle refunds back to the shopper's original card. Your commerce platform must communicate this delay clearly and not assume instant reversal.

No real-time shopper balance or eligibility check

You cannot query Clearpay during checkout to ask 'is this shopper eligible for Clearpay' or 'how much can they spend'. Eligibility is determined only at authorisation time, meaning you may show Clearpay as an option then decline the order at the last moment.

Settlement currency and FX handling

If you sell in multiple currencies, Clearpay may settle in GBP only, requiring you to manage FX conversion and reconciliation separately in your ERP.

Partial capture and split shipment complexity

Clearpay authorises the full order value upfront. If you ship in instalments or allow partial refunds, the reconciliation between authorised, captured and refunded amounts can drift from your ERP's expectation.

04 · The real work

The lag between authorisation and settlement creates a reconciliation window where orders are complete but bank money hasn't arrived; most teams underestimate how this affects cash flow forecasting and monthly close.

05 · Where it sits

Where this integration sits in your estate.

Clearpay 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.

One integration architecture, any storefront. Clearpay connects through the same governed layer whatever commerce core you run.

System of record
Source / owner
Clearpay
Payment provider for point-of-sale pay-later authorisations and settlement
  • Shopper eligibility and credit decision
  • Payment authorisation and plan creation
  • Settlement and bank transfer timing
  • Chargeback and dispute resolution
  • Refund reversal and processing
iWeb integration layer
Customer-facing commerce
Commerce platform
Adobe CommerceMagento Open SourceShopify PlusBigCommerceOther storefronts
  • Payment method presentation in checkout
  • Fallback payment method selection
  • Authorisation token storage and order association
  • Refund initiation and tracking
  • Customer communication on payment status
Connected neighbours
Integration layer
ERP
Receives settlement files daily or weekly; reconciles against sales revenue and bank accounts; records refunds as reversal entries.
Integration layer
Order management system
Stores Clearpay authorisation tokens and tracks refund status; integrates with shipping and returns workflows.
Integration layer
Fraud detection
May run in parallel with Clearpay; benefits from Clearpay's identity verification but maintains independent transaction rules.
Integration layer
Customer communication platform
Sends transactional emails about payment confirmation and settlement; may reference Clearpay payment plan status in order updates.
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 (accounting, bank reconciliation, revenue recognition)
  • Order management system (OMS)
  • Fraud detection engine
  • Customer data platform (CDP)
  • Email and SMS marketing platform
  • Business intelligence and reporting
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 CLEARPAY
←From CLEARPAY
↔BOTH WAYS
Payment intent and authorisation: Your commerce platform sends shopper amount, currency, order reference and billing/delivery addresses to Clearpay when they select the payment method
Clearpay returns an authorisation token that locks the shopper into the payment plan.
Authorisation confirmation and status: Clearpay notifies your commerce platform immediately whether the authorisation succeeded or failed, triggering order confirmation or payment decline flow.
Refund and cancellation requests: When a customer requests a refund or you cancel an order, your commerce or ERP system sends the refund amount and original transaction reference to Clearpay for processing.
Settlement and reconciliation data: Clearpay sends daily or weekly settlement files showing cleared payments, fees, chargebacks and refunds
Your ERP ingests these for bank reconciliation and revenue recognition.
Declined authorisations and exceptions: If Clearpay declines an order, your commerce platform must catch the error, surface it to the shopper and offer fallback payment options
Clearpay may flag disputes or chargebacks that need refund reversal or communication.
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
    Payment orchestration and failover

    We integrate Clearpay into your existing payment method selector, ensuring it coexists safely with card, alternative PSPs and legacy payment gateways. If Clearpay declines an order, we route the shopper to the next available method without loss of checkout context.

  2. 02
    Real-time authorisation and error handling

    We call Clearpay's API synchronously during checkout, capture the authorisation token and handle connection timeouts, rate limits and API errors gracefully. Failed calls trigger a retry loop or fallback, not a hung order.

  3. 03
    Settlement reconciliation and ERP integration

    We build the pipeline to fetch Clearpay settlement files, parse them, validate totals against your ERP's sales ledger and load transactions into bank reconciliation. We flag mismatches and partial settlements for manual review.

  4. 04
    Refund and dispute workflow

    We implement full-refund and partial-refund requests, route them to Clearpay with idempotency safeguards and report the outcome back to your order management system. We track disputed or rejected refunds separately for accounting.

  5. 05
    Observability and alerting

    We log all Clearpay API calls, responses and settlement events. We set up dashboards to track authorisation rate, decline reasons, settlement lag and refund processing time. Alerts trigger on anomalies like sudden decline spikes or missing daily settlement files.

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 in checkout
Source / ownerClearpay merchant account configuration
Maintained byCommerce and payments operations
NotesClearpay eligibility rules and limits are set in Clearpay's dashboard; your commerce platform surfaces the method based on merchant rules and shopper location.
DataAuthorisation requests and responses
Source / ownerClearpay transaction ledger
Maintained byClearpay (via API)
NotesYour commerce platform captures the authorisation token and stores it against the order for future refund and reconciliation reference.
DataRefund requests and reversals
Source / ownerClearpay transaction ledger
Maintained byCommerce or order management system
NotesYou initiate refunds; Clearpay processes and settles them. Your ERP must track refund status and reconcile against settlement files.
DataSettlement files and bank reconciliation
Source / ownerClearpay settlement reports
Maintained byERP finance team
NotesClearpay provides the authoritative settlement; your ERP loads, validates and reconciles it to bank movements and revenue recognition.
DataDisputes and chargeback notifications
Source / ownerClearpay dispute ledger
Maintained byClearpay and operations team
NotesClearpay notifies you of disputes; you acknowledge or provide evidence. Outcome is Clearpay's decision and appears in settlement files.
DataShopper identity and credit eligibility
Source / ownerClearpay identity and credit system
Maintained byClearpay
NotesYou do not own or access shopper credit data. Clearpay's decision is final; you only see approved or declined.
10 · Experienced integrator

Built this before

iWeb has integrated Clearpay into multiple commerce estates and understands how it fits alongside card payments, ERP reconciliation and order management. We know the authorisation, settlement and refund flows and have experience with the reconciliation and cash flow challenges that emerge at scale.

We route Clearpay through your checkout method selector with fallback logic so that a decline does not block the order.
We handle real-time authorisation calls, capture tokens and store them safely for refund and reconciliation reference.
We build the settlement file ETL pipeline: fetch, parse, validate and load into your ERP's bank reconciliation module.
We implement idempotent refund requests so retries and timeout recovery do not create duplicate reversals.
We set up observability to track authorisation rates, decline reasons, settlement lag and reconciliation drift.
11 · Before launch

What we test before launch.

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

Authorisation success and decline flows both route the shopper correctly; verify fallback payment method displays and accepts input without data loss.
Refund requests idempotently route to Clearpay; retry a refund twice and confirm only one reversal is processed.
Settlement files import daily without gaps; verify row counts and totals match Clearpay's reports and your order ledger.
Bank reconciliation correctly matches Clearpay lump deposits to individual order authorisations; test both matched and unmatched scenarios.
API timeout occurs within 5 seconds if Clearpay is slow; verify checkout does not hang and falls back to alternative payment method.
Partial refunds reverse the correct amount in Clearpay; confirm ERP records the refund on the correct date and the shopper sees credit.
Multi-currency transactions settle in the correct currency and FX is handled; verify no rounding or conversion errors in ERP reconciliation.
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.

Authorisation decline at checkout close

Shopper reaches the final step, selects Clearpay, and Clearpay declines the authorisation. If your fallback payment method is card and the shopper has no card on file, they abandon. Design your UX to show Clearpay eligibility early or offer pre-loaded alternative methods.

Settlement lag and cash flow timing mismatch

Clearpay settles transactions 2-3 days after order placement. Your ERP may recognise revenue on order date, creating a temporary book-cash mismatch. Your finance team must understand Clearpay is not instant settlement.

Refund reversal not reflecting in ERP

You issue a refund to Clearpay, but your commerce platform marks the order as refunded immediately while Clearpay takes 5 days to settle the reversal. Your ERP sees a refund in the order system but no corresponding bank movement, triggering reconciliation confusion.

Partial refund and order line reconciliation drift

You refund a single order line that shipped early, but Clearpay's settlement file reports it as a partial reversal without line-item detail. Your ERP's revenue and refund accounts don't reconcile by line. Build a reconciliation map between order lines and Clearpay transactions.

Clearpay API outage breaking checkout

Clearpay's API is down or slow. Your commerce platform times out trying to reach them, leaving the shopper hanging or showing an error. Without a timeout and fallback, every Clearpay request becomes a risk. Set a hard 5-second timeout and fail open to the next payment method.

Duplicate refund processing on retry

Your order management system retries a failed refund request. Clearpay processes both attempts, issuing two refunds. Without idempotency keys, you issue a double refund and must chase Clearpay support to reverse the second one.

13 · Where it applies

Relevant services and sectors.

14 · Questions

Common questions about Clearpay integrations.

What happens if Clearpay declines a shopper's authorisation?

Your commerce platform catches the decline response and must route the shopper to an alternative payment method. You should not show Clearpay as the only option; always have a fallback ready (card, Apple Pay, alternative PSP). We build this logic into the checkout flow with clear error messaging.

How long does Clearpay settlement take, and when does money land in my bank?

Clearpay typically settles authorised transactions within 2-3 working days. Settlement happens in batches, not transaction-by-transaction. Your bank will show the deposit as a single Clearpay payment, not individual orders. Your ERP must reconcile the lump settlement against your order ledger.

Can I refund a Clearpay transaction partially?

Yes. You can refund any amount up to the authorised total. Clearpay will reverse the refunded amount back to the shopper's Clearpay account (or original card if the shopper has multiple payment plans). Partial refunds do not automatically adjust future Clearpay instalments; the shopper's payment schedule remains unchanged.

How do I reconcile Clearpay transactions in my ERP?

Clearpay provides settlement reports (usually daily or weekly). You import these into your ERP's bank reconciliation module, matching the Clearpay deposit to your orders and refunds. We build the ETL pipeline to fetch, validate and load these files automatically. Mismatches (orders authorised but not settled, or refunds not yet reversed) are flagged for review.

What is the difference between authorisation and settlement with Clearpay?

Authorisation is immediate: Clearpay approves the shopper for the payment plan at checkout. Settlement is delayed: Clearpay transfers money to your bank account 2-3 days later. Between auth and settlement, the transaction is pending. Refunds reverse pending or settled transactions and take another 2-5 days to appear.

Can I see why a shopper's Clearpay application was declined?

No. Clearpay does not expose decline reasons to you. You only see 'approved' or 'declined'. If a shopper asks why, you cannot provide a specific answer; you must refer them to Clearpay's customer support or suggest an alternative payment method.

What if I need to cancel an order that was authorised with Clearpay?

You can issue a full refund to reverse the authorisation immediately. Clearpay will cancel the shopper's payment plan and credit their Clearpay account. If the order has already partially shipped and settled, the refund will apply to the settled portion only; any remaining pending balance may need manual intervention with Clearpay.

How does Clearpay handle chargebacks and disputes?

Clearpay manages chargebacks and disputes directly with the shopper and their bank. If a shopper disputes the transaction, Clearpay investigates and decides the outcome. You will see the dispute reported in your settlement file and your reconciliation. Clearpay may reverse the settlement if they lose the dispute.

Can I offer Clearpay to shoppers outside the UK?

Clearpay is primarily a UK and US service. International shoppers will see Clearpay as unavailable. If you operate multi-region, your commerce platform must geo-restrict Clearpay to eligible countries and show alternative methods to shoppers elsewhere.

What happens if Clearpay's API is down during checkout?

Your checkout should have a timeout (typically 5 seconds) to detect API unavailability quickly. If Clearpay does not respond, your commerce platform should fail gracefully, hide Clearpay as an option and offer other payment methods. We implement this failover logic to prevent shopper abandonment.

How do I report Clearpay transaction volume and value for accounting?

Clearpay settlement files provide totals for authorisations, captures, refunds and fees. Your ERP loads these and recognises them as revenue on settlement date (not order date, unless you use revenue deferral). You can report Clearpay revenue separately or combine it with other payment methods depending on your accounting policy.

What if my commerce platform is replatformed or my payment gateway changes?

Clearpay integration is API-based and gateway-agnostic. You can migrate to a new commerce platform or payment processor without losing Clearpay functionality. We ensure that existing Clearpay transactions are not disrupted during the switch and that settlement reconciliation continues unbroken.

Next step

Have a Clearpay 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 →