Example projects

Three places hold runnable Wajub code, and they answer different questions. The cookbook shows a complete feature in a real framework, the CLI scaffolds a webhook receiver on your disk, and each SDK repository carries a minimal script that proves the install worked.

Complete features, in a framework

The cookbook recipes are full walkthroughs. Each one is a working integration you can read end to end, with the server call, the browser or app half, and the webhook that confirms.

A webhook receiver, scaffolded

The CLI writes a working receiver into a directory of your choice. It has no dependency beyond Node, and it verifies the signature the same way the SDKs do, which makes it useful for reading as well as for running.

wajub samples webhooks my-receiver
node my-receiver/server.mjs

# in a second terminal
wajub listen --forward-to localhost:3000/webhooks
wajub trigger payment.succeeded

wajub samples --list prints what is available. Today that is the webhook receiver, and the list is where new ones appear.

The minimal call, per language

Two SDK repositories ship an examples/ folder holding one script. It creates a payment and prints the URL, which is exactly enough to prove your key, your network and your install.

Each reads WAJUB_API_KEY from the environment. Export a sandbox key first and the payment it creates is harmless.

Building your own starting point

If you are setting up a project rather than reading one, the shortest honest path is three steps.

Keep Konsole open while you do. It shows every request and every webhook delivery as they happen, which turns most debugging into reading rather than guessing.