Plug-ins · hosted checkout · headless

Shopping cart payment gateway — every cart, one integration.

Plug-ins for Shopify, WooCommerce, Magento and PrestaShop. Hosted checkout for bespoke and headless carts. Behind every cart is the same unified API, PCI L1 vault, smart-routed multi-acquirer panel and one reconciliation feed.

Book a cart review Read the API docs
  • Shopify
  • WooCommerce
  • Magento (Adobe Commerce)
  • PrestaShop
  • OpenCart
  • BigCommerce
  • Custom / headless
Plug-ins
for Shopify, WooCommerce, Magento, PrestaShop
Hosted
redirect or iframe for bespoke carts
300+
methods reachable through one integration
1 ledger
across every cart and every provider

Key benefits

Why shopping cart payment processing looks different here

Four properties that show up the moment a merchant plugs a real cart into a real multi-acquirer platform instead of a single-provider gateway.

  1. 01

    Drop-in for popular carts

    Install the plug-in from the platform's marketplace, paste the merchant credentials, and the checkout starts routing through the connected acquirer panel. No custom back-end code required for merchants on Shopify, WooCommerce, Magento or PrestaShop.

  2. 02

    Hosted checkout for bespoke carts

    For custom or headless carts, the merchant redirects the buyer to a hosted checkout URL or embeds an iframe. The cart passes an order reference; the platform handles the whole authorisation flow and posts a signed webhook back on completion.

  3. 03

    Smart routing under the same cart

    Every authorisation runs through the routing engine — per-BIN, per-currency, per-country. Soft declines cascade to the next ranked provider inside the same authorisation; the buyer sees one decision, not a retry loop on the confirmation page.

  4. 04

    One ledger across carts

    Merchants running multiple carts (Shopify for DTC, headless for wholesale, a bespoke B2B cart) get one reconciliation feed across all of them. Every settlement row is tagged with the originating cart, provider, currency and applied FX rate.

How the shopping cart payment gateway wires up

From install to reconciled ledger in six steps

What actually happens between the plug-in installation on the cart and the settlement row landing in the merchant's accounting system.

  1. 01

    Cart-side install

    Install the plug-in from the cart's marketplace (Shopify, WooCommerce, Magento, PrestaShop) or paste the merchant's public key into the checkout config for a hosted-page integration.

  2. 02

    Configure methods per market

    In the topropay dashboard, enable the payment methods the merchant wants to surface — cards, wallets, BNPL, regional bank rails — per country. The cart re-orders the method list per buyer's country automatically.

  3. 03

    Buyer reaches the checkout

    The buyer completes the cart, hits pay-now, and the checkout renders the method list. Card fields sit in hosted iframes; wallets appear as native pay-sheets; BNPL and bank rails redirect through the acquirer's flow.

  4. 04

    Route and authorise

    The authorisation runs through the routing engine — the top-ranked connected acquirer clears it. Soft declines cascade to the next ranked provider inside the same authorisation.

  5. 05

    Post the order back to the cart

    A signed webhook posts the final order state (paid, pending, failed) back to the cart. The cart marks the order paid and triggers fulfilment, receipt emails and downstream automations.

  6. 06

    Reconcile the settlement

    The daily settlement feed rolls up every cart order into one ledger — tagged by cart, provider, method, currency and applied FX rate — for import into the merchant's accounting system.

Main use cases

Where shopping cart payment processing on a panel earns its keep

Six recurring merchant shapes that benefit from a multi-acquirer cart-side gateway over a single-provider one.

  • DTC

    DTC brands on Shopify with growth traffic

    A DTC brand outgrows Shopify Payments' geography or method mix and wants a multi-acquirer cart-side gateway that keeps the Shopify checkout branding intact but routes to a panel of connected acquirers underneath.

  • Woo

    WooCommerce stores with international traffic

    A WooCommerce store shipping to EU, UK and APAC uses the plug-in to surface local methods per market — SEPA and iDEAL for EU, Bacs for UK, PayID for AU — through one integration.

  • Mag

    Magento / Adobe Commerce mid-market

    A mid-market Magento merchant with 500k+ orders per year uses the plug-in for one merchant record across every store view, with reconciliation split by store view for finance.

  • Custom

    Custom / headless commerce

    A headless commerce merchant integrates against the hosted checkout redirect from their own front-end, keeping the storefront experience bespoke while the checkout inherits PCI L1 scope reduction.

  • Wholesale

    B2B wholesale carts

    A wholesale merchant running a NET-30 cart alongside an instant-pay retail cart uses the same platform for both — instant card / BNPL for retail, invoice pay links plus SEPA SDD for wholesale.

  • Multi

    Multi-cart merchants

    Merchants running a Shopify cart, a WooCommerce cart and a bespoke cart under one brand get one merchant record, one method configuration and one reconciliation feed across all three surfaces.

