Multi-tenant platforms, marketplaces, B2B commerce, regulated e-commerce and native mobile, instrumented from the advertising click to the settled payment. Payments architecture is the specialism we go deepest on. Remote-first, working with clients across the UK and EU.
Across the startup boom, the blockchain cycle and now AI. The tools change. The parts that break do not.
Ledgers that prove themselves on a schedule. Multi-gateway routing, sub-merchant settlement, reconciliation.
Allocation you can prove rather than promise. Verification, payouts, live liability reporting.
Patient data under HIPAA and UK GDPR. Prescriptions, prescriber verification, separate US and EU regions.
Quote-to-cash, negotiated pricing, white-label buyer portals. Price is never a column.
Stock as a movement ledger, not a number you overwrite. Pick pack ship, bonded goods, integrations.
Bonded and duty-paid stock on one catalogue. Vintage structure, trade and consumer pricing.
Four short tools covering the things people usually pay for a first meeting to find out. Nothing stored, no sign-up, and the answer is yours either way.
The one below is the most asked. If you collect payments on behalf of others, card scheme enforcement has probably changed what is acceptable since you built it, and switching provider does not help because every mainstream acquirer applies the same test.
Five questions. Which structure are you actually running?
1. One merchant account, paying out to multiple sellers?
2. Do those sellers set their own prices?
3. Whose name is on the cardholder statement?
4. Who owns refunds and chargebacks?
5. Elevated-risk category? Pharma, gambling, travel, adult, CBD, high-value goods.
Indicative only. It reflects how acquirers weight pricing control and cardholder perception, not a formal assessment.
Tokens, webhook semantics and schema vocabulary decide whether a switch is weeks or a quarter.
Volume, structure and category. Providers assess on arithmetic, not on how good the business is.
Setup time, suite speed, enforced conventions, and how many people understand the billing code.
The check above on its own page, with the reasoning behind every result.
Audit, build, MVP, or embedded. All scoped before they start.
Conventions enforced by machinery, not by discipline. Discipline leaves when the contractor does.
Our full working standard, the positions we hold, and what runs in production
Payments infrastructure, regulated data, testing discipline, and systems that outlive the people who wrote them.
| Your review queue is the bottleneck now | Median code review time up 441% while throughput rose 34%. Agent-authored pull requests carry more debt and get approved more readily, because they read well. |
| The accessibility deadline most teams missed | In force since June 2025, applies to UK businesses selling to EU consumers, penalties to 100k euros. First cases filed in France last November. |
| Why your merchant ID was withdrawn | The three structures acquirers accept, and what each one costs. |
| Your gateway probably owns your customers' cards | Visa and Mastercard issue tokens directly. Whether they are yours or your provider's comes down to one field most merchants have never looked at. |
| Cards, open banking or crypto | Cost, settlement, reversals and friction compared plainly. Open banking is excellent on mobile and awkward on desktop. |