Connect Stripe
without holes in your revenue.
Taking a payment is the easy part. The hard part is everything after: a webhook that arrives twice, a trial that ends, a failed direct debit, a customer who cancels and keeps access anyway. That is where the holes are that you find months later.
Where payment integrations break.
Access hangs off the checkout
Someone pays, gets access, and that access stays. Even when the payment later fails or the subscription is cancelled.
Webhooks are not verified
Without signature checking anyone can send a 'payment succeeded' to your endpoint. Without idempotency you book the same payment twice.
Subscription changes do not add up
Upgrading mid-month, downgrading, pausing: if you recalculate that yourself instead of letting Stripe do it, your bookkeeping drifts.
VAT is an assumption
Business or consumer, inside or outside the EU, with or without a VAT number. Done by hand, that does not stay right for long.
Failed payments are silent
No reminder, no retry, no email. The customer does not notice and you only see revenue drop.
Only tested in test mode
Test cards always do what you want. Real 3D Secure, declined cards and chargebacks do not.
Payments that survive the edge cases.
Work out what you sell
One-off, subscription, usage-based or paying out to third parties. That decides the model, and changing the model afterwards is the most expensive route.
Stripe as the source of truth
Checkout or Elements for paying, and Stripe tracking the status. Your database follows Stripe, not the other way around.
Webhooks that hold up
Signature checking, idempotency so duplicate events do not become duplicate bookings, and a retry if your side is briefly down.
The whole lifecycle
Trial, upgrade, downgrade, cancellation, failed payment with reminder emails, refunds and the customer portal where they handle it themselves.
- ✓Access that stops when the paying stops
- ✓Webhooks with signatures and idempotency
- ✓Subscriptions with trial, upgrade and cancellation
- ✓Invoices and VAT handled automatically
- ✓Tested with real payments, not only test cards
The first opinion costs you nothing: send me the repository or a link and I will tell you honestly whether building on beats starting over.
Clients rate me
5 stars on average.
Translated from the Dutch originals on Google.
I am Bas Voets. Since 2021 I have been building websites, client portals and business software for small and mid-sized companies, from Hazerswoude-Dorp in the Netherlands. From first call to launch you talk to me, not to an account manager.
What does a Stripe integration cost?
Stripe or Mollie?
Can you build it into an app I made myself?
How long does it take?
Tell me what you
want to build.
A half-hour call. You get an honest answer about what it costs, how long it takes and whether building it is smart at all.
Have your current site or tool scanned
You do not have to want to buy anything yet. Send what you have and I will tell you honestly what I would keep, what I would replace and whether that is worth the investment. Including when the answer is that you are better off doing nothing.
The scan is a first impression, not a security audit.
- 01Send a link to your site, your tool or your repository
- 02I look at speed, structure, data and security
- 03Usually within two working days you hear what I would replace and what that costs