Platform features

Capabilities behind the shopping cart payment gateway

Twelve capabilities the platform ships once and reuses across every supported cart surface — from the Shopify plug-in through to a bespoke headless cart.

  • Shopify plug-in

    Marketplace-listed plug-in; supports Shopify's checkout extensibility API and Shop Pay where enabled.

  • WooCommerce plug-in

    WordPress-listed plug-in; supports blocks-based checkout and the classic short-code cart.

  • Magento / Adobe Commerce

    Extension compatible with Magento 2.4+ and Adobe Commerce; multi-store-view aware.

  • PrestaShop / OpenCart / BigCommerce

    Additional plug-ins for the wider SMB cart ecosystem — install from the merchant dashboard.

  • Hosted checkout URL

    For bespoke or headless carts: redirect or iframe surface, brand-configurable through the dashboard.

  • Embedded hosted fields

    Alternative to redirect: card-number, expiry and CVV render as hosted iframes inside the merchant's own confirmation page.

  • SDK for full control

    Server SDK plus client primitives for merchants who want to build a bespoke checkout while still using the platform's vault and routing.

  • Signed webhook events

    Auth, capture, settlement, refund and dispute events post signed back to the cart with replay-safe IDs.

  • Per-market method sorting

    Method list re-orders per buyer's country — cards first, wallets by device, regional bank rails where relevant.

  • Multi-currency presentment

    Prices render in the buyer's currency where the merchant configures presentment and the acquirer supports it.

  • Vault tokens across sessions

    Vault tokens carry between guest and registered sessions; returning buyers see saved cards without re-entry.

  • One reconciliation feed

    Daily normalised feed tagged by cart, provider, method, currency and FX rate — one export across every cart surface.

Industry relevance

Shopping cart payment processing for licensed EU, UK, APAC and LATAM merchants

topropay's cart-side posture targets licensed merchants operating across EU, UK, APAC and LATAM — DTC brands on Shopify or WooCommerce, mid-market retail on Magento, headless / composable commerce, wholesale B2B carts, licensed gaming operators (where licensed) and the wider e-commerce ecosystem.

Trust & compliance

Compliance posture the cart plug-ins inherit

One audited environment for the platform; PCI scope drops to SAQ A or SAQ A-EP on the cart side; scheme programmes surfaced per connected acquirer.

PCI DSS Level 1
Card data captures into the platform vault before any acquirer sees it; the cart's PCI scope drops to SAQ A (hosted) or SAQ A-EP (embedded hosted fields).
SCA & PSD2
Selective EMV 3DS2 on the card path keeps European approval high without skipping the SCA bar; per-BIN exemption logic runs on the platform side.
Scheme programmes
Visa VDMP / VAMP / VFMP and Mastercard ECP / EFMP positions surfaced per acquirer; routing weights rotate around at-risk lanes.
Bank-rail mandate posture
NACHA authorisations for ACH, SEPA mandate IDs for SEPA Direct Debit — captured at cart-side pay-now, retained per scheme rules.
Sanctions & AML alignment
Sanctions screening at onboarding; AML monitoring tuned per merchant vertical, cart volume and cross-border mix.
Licensed verticals only
Licensed gaming, regulated financial services and other compliance-bound verticals supported only where current operating licences exist. Grey and black-market verticals are out of scope.

Ready to plug in

Plug your cart into an orchestration platform.

A 30-minute cart review covers the platform your merchant is on today, the methods relevant to your buyers, migration timing from your current gateway, and a sandbox to test against before any commercial commitment.

Book a cart review Read the API docs

Frequently asked

Buyer questions about shopping cart payment gateway on topropay

