Skip to main content
Use fiat wallet routes to show incoming deposit details and confirm bank account names before saving recipient records. The deposit account is for incoming fiat deposits. Account verification is for saved recipient setup and account-name confirmation. Production requires approved KYB before the API returns an existing NGN deposit account, provisions a new account, or verifies recipient bank details. A non-approved account receives 403, including when deposit details were provisioned previously. Development and staging skip this gate.

​
List Supported Banks

Bank codes can change. Load them from the API instead of maintaining a static list in your application.
Each bank has an institution_code and, for some banks, a shorter bank_code. Wherever the API asks for a bank_code, either value is accepted. institution_code is always present, so it is the safer one to store.

​
Verify A Bank Account

Use verification before creating a fiat recipient so operators can confirm the account name they expect.
Verification confirms account details. It does not create a recipient and it does not move funds. It returns 503 when the bank lookup is temporarily unavailable; retry with backoff.

​
Retrieve Deposit Account

An optional currency query parameter defaults to NGN, the only supported value; anything else returns 400. Show the returned account name, bank name, and account number exactly. Reconcile incoming credits from GET /partner/wallets/transactions.

​
Required Headers

GET /partner/wallets/fiat/banks is public. Verification and deposit account reads require X-Api-Key; verification requires key access to recipient setup, and deposit account reads require wallet read access. Common failures are 400 for an invalid bank code, account number, or currency, 403 for a key without the needed scope or an account whose production KYB is not approved, and 503 when bank verification is temporarily unavailable.