Payment platforms with compliance designed in.

On Purpose Payment the hard questions were about how money moves: customers link a bank through Plaid, pay a store by scanning its QR code, and every order splits automatically between the store and a charity the customer chose. Those rules live in one API that the customer app, the merchant portal and the admin console all share, so a payment, its charity share and the points it earns are recorded together.

That is the lesson we take into every financial build: decide how money is split, stored and shown before the first screen, and keep that logic in one place. A payments product whose rules are scattered across its screens is a prototype, however good it looks.

EIGHTClouds is an in house product built for a group company. Each investor sees their portfolio, the documents attached to each investment and the news that affects them, in a Laravel portal and a Flutter app that mirrors it. The team manages offerings, investors, agents, commissions, banks and brands from an admin, and a Next.js marketing site sits in front.

Running the product ourselves taught us what a portal is for. The dashboard is glanced at; the documents are what an investor downloads before a meeting with their accountant. Three surfaces, portal, admin and app, share one source of truth, so a document uploaded by the team is the document the investor opens on a phone.

Most of our payment work happens inside marketplaces, stores and subscription apps rather than in a standalone fintech product. Skills Sync uses Stripe setup intents so a customer saves a card once and rebooks without re-entering it. Teachers Lunch confirms card payments through webhooks and sends SMS and push updates as the order moves. Edsidera takes parent payments through Stripe on its own portal. Pioneer Auctions settles bids through PayTabs in English and Arabic.

The pattern is the same in every case: the payment provider confirms through a webhook, the API records the result, and the product never trusts a client's word that a payment happened. Subscriptions, plans and coupons live in the API, as on My Places and Brilliant Teaching, so billing does not run on support tickets.

On EIGHTClouds the public portal is the smaller half of the product. The admin is where the team creates offerings, onboards investors and agents, records commissions, manages banks and brands and uploads the documents that investors will later download. If that console is slow or incomplete, the finance team falls back to spreadsheets and the portal quietly stops being the source of truth.

So the admin is scoped with the same care as the investor facing screens, with roles that match how the team actually divides the work and a trail on every change. The same rule applied to Purpose Payment, whose admin console runs customers, merchants, charities, payouts and reports.