Definitions, cart-platform support, migration timelines, refund mechanics and the practicalities of running a multi-acquirer gateway behind a real commerce cart.

  1. 01

    What does shopping cart payment gateway mean on topropay?

    A shopping cart payment gateway on topropay is the plug-in-plus-back-end combination that connects a commerce cart (Shopify, WooCommerce, Magento, PrestaShop, or a bespoke cart) to the platform's unified authorisation, vault, routing and reconciliation. The cart handles the storefront and order state; the gateway handles PCI-scope payment capture and clearing.

  2. 02

    How is shopping cart payment processing different from a headless checkout API?

    Shopping cart payment processing is the cart-side view of the same authorisation flow — the plug-in exposes a familiar 'pay now' button on the cart and handles the redirect / webhook cycle. A headless checkout API talks directly to the platform's REST endpoints from the merchant's own back-end. Same platform, different integration shape depending on the merchant's stack.

  3. 03

    Which shopping cart platforms are supported?

    Shopify, WooCommerce, Magento (Adobe Commerce), PrestaShop, OpenCart, BigCommerce and any custom or headless cart via the hosted checkout URL or embedded hosted fields. New plug-ins are added as merchant demand justifies; a hosted redirect covers any cart that isn't natively plugged in yet.

  4. 04

    Does the plug-in change the cart's checkout UI?

    The plug-in respects the cart's checkout UI as far as possible. On Shopify and WooCommerce, the checkout keeps the platform's native look; the payment step surfaces the method list (cards, wallets, BNPL, bank rails) inside the cart's own container. For hosted redirect, the buyer briefly leaves the cart to a branded topropay hosted page and returns after paying.

  5. 05

    How quickly can I switch from my current gateway to topropay?

    For a Shopify or WooCommerce store, the switch is a plug-in install plus a credentials paste — most merchants are live in under a day once onboarding is complete. For Magento or a bespoke cart, integration typically takes 1–3 weeks depending on the merchant's confirmation-page customisation and any downstream fulfilment integrations.

  6. 06

    What about multi-store or multi-brand merchants?

    Multi-store and multi-brand merchants get one merchant record with sub-accounts per store or brand. Each cart plug-in installs against its own sub-account credentials; reconciliation reports roll up per sub-account or across the whole merchant record depending on the finance team's preference.

  7. 07

    Can I keep my existing gateway alongside topropay during migration?

    Yes. Most carts support multiple payment gateways side by side. Merchants typically route a percentage of traffic to topropay during migration to compare approval, cost and dispute outcomes before cutting the remaining volume over. Both gateways surface as separate options on the checkout during that period.

  8. 08

    How does the platform handle guest vs registered checkouts?

    Guest checkouts get a fresh vault token per authorisation. Registered / logged-in buyers can have their card stored against the vault token linked to their account, so returning buyers see saved cards without re-entering details. Storage requires the merchant's card-on-file consent flow on the cart side.

  9. 09

    What happens on refunds, chargebacks and disputes?

    Refunds fire from the cart's order-management UI, calling the platform via webhook or API. The platform handles the reversal against the vault token. Chargebacks and disputes surface in the topropay dashboard with a unified queue and evidence-pack templates per vertical; per-order metadata from the cart is pre-attached to speed representment.

  10. 10

    Does the shopping cart payment gateway support recurring billing?

    Yes. Recurring billing (subscriptions on Shopify, WooCommerce Subscriptions, Magento subscription extensions, etc.) rides the platform's recurring engine with network tokens, account updaters and smart retries. The cart continues to own the subscription state; the platform owns the payment side.

  11. 11

    What methods are surfaced by default in each region?

    By default, the checkout surfaces cards + Apple Pay + Google Pay + Click to Pay globally; SEPA + iDEAL + Bancontact in the eurozone; Bacs in the UK; PIX in Brazil; PayID / OSKO in Australia; ACH in the US. BNPL (Klarna, Afterpay, Affirm) surfaces per market where the merchant enables it.

  12. 12

    Are wallets available on the cart-side plug-ins?

    Yes. Apple Pay, Google Pay and Click to Pay surface on the cart-side checkout through the plug-in. On Shopify, Shop Pay coexists with the other wallets. Enabling wallets is a dashboard toggle rather than a code change.

  13. 13

    How does the platform handle high-cart-abandonment merchants?

    For merchants with high cart abandonment, the platform's smart-routing and cascade features lift the actually-completed authorisation rate materially. Combined with wallet-first sorting and vault tokens for returning buyers, the effective checkout-completion rate can move meaningfully without any cart-side redesign.

  14. 14

    What analytics does the plug-in surface?

    The topropay dashboard shows per-cart analytics: authorisation rate, decline reason mix, method-mix, currency-mix, dispute rates and settlement timing. The data is exportable as CSV or via API for ingestion into the merchant's BI tools.

  15. 15

    Is the shopping cart payment gateway suitable for licensed high-risk merchants?

    Yes, subject to underwriting and the merchant holding the relevant operating licence in their jurisdiction. Licensed gaming, licensed forex brokerage and other compliance-bound verticals are supported on the same cart plug-ins where their licence permits. Unlicensed operators are out of scope regardless of cart platform.

Related

Related on the topropay platform