Checkout and webhooks
$250
4 days · 1 revision
One-time payments through Stripe Checkout.
- Stripe Checkout for one-time payments
- Paid and failed payment webhooks
- Webhooks run as queued jobs with logs
- Short handover guide
Fixed-price project
I add Stripe payments, subscriptions and webhooks to a Laravel app, so your records match what Stripe says. It fits teams that sell online or by plan and need billing they can trust, from $250 in 4 days.
Who it is for
Signs
Scope
A customer can close the tab right after paying. So I mark an order as paid when Stripe's webhook says so, not when the browser comes back. I built a marketplace this way: paid and voided invoices arrive as webhook events and run through queued jobs.
I check the Stripe-Signature header with your endpoint secret, using the raw request body. Stripe can send the same event more than once, so I record the event IDs and skip repeats. Stripe does not promise any order, so handlers do not depend on it. When one needs the latest state, it asks the Stripe API for the current object.
The endpoint answers with a 2xx code quickly and hands the work to a queue job. Stripe keeps retrying for up to three days in live mode, and I log each failed job so it can be retried.
I use Laravel Cashier when it fits your app. It covers subscriptions, coupons and proration. Customers can update their card, see invoices and cancel from the billing portal that Stripe hosts, so you do not build those screens.
A failed payment and a refund are events too. Stripe tells your app, and your records change. The Full billing system package also sends a failed-payment email to the customer and adds an admin view.
I build in Stripe test mode first. Your endpoint listens only to the events your flow needs, not to every event Stripe can send. You get the code in your repository, a list of the events it handles and a short handover guide.
Packages
Fixed price in US dollars. Each package lists what is included.
$250
4 days · 1 revision
One-time payments through Stripe Checkout.
$600
8 days · 2 revisions
Recurring plans with a customer billing portal.
$1,200
15 days · 3 revisions
Plans with coupons, proration, refunds and an admin view.
Process
Step 1
We write down what customers buy, how often they pay and what each Stripe event should change in your app. This removes the guessing before I build.
Step 2
I build against your Stripe test mode. I send test events to my local endpoint with the Stripe CLI, so I never need your live keys during the build.
Step 3
I send the same event twice, send events in the wrong order, fail a card and refund a payment. After each one I check that your records are still right.
Step 4
The code goes into your repository with the list of handled events and a short guide on where to look when a payment looks wrong. Going live means adding your live keys and a live webhook secret. I walk you through it.
Proof
Case study
This is a multi-sided marketplace SaaS that connects service providers with the clients who hire them, and handles the money between them. I...
Article
FAQ
Yes. Stripe can send the same event more than once, and it does not promise that events arrive in order. I record the IDs of events I have processed and skip repeats. The handlers do not depend on order. When one needs the latest state, it asks the Stripe API for the current object.
Stripe tries again for up to three days in live mode, with longer waits between tries. When your server is back, the events arrive and the queue works through them. You can also resend an event from the Stripe Dashboard or the Stripe CLI if you ever need to replay one.
I need a Stripe account with test mode keys, the products and prices you plan to sell, and access to your Laravel code and a staging site. I build in test mode, so I do not need your live keys. You add them yourself when we go live.
No. Card details are entered on Stripe Checkout or in Stripe's own payment fields, so the numbers go to Stripe. Your app stores Stripe IDs, such as the customer and subscription IDs, and the status of each payment. I keep Stripe keys in your environment settings, never in the code.
Yes, from the Subscriptions and billing package up. I connect your app to the Stripe customer portal, a page that Stripe hosts. Depending on what you switch on, customers can update their card, see invoices, and change or cancel a plan. You do not build those screens.
Not in these three packages. Payouts between buyers, a platform and sellers are a bigger job with their own rules. I led development on a marketplace platform built on Stripe Connect, so I can scope it. Send a quote request and tell me how money should move.
I use it when it fits your app. Cashier supports subscriptions, the billing portal, coupons and proration. If your billing rules are far from what Cashier expects, I will tell you before I start, and we will pick a simpler route together.
The packages do not cover tax setup, Stripe account approval, a custom checkout design or sending invoices to your accounting system. They also do not cover marketplace payouts. If you need any of these, tell me before we start, and I will quote it on its own.
If your work does not fit these packages, tell me what you need and I will reply with a plan.
More projects
From $300
Contacts, companies and deals kept in step between Laravel and HubSpot.
From $450
Customers, items and orders kept in agreement between Laravel and your ERP.
From $350
Upgrade an old Laravel app step by step, with login, payments and queues checked.