13-status-matrix

I shipped a Python SDK for a payment gateway. The page I'm most proud of is a status table.

Most SDK READMEs say "production ready" — a marketing word.
Mine shows a matrix, row by row:

→ Unit — respx-mocked, asserting the exact body sent on the wire
→ Sandbox — integration against the gateway's sandbox
→ Prod — real money, exact date (2026-05-31), verified back via webhook

Six payment methods. Two API generations. Three auth methods.
Each row earned independently.

The table also tells the uncomfortable truths:

→ Apple Pay sandbox returns 400 on merchant validation (reported, not fixed on their side yet).
→ Multibanco refund settles asynchronously via a separate webhook, hours later.
→ Pay By Link expires silently — no webhook, just a generic 404.

Each of these is now a normalized type or a documented quirk in the SDK.

If your README has a "Production Ready ✅" badge and nothing else, you're asking your users to trust a sticker.
A matrix gives them something they can audit.

What's the most honest thing in your docs?

Status matrix live: eupago.bilouro.com

P.S. New tech post every Wednesday.

#OpenSource #Python #SoftwareArchitecture