nombaone/nombaone

Managed recurring billing, built for how Nigeria pays. # nomba one subscriptions and recurring billing for nigeria, built on nomba. merchants sell plans. we bill the cards, chase the failures, keep the ledger, and pay them out. --- tl;dr (skip to section #7) --- ## for judges: verify the whole thing in ~10 minutes everything below is live. no setup, no install. | what | where | |---|---| | website | nombaone.xyz | | docs | docs.nombaone.xyz | | merchant console | console.nombaone.xyz | | api (live) | api.nombaone.xyz | | api (sandbox) | sandbox.api.nombaone.xyz | | a real merchant using us | recipe-1.nombaone.xyz | **console login** ``` email: emekapraiseo@gmail.com password: HHMyLiG3uMncxLw ``` --- ### 1. see the product (1 min) go to nombaone.xyz then docs.nombaone.xyz. every page is real, no placeholders. the error reference and event catalog are generated from the code, so they cannot drift. --- ### 2. sign in to the console (1 min) go to console.nombaone.xyz and use the credentials above. top right, there is a **sandbox / live** toggle. that is the whole environment model: one deployment, two account modes, decided by the api key prefix (`nbo_sandbox_` / `nbo_live_`). **start in sandbox.** no real money moves there. --- ### 3. watch a subscription bill itself, in real time (10 min, mostly waiting) this is the part worth your time. 1. **plans → new plan** 2. name it anything, price it anything 3. for the cadence, pick **every 10 minutes** that is not a demo mode. `interval: minute, intervalCount: 10` is a first class cadence, identical to monthly in every code path. it exists so a developer can watch billing happen instead of waiting a month. 4. **developers → test**, add a test card with behavior **success** 5. **subscriptions → new subscription**, pick your plan, that customer, that card 6. now wait come back in ~10 minutes. it billed itself again. **invoices** shows two paid invoices about 10 minutes apart, a …