Stripe Connect + Driving School Payments

When we started working on the DSP platform, the original goal sounded simple.

Students should be able to book driving lessons and pay online. Instructors should receive their money, and Stripe would handle the rest.

Simple enough.

But once we started looking at how the business actually worked, we realized that accepting payments was only a small part of the problem.

The real challenge was deciding what should happen after someone clicks "Book Lesson".

Because money, schedules, refunds, instructors, and the platform itself all had to work together. And that's where things got interesting.

Some lessons are days or even weeks away.

Charging students immediately for a lesson that might still be cancelled didn't feel right.

But waiting until the last moment created another problem.

What if the card declined? What if the bank required 3D Secure authentication? What if the student simply disappeared?

Suddenly, "Take payment with Stripe" became much more complicated. We needed a better approach.

Some cards required 3D Secure. Others failed due to insufficient funds. Students sometimes abandoned checkout.

Instead of treating failures as errors, we treated them as part of the workflow.

Users could resume unfinished payments. Retry failed charges. Complete authentication when required.

And once lessons had passed, payment flows became locked.

Getting money from students was only half the story.

The platform keeps a commission on every lesson. Money couldn't simply pass through. And instructors shouldn't be paid immediately because cancellations and refunds still existed.

So payouts became tied to lesson completion. Only completed lessons became eligible.

An automated payout system continuously looked for completed lessons, successful payments, and unpaid lessons.

Then Stripe Connect transferred instructor shares while retaining platform commissions.

Refunds were not button clicks. They were business rules.

Completed lessons couldn't be refunded. Paid-out lessons couldn't be refunded. Duplicate refunds were blocked.

Admins couldn't accidentally break accounting. The system protected itself.

Eventually, we realized we weren't building Stripe features. We were building trust.

Students trusted they wouldn't be charged unfairly. Instructors trusted they'd get paid.

The platform trusted commissions and payouts would always remain balanced.

Stripe became the engine. Business rules became the real product.