Payments · 3 min read · 20 August 2026

Payment success is not trusted until the server confirms

Paystack
webhooks
idempotency

Problem

Client-side “payment successful” callbacks can be forged.

Approach

For Zumelia (founder-confirmed Paystack integration): treat browser success as provisional; verify on the server and design webhooks with idempotency. Exact webhook code is not audited in this portfolio repo.

Result

Documented as an engineering decision on the Zumelia case study — labeled from product practice, not a pasted secret.

What I learned

Idempotency keys and signature verification are non-negotiable for payment webhooks.

Related insights

AI · 4 min
Server-side AI without leaking keys
A portfolio assistant needs an LLM, but putting the API key in the browser would expose it to every visitor.
AI · 5 min
Keyword knowledge before vector RAG
Dumping the whole site into one prompt wastes tokens and still hallucinates.

Keep exploring

Ask the grounded assistant about this decision, or open the lab playground.

AI assistant API playground