Rihuum Commerce Standard
Payment infrastructure with activation kept separate from implementation.
Rihuum maintains a shared product register, payment-intent ledger, provider contracts and verification controls. Every live destination remains inactive until merchant, callback, settlement and acceptance evidence is complete.
All providers report live: false. RAHIS uses Paystack test mode for controlled sandbox commissioning only.
Open readiness API →- Live collection
- Inactive
- RAHIS payment mode
- Paystack sandbox
- Ledger
- Durable payment intents
- Settlement owner
- Finance acceptance
01 / Provider register
Supported contracts with their real activation gates.
Implemented means server adapter and control contract—not merchant activation, valid destination, settlement, certification or live processing.
| Provider | Implementation | Supported methods | Activation evidence |
|---|---|---|---|
| Paystack Paystack | ImplementedLive: false | Cards · Bank · Bank transfer · USSD · QR · Mobile money · Apple Pay · Direct debit | Verified merchant account, protected keys, webhooks and settlement acceptance |
| Squad / SquadCo GTCO | ImplementedLive: false | Cards · Transfer · USSD · Bank debit · Recurring payment | Verified merchant KYC, protected keys, webhooks and settlement acceptance |
| Flutterwave Flutterwave | ImplementedLive: false | Cards · Bank transfer · USSD · Mobile money · Regional methods · Supported device wallets | Verified merchant account, protected keys, webhook secret and settlement acceptance |
| GlobalPay by Zenith Bank PLC Zenith Bank PLC | Contract-controlledLive: false | Cards · Hosted payment · Bank-approved channels | Zenith merchant onboarding, bank-issued API contract, sandbox, credentials and production acceptance |
| Rihuum direct bank transfer Rihuum Intercontinental Limited | ImplementedLive: false | GTBank · Zenith Bank · Titan Trust Bank · Moniepoint MFB | Finance-verified account name, number, currency, reference and reconciliation owner for each account |
| Cryptocurrency wallets Rihuum Intercontinental Limited | ImplementedLive: false | BTC · ETH · USDT · USDC · Approved networks | Verified wallet, asset/network, pricing, expiry, confirmations, reconciliation, accounting and compliance approval |
02 / Verification path
A webhook is evidence—not final proof.
Fulfilment can proceed only after signature validation, independent provider verification and an exact transaction match.
- Intent
- Create a durable, idempotent payment intent for an allowlisted Rihuum product, exact amount and currency.
- Provider
- Use protected server credentials and a provider-hosted or contract-approved payment path.
- Event
- Verify the provider signature and reject malformed or repeated webhook events.
- Query
- Re-query the provider server-to-server and compare reference, amount, currency and success state.
- Accept
- Reconcile settlement, exceptions, refunds and disputes under accountable finance ownership.
03 / Shared API contract
Product-scoped and centrally governed.
Every product uses the same allowlisted contract so provider logic, payment truth and audit controls do not diverge by website.
| GET | /api/productsRegistered products and deployment evidence. |
|---|---|
| GET | /api/payments/providersCurrent configuration and live-status response. |
| POST | /api/payments/initializeAllowlisted, idempotent payment-intent creation. |
| GET | /api/payments/intents/{reference}Public-safe intent state. |
| POST | /api/payments/webhooks/{provider}Signed provider event intake. |
04 / Destination control
No account or wallet is guessed or published.
Payment destinations and credentials remain protected configuration owned by authorised finance and technical operators.
- No bank account number is accepted from ordinary visitor input.
- No cryptocurrency wallet is activated without asset, network and ownership verification.
- No provider secret enters public source or a browser response.
- No successful screen or webhook alone marks a ledger item settled.
Commerce commissioning
Activate only after the destination and settlement path are verified.
Merchant onboarding, credentials, callbacks, webhooks, reconciliation, refunds and acceptance are commissioned as one controlled release.