Payments
Initiate, verify, refund, and monitor payments through the existing public API
AfriRoute already exposes payment initiation, verification, transaction lookup, refund, provider discovery, and webhook paths. The portal should surface those as the supported payment lifecycle.
Docs mode
Reference and guide
Keep the task clear, the example nearby, and the next step obvious.
Recommended payment lifecycle
Initiate the payment first, persist the returned transaction reference, then verify state through the verify or transaction lookup endpoints. Use webhooks for provider-side finality when available.
Keep provider selection, refund support, and webhook handling adjacent to the examples so developers understand which pieces are synchronous and which are event-driven.
Core endpoints
POST /api/v1/payments/initiate
GET /api/v1/payments/verify/{transactionId}
GET /api/v1/payments/transaction/{transactionId}
GET /api/v1/payments/transactions
GET /api/v1/payments/providers
What to emphasize publicly
Provider discovery and initiation examples for the supported payment flows.
Verification and transaction state handling for back-office reconciliation.
Webhook-driven finality and retry-safe transaction processing.