omniway.online · v1.0.0

One platform that lets any merchant accept InnBucks — online or at the till.

Omni Way is the unified financial layer for InnBucks payments. A school collecting fees, a hospital billing patients, a tuck shop at the corner, a fleet operator, an online store — they all integrate the same way: one API, one redirect, one ledger. All business logic lives in the platform backend; your frontend never talks to InnBucks directly.

🚀 Get started → 🛒 One-redirect checkout API reference

USD & ZWG Sandbox built in One redirect to integrate REST + webhooks

How a payment flows — end to end

Whatever you sell, the loop is the same five steps. The platform handles every InnBucks rule for you — code expiry, inquiry throttling, settlement, reconciliation.

Create a payment

POST /v1/payments with the amount in cents. You get a code, QR, deep link and a hosted checkout_url.

→

Customer pays

InnBucks app, QR scan, deep link, or USSD *569# — at the counter or from their couch.

→

We confirm

The platform polls InnBucks within their rules and flips the payment to paid.

→

You get notified

A signed webhook (payment.paid) hits your server, or you poll GET /v1/payments/:id.

→

Money settles

Your ledger balance grows. Pay out to your own InnBucks wallet any time with POST /v1/payouts.

◆

Where the business logic lives

Your storefront, school portal or till screen is just a surface. Amounts, fees, settlement, the InnBucks gateway rules, balances and statements all live in the platform backend. That is why a frontend integration is one redirect — and why every product below shares one consistent ledger.

The products

💳

Payments

InnBucks payment codes with QR, deep link and USSD — the core primitive every other product builds on. Start here.

🛒

Hosted Checkout

An InnBucks-branded payment page we host. Integrate with one redirect, or pop it over your page with pos.js.

🧾

Sales, Stock & Till

The full POS layer: catalog, barcode scanning, stock control, cash + InnBucks sales — with a bundled till app at /till.

🔔

Webhooks & Events

Signed push notifications for paid, expired, payout and cash-out events — plus a polling fallback.

💸

Payouts & Balance

Your running balance, the append-only ledger behind it, and self-service payouts to your verified InnBucks wallet.

🏧

Agent Operations

Act as a cash point: withdrawal codes for customer cash-out and instant change-to-wallet up to USD 5.00.

📱

Utility Payments

Sell airtime and utility products from your balance and earn the provider commissions.

📊

Merchant Dashboard

Balances, payments, payouts, CSV statements, API keys and webhooks — no code required.

🧩

Integration Recipes

End-to-end blueprints per merchant type: school, hospital, tuck shop, fleet, online store.

Test mode and live mode

Every account has two parallel worlds, switched purely by the API key you use:

	`sk_test_…` — sandbox	`sk_live_…` — production
Money	Simulated. Payments auto-settle ~18 s after creation.	Real InnBucks money against the live gateway.
Data	Fully separate payments, ledger and balance.	Fully separate payments, ledger and balance.
Behaviour	Identical API shapes, codes, QR, checkout and webhooks.	Identical — switching is changing one key.

Build your whole integration in test mode first — see Sandbox, UAT & Go-Live.

Sixty seconds to your first payment

curl https://omniway.online/v1/payments \
  -H "Authorization: Bearer sk_test_..." \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
    "amount_cents": 1050,
    "currency": "USD",
    "merchant_ref": "order-42",
    "success_url": "https://yourshop.example/thanks"
  }'

The response carries everything: the 9-digit code, a qr_png_data_url, the deep_link, USSD instructions and a hosted checkout_url. Redirect the customer to checkout_url and you are done — the page shows InnBucks branding, counts down the 10-minute code window, detects payment and sends them back to your success_url.

✦

Amounts are always integer cents

1050 means USD 10.50. Supported currencies are USD and ZWG. Every money-moving POST requires an Idempotency-Key header so retries are always safe — see Errors & Idempotency.

Explore the docs

🚀