Get customer wallet by customer ID
GET /wallet/customer
Retrieves the wallet and transaction limit details for a single customer using their customerId.
Request
Bearer token.
The unique customer ID (UUID) returned when the wallet was created.
Response
true on success.The customer wallet object, including tier-based transaction limits.
Examples
Response
Get customer wallet by account number
GET /wallet/customer/account
Retrieves a customer wallet using a 10-digit virtual account number. The account must belong to a customer under your merchant account.
Request
Bearer token.
Exactly 10-digit virtual account number.
Examples
Response
Get wallet info by account number
GET /wallet/info
Returns basic wallet information for any account number that belongs to your merchant (customer or merchant wallet). Unlike /wallet/customer/account, this endpoint returns a minimal object without customer-level details.
Request
Bearer token.
Exactly 10-digit account number.
Response
true on success.Examples
Response
Close a wallet
POST /wallet/close
Freezes a customer wallet, preventing any further transactions. Provide a reason for audit purposes. The wallet remains frozen until you explicitly re-enable it with POST /wallet/enable.
Request
Bearer token.
The customer ID whose wallet you want to close.
Reason for closing the wallet. Stored for audit and shown if someone attempts to enable the wallet.
Response
true on success.Confirmation message:
"Customer wallet successfully frozen."Examples
Response
Enable a wallet
POST /wallet/enable
Re-activates a previously frozen wallet. If the wallet was frozen due to BVN/NIN verification failure and BVN verification is still pending, the request is rejected until verification is resolved.
Request
Bearer token.
The customer ID whose wallet you want to activate.
Response
true on success.Confirmation message:
"Customer wallet successfully activated."Examples
Response
Set transaction PIN
PUT /wallet/transaction-pin
Sets or updates the 4-digit transaction PIN for a customer wallet. The PIN is required by certain debit flows.
Request
Bearer token.
The customer ID whose PIN you are setting.
The new 4-digit PIN. Minimum 4 characters.
Response
true on success."Wallet transaction PIN successfully set."Examples
Response
Enable post-no-credit mode
POST /wallet/enable-post-no-credit
Enables post-no-credit (PNC) mode on a customer wallet. When PNC is active, any credits to that wallet — including from batch operations — are silently rejected with an error. Use this to block a wallet from receiving funds without fully freezing it.
This endpoint requires
MainMerchant or Admin role. Standard API keys cannot call this endpoint.Request
Bearer token with elevated permissions.
UUID of the customer. Must be a valid UUID format.
Optional reason for enabling PNC mode.
Examples
Response
Disable post-no-credit mode
POST /wallet/disable-post-no-credit
Removes the post-no-credit restriction from a customer wallet, allowing the wallet to receive credits again.
Requires
MainMerchant or Admin role.Request
Bearer token with elevated permissions.
UUID of the customer.
Optional reason for disabling PNC mode.
Examples
Response
Error responses
| HTTP Status | Description |
|---|---|
400 | Customer not found or does not belong to your merchant account |
400 | Wallet frozen due to verification failure — BVN verification required before enabling |
400 | Account number must be exactly 10 digits |
401 | Missing or invalid authentication token |
403 | Insufficient permissions for the requested operation |
