Skip to content

Cookbook

One finished implementation per stack, for the problems the guides describe.

A guide explains a problem and the shape of its solution, in whatever language you read. A recipe is the other half: one finished implementation, in one stack, with the file names and the imports and the parts nobody writes down.

Pick the recipe whose stack matches yours. If none of them does, read the guide behind it: the reasoning transfers, only the syntax does not.

The five recipes

RecipeStackWhat it actually shows
Next.js checkoutNext.js App Router, TypeScriptA Server Action that charges a price the client cannot choose
Express webhook handlerExpress, TypeScriptAn endpoint that survives retries, replays and malformed bodies
Laravel recurring billingLaravel 11, PHPSubscriptions built from plain payments, with dunning
Django marketplaceDjango REST Framework, PythonA Sync marketplace where money lands on the vendor, not on you
React Native Mobile MoneyExpo or bare React NativeA mobile checkout with no key in the bundle

What every recipe assumes

None of them repeats the basics. Each one assumes you already have an account, sandbox keys and the SDK installed, and that you have read the guide it implements.

Each one also follows the same two rules, because every integration that works does.

The server decides the price. An amount that arrives from a browser or a phone is a suggestion, not an instruction. Every recipe reads the amount from its own database.

The webhook decides the outcome. A return page, a deep link or an SDK callback tells you what the client believes. Only a verified webhook tells you what happened.

What did you think of this content?