Take payments and subscriptions properly

Stripe for almost everything, wired properly: webhooks that are idempotent because they will be delivered twice, subscription state that survives a failed payment, proration handled rather than ignored, and a reconciliation view that shows when the ledger and the provider disagree.

The problem

You need to charge people — one-off, recurring, metered or all three — and the money path is the one part that absolutely cannot be approximately right.

How we approach it

Stripe for almost everything, wired properly: webhooks that are idempotent because they will be delivered twice, subscription state that survives a failed payment, proration handled rather than ignored, and a reconciliation view that shows when the ledger and the provider disagree.

What changes

Payments that work, a billing state you can audit, and dunning that recovers failed cards instead of silently losing the customer.

The service this falls under

Software development

Web apps, SaaS platforms, APIs and the systems underneath them.

Six to twenty weeks depending on scope.

Industries where this comes up

Last reviewed · Site changelog