The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
Taking payments with Stripe? The money moving is only half the story. The other half arrives later as webhooks, and handling them badly means customers who paid but have no access, or orders processed twice.
Six rules I follow on every Laravel build:
Verify the Stripe-Signature header against the raw body
Exempt only the webhook route from CSRF
Respond fast, then process in a queued job
Deduplicate on the event ID
Never assume events arrive in order
Make every handler safe to run twice
Bonus: store the raw event before processing it. You get an audit trail and can replay after a bug fix instead of asking Stripe to resend.
What's the nastiest webhook bug you've hit?
aqibjavaid.site
Stripe Webhooks in Laravel: A Safe Setup - Aqib Javaid
Stripe webhook handling in Laravel: verify signatures, respond fast, deduplicate by event ID, handle out-of-order events and replay failures safely.
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
Messy books in. Clean books out. 📊
This is a simple before/after of a bank reconciliation (sample figures, no client data). Before: a duplicate payment and a missing entry left the books out by KES 13,650. After: both fixed, and the difference is KES 0.00.
This is the kind of work I do for small businesses every month:
✅ Bank and account reconciliations
✅ Accounts payable and receivable
✅ Invoice and payment processing
✅ Month-end support and financial reporting
This is a great example of how proper bookkeeping makes a real difference! Clean reconciliations lead to more accurate records and better financial decisions. 👏📊
Title: Why 80% of your new email subscribers never buy or donate
Most brands work so hard on top of funnel traffic. You run ads, post on social media, and get people to sign up for your newsletter.
Then you send them a generic welcome email with a discount code and complete silence for two weeks.
Here is what happens when you do that:
Your subscribers forget who you are within 48 hours
Your open rates drop on every future broadcast
Readers feel like just another metric on your list instead of an insider
A generic confirmation email does not build trust. A strategic 3-part sequence tells your core origin story, sets clear expectations, and guides new subscribers toward their first purchase or donation while their interest is at its peak.
If your welcome flow feels dry or non-existent, I write 3-part custom on boarding sequences that turn cold signups into warm, loyal community members.
Drop a comment or check out my fixed-scope service link on my profile to get your welcome sequence updated this week.
Once a campaign email sends, every mistake in it is in every inbox on your list.
A dead link. A code that ended last week. A subject line that says 20% off when the code only gives 15%.
I built an n8n workflow that checks Klaviyo campaigns before they go out:
• Every hour it finds the campaigns scheduled for the next 24 hours, and checks each A/B version on its own.
• It tests the links and images in the email.
• Claude lists every code, discount and date it finds, with the exact words.
• Plain code checks those against a Google Sheet of your live offers and the send date. Anything Claude quotes that is not in the email is thrown out.
• Slack gets one message per email: ready, ready with notes, or what to fix. If a problem is still there close to send time, you get one reminder.
It only reads Klaviyo. It never edits, cancels or sends a campaign, so the fix stays in your hands.
If you send Klaviyo campaigns for your store or for clients, send me a message and I will set this up for you.
