eCommerce & Payments

How eCommerce & Payments actually runs.

1. 01

   Scope

   Map the products, the rates, the markets, the tax regime. The architecture call here decides whether the next two years feel like growth or whack-a-mole.

2. 02

   Integrate

   Pick the PSP (Stripe, Adyen, Mollie, mix), wire it in once, then write the rest of the system against the clean interface — never against PSP quirks.

3. 03

   Stress-test

   Run the unhappy paths: declines, partial captures, refunds, disputes, fraud signals, EU 3DS2, VAT boundaries. Production sees fewer surprises this way.

4. 04

   Tune

   Funnel analytics on day one — not a sprint after launch. The first month is reading the data and fixing the actual leaks, not the assumed ones.

Before you ask

• Q·01 Shopify, Centra, custom — what should we use? +

  Depends on the product and the team. Off-the-shelf is cheaper to start; custom storefront on a hosted backend (Shopify Hydrogen / Saleor / Medusa) wins when the brand experience is the product. We'll recommend based on margin, scale and editorial weight.

• Q·02 Do you handle subscriptions? +

  Yes — Stripe Billing or Adyen Subscription, with the dunning, plan changes and proration logic that off-the- shelf gets only 80 % right.

• Q·03 What about marketplaces (multi-seller)? +

  We've shipped marketplace flows on Stripe Connect and Adyen for Platforms — KYC, payouts, split capture. Not every team needs the platform model; we'll tell you if you do.

• Q·04 Can you migrate us off the current shop? +

  Yes — usually a phased cutover by SKU group or market, with the old shop and the new running side-by-side until the data and traffic are both safe to switch.

• Q·05 How do you handle PCI? +

  Tokenised end-to-end. We use hosted fields / Stripe Elements / Adyen Web Components so card data never touches your servers. PCI scope stays small by design.