Payments Engineering
Build a payments service with two providers behind one interface, an append-only ledger, safe webhooks, refunds, daily reconciliation and receipts an auditor can trace.
- About 6 weeks
- Intermediate
- About 10 hours a week
- Self-paced, text-based
- Code checks and AI feedback
One payment. Every lesson unlocks at once.
Start this courseStart today. 14-day full refund.
- Pace
- Yours, about 6 weeks
- Level
- Intermediate
- You build
- One deep project
- Lessons
- 18 text lessons, about 8 hours of reading
- Feedback
- Code checks every project, then AI
{about this course}
What it is
Taking a payment is the easy part. The work starts afterwards: a webhook arrives twice, a refund is partial, a payout is smaller than the day's sales, and an accountant asks why. This course teaches the engineering that makes those questions answerable. It is for developers who already build web applications and have not specialised in payments.
You build one project over about six weeks at ten hours a week: the payments service of a cooking school, in TypeScript and PostgreSQL. It records every movement of money in an append-only ledger in whole minor units, takes payments through Stripe and PayPal behind one interface, processes webhooks once however often they arrive, issues full and partial refunds, tracks disputes, reconciles against each provider every day and issues numbered receipts that trace back to the ledger. The last lesson adds a local payment method behind the same interface, with honest notes on where it is available.
Everything runs in the providers' sandboxes, so you need no registered business and no real money. Each module ends in one milestone of the project that you can hand in on its own. Code checks each milestone, and AI tells you what is solid and what to improve first.
{outcomes}
By the end you can
- Trace a card payment from authorisation to payout, and account for every fee, refund and dispute on the way
- Model money in PostgreSQL with integer minor units, an append-only double-entry ledger and payment states the database enforces
- Integrate Stripe and PayPal behind one TypeScript interface, so the rest of your code does not care which provider took the money
- Verify, deduplicate and process webhooks so that duplicate, late and out-of-order events cannot corrupt your records
- Issue full and partial refunds and track disputes without the ledger and the provider drifting apart
- Reconcile your ledger against each provider every day, and issue numbered receipts and credit notes that trace back to ledger entries
- Add a local payment method behind the same interface, and say plainly where it is available and where it is not
{projects}
The one project you build
Project 1: A payments service for a cooking school
A TypeScript and PostgreSQL service for Rempah Cooking School in George Town, Malaysia. It takes payments through Stripe and PayPal behind one interface, records every movement in an append-only ledger, handles webhooks and refunds, tracks disputes, reconciles against both providers every day and issues numbered receipts.
- TypeScript
- Node.js
- Express
- PostgreSQL
- Stripe
- PayPal
- pg-boss
- pdf-lib
{syllabus}
Everything you will read and build
4 modules · 18 lessons · 4 projects
How the school and this short course work, the six-step method and the debugging loop, and the accounts and sandboxes you will use while you learn in public.
- 15 minHow Leet School works
You can describe the loop of a lesson, a week and a milestone, and plan your own weeks of study.
- 20 minThe method, debugging and asking for help
You can use the six-step method on a payments problem with no code, follow the debugging loop, and ask a question that includes the provider's request id.
- 20 minYour accounts and learning in public
You can set up the accounts and sandboxes the course uses, choose a stand-in where a provider does not serve you, and share what you learn without leaking a secret.
- Weekly check and weekly article
A few questions answered in your own words, marked at once, and one article about the week.
- Set-up projectYour learning home
You publish a profile page on GitHub that says who you are, what you are building and which sandboxes you use, and you write your first public post.
{is this for you}
Who Payments Engineering is for
It suits you if
- Developers who have added a checkout to a product and now own what happens after the customer pays
- Freelancers and agency developers who build shops, booking systems or billing for clients
- Backend engineers joining a payments, billing or finance team who want the vocabulary and the patterns
- Technical founders who take payments online and want records that match the bank statement
Pick something else if
- People new to programming. You need to be comfortable with TypeScript, HTTP and SQL before this course makes sense
- Anyone who only needs a hosted payment link or a no-code checkout. Those work well and do not need this course
- Anyone looking for tax, accounting or legal advice. The course teaches the engineering and says where you need an accountant
{before you start}
What you need
- You write TypeScript or JavaScript and can build a small HTTP API with Node.js
- You can write SQL joins and transactions, and have used PostgreSQL or another relational database
- You are comfortable with Git, GitHub and the command line
- Node.js 26 and PostgreSQL 17 or newer on your computer. Both are free
- Free sandbox access to Stripe and PayPal where they serve you. If one does not, the course gives you a stand-in for it
{tools}
Tools you will use
- TypeScript
- Node.js
- Express
- Zod
- PostgreSQL
- node-postgres
- Stripe
- Stripe CLI
- PayPal
- pg-boss
- pdf-lib
- Git
Start Payments Engineering today.
$250. No application. Change your mind within 14 days for a full refund.