Payments
Every money movement is recorded as an immutable ledger entry with a provider reference.
No payment provider connected
Provider choice is an open decision. Credentials will live in server-side secrets only — never in frontend code — and all charges will be created and verified server-side.
Payment records
Placeholder rows; amounts intentionally blank until commercial terms are set.
| Reference | Type | Party | Amount | Status |
|---|---|---|---|---|
| PAY-5521 | Trip payment | Amaka N. | — | Captured |
| PAY-5520 | Wallet funding | Segun L. | — | Pending |
| PAY-5518 | Founding member | Hauwa S. | — | Captured |
| PAY-5511 | Refund | Hauwa S. | — | Reversed |
| PAY-5502 | Driver payout | Chinedu O. | — | Processing |
Provider integration points
Where a future provider plugs in — each is a server-side function boundary.
Passenger trip payment
Charge on trip completion or wallet debit
Wallet funding
Hosted checkout / bank transfer, confirmed by webhook
Membership payment
Recurring or one-off charge, status drives access
Founding member payment
One-off charge, unlocks founding benefits
Driver payout
Batch transfer to verified bank account
Withdrawal request
Driver-initiated payout, admin or rule approval
Refund
Reverse a captured payment, credit the wallet ledger