Merchant API Reference
VendStack calls your HTTPS endpoints to list products and complete purchases. Everything is POST with a JSON body, and every request is signed so you can confirm it came from us.
Don't want to write this by hand? A starter kit — one drop-in file for Laravel, PHP, Node.js or ASP.NET Core — implements every endpoint below, verifies the signature, and makes
/vendidempotent. You supply only your wallet and vending logic.
You configure this once, on the dashboard's Merchant API card: a single base URL and a signing secret. Every channel — WhatsApp, USSD and any we add later — uses this same API, so you integrate once and turn channels on as you go. We call paths under your base URL, e.g. base https://api.yourbank.com/vendo → https://api.yourbank.com/vendo/vend.
You implement only what your products need
| Product | /billers |
/packages |
/validate |
/vend |
|---|---|---|---|---|
| Airtime | – | – | – | ✅ |
| Data | – | ✅ | – | ✅ |
| Cable | ✅ | ✅ | ✅ | ✅ |
| Power | ✅ | – | ✅ | ✅ |
| Betting | ✅ | – | ✅ | ✅ |
So airtime-only merchants implement one endpoint (/vend); a full-service merchant implements four. A few more are optional: /status (reconcile a purchase after a timeout — recommended for reliability), /balance (customers check their balance — every wallet, e.g. main and commission — from the Check Balance menu option or by asking the assistant, and see it before they pay), /wallet-transfer (lets customers move money between their own wallets, e.g. commission → main, by asking the assistant), /accounts (powers the Fund Wallet option — VendStack fetches the customer's bank account and shows it so they can top up), /authenticate (checks up front whether a number has an account, so an unrecognized customer is sent straight to sign-up instead of after a failed purchase), and /register (lets a new customer create an account in chat when their number isn't recognized).