Payments
Payment systems that reconcile at the end of the month
Taking money is easy. Taking it reliably, refunding it, invoicing it, and proving where it went is the actual work.
I've built payment infrastructure on three different kinds of rails — a card gateway processing over $1M a year, Stripe subscription billing for my own SaaS products, and an open-source cryptocurrency gateway for WooCommerce. Different rails, same hard parts: webhooks that arrive twice, states that get stuck, and edge cases that only show up with real money.
Scope
What I integrate
Stripe billing & subscriptions
Checkout, subscriptions, plan changes, proration, failed-payment recovery, and the webhook handling that keeps your database agreeing with Stripe's.
Meshulam & Israeli gateways
Full Meshulam SDK integration including tokenization, recurring charges, and invoice generation — built into a Strapi backend and running in production.
Custom WooCommerce gateways
When your processor has no plugin, or the one that exists is abandoned. Written to the WooCommerce gateway API properly, so refunds and order states behave.
Cryptocurrency payments
Non-custodial crypto acceptance where funds go straight to the merchant's own wallet. Address derivation, confirmation monitoring, and order reconciliation.
Invoicing & documents
Automated PDF invoice generation, e-signature flows, and the document trail your finance team and auditors will ask for.
Rescue & reconciliation
Payments landing but orders not updating. Duplicate charges. Webhooks silently failing for three weeks. I find it and fix it.
Proof
Systems handling real money
Meshulam + Strapi — $1M+ per year
At One Digital I built an end-to-end payment system on the Meshulam SDK inside a Strapi backend, processing over $1,000,000 a year in transaction volume. That included the payment flow itself, automated PDF invoice generation via Dockerized Puppeteer on Azure Functions, and the reconciliation work that makes finance trust the numbers.
Stripe — billing my own SaaS
GhostChat and Gmailytics run on Stripe subscription billing that I built and operate. There is a particular kind of care you develop when the failed-payment webhook is your own revenue, and that's the standard I bring to client billing systems.
KaspaWoo — open-source crypto gateway
A production Kaspa payment gateway for WooCommerce, open-sourced on GitHub. It's non-custodial: payments derive to the merchant's own wallet, never mine. The address derivation is its own MIT-licensed npm package, kaspa-simple-wallet — watch-only derivation from a KPUB/XPUB, Kaspium-compatible, so the store never holds a private key.
Why the non-custodial detail matters: a store that never holds keys can't lose them. Most payment bugs are really state bugs — and the best fix is usually an architecture where the dangerous state doesn't exist in your system at all.
E-signatures and contract flow
At Hertz Furniture I integrated SignNow for e-signatures on PDF quotes, cutting contract turnaround time by 90%. Payments rarely live alone — they sit next to quotes, contracts, invoices, and a CRM that all need to agree with each other.
Got a payments problem?
New integration, custom gateway, or something that's quietly broken and costing you orders — describe it and I'll tell you what it'll take.