User Management API: BVN Onboarding, KYC & Account Control

The User Management API lets you register end-users on Strails using their Bank Verification Number (BVN), track the async KYC process through to completion, fetch full user profiles including wallet addresses and virtual accounts, control user account status, and route a user’s cNGN deliveries to an external default wallet. Because BVN verification is handled by an external identity provider, all onboarding requests are processed asynchronously - you receive a requestId immediately and poll or listen for the result.

Endpoints Overview

Section	Endpoint	Method	Description
Onboard User	`/onboarduser`	POST	Initiate BVN-based KYC and create a new user account.
Onboard Status	`/onboardstatus`	POST	Check the current status of a pending onboarding request.
Get User Details	`/getuserdetails`	POST	Retrieve a user’s full profile, wallets, and virtual accounts.
Manage User Status	`/manageuserstatus`	POST	Activate or deactivate a user account with an audit reason.
List Fintech Users	`/listfintechusers`	POST	Retrieve a paginated list of all users belonging to your fintech.
Set User Default Wallet	`/setuserdefaultwallet`	POST	Route a user’s cNGN deliveries to an external wallet address.
Get User Default Wallet	`/getuserdefaultwallet`	POST	Retrieve the external default wallet currently set for a user.
Remove User Default Wallet	`/removeuserdefaultwallet`	DELETE	Clear the external default wallet and revert to the system smart wallet.
Set User Settlement Network	`/setusersettlementnetwork`	POST	Choose the network a user’s onramp cNGN is delivered on.
Get User Settlement Network	`/getusersettlementnetwork`	POST	Retrieve a user’s settlement network and where it would be delivered.
Remove User Settlement Network	`/removeusersettlementnetwork`	POST	Clear a user’s settlement network setting.
List User Settlement Destinations	`/listusersettlementdestinations`	POST	List every network and whether the user can be paid on it.
Set Fintech Settlement Network	`/setfintechsettlementnetwork`	POST	Set the default settlement network for all of your users.
Get Fintech Settlement Network	`/getfintechsettlementnetwork`	POST	Retrieve your fintech’s default settlement network.
Remove Fintech Settlement Network	`/removefintechsettlementnetwork`	POST	Clear your fintech’s default settlement network and revert to Base.

POST /onboarduser

Initiates onboarding for a new user by submitting their 11-digit BVN for identity verification. The request is processed asynchronously - use the returned requestId to poll /onboardstatus, or wait for the user.onboarded webhook event.

curl -X POST https://api.strails.io/v1/onboarduser \
  -H "Content-Type: application/json" \
  -H "x-api-key: YOUR_SECRET_API_KEY" \
  -d '{
    "bvn": "12345678901"
  }'

Request Parameters

string

required

The user’s 11-digit Bank Verification Number. Must be exactly 11 numeric digits and must not belong to an existing Strails user.

bvn is the only field this endpoint accepts. Identity details (names, phone, date of birth) are resolved from the BVN record, and the user’s identifier is issued by Strails and returned as userHash - do not supply your own userId.

Response

{
  "status": "Success",
  "response_code": "00",
  "message": "User registration initiated",
  "data": {
    "requestId": "7898f29e-10a6-4b2b-9496-f4ee50549fd4",
    "status": "processing",
    "userHash": "user_uniqueID",
    "message": "User registration request has been submitted for processing",
    "estimatedCompletionTime": "2-5 minutes"
  }
}

Store the requestId returned here - you will need it to check onboarding status via /onboardstatus.

Error Responses

{
  "status": "Error",
  "response_code": "01",
  "message": "Validation error",
  "error": "Invalid BVN format. BVN must be 11 digits"
}

{
  "status": "Error",
  "response_code": "01",
  "message": "User already exists",
  "error": "A user with this BVN is already registered"
}

{
  "status": "Error",
  "response_code": "05",
  "message": "BVN verification failed",
  "error": "Unable to verify BVN with identity provider"
}

POST /onboardstatus

Checks the current status of a pending user onboarding request using the requestId returned by /onboarduser. Poll this endpoint until status is "completed" or "failed", or handle the user.onboarded webhook event instead.

curl -X POST https://api.strails.io/v1/onboardstatus \
  -H "Content-Type: application/json" \
  -H "x-api-key: YOUR_SECRET_API_KEY" \
  -d '{
    "requestId": "7898f29e-10a6-4b2b-9496-f4ee50549fd4"
  }'

Request Parameters

string

required

The unique identifier returned by /onboarduser when the registration was initiated.

Response

{
  "status": "Success",
  "response_code": "00",
  "message": "User registration completed successfully",
  "data": {
    "type": "user_registration",
    "userId": "user_uniqueID",
    "status": "completed",
    "createdAt": "2026-01-18T19:33:39.945Z",
    "message": "User registration completed successfully"
  }
}

Once status is "completed", use the userId from the response to call /getuserdetails and retrieve the user’s full profile.

Error Responses

{
  "status": "Error",
  "response_code": "02",
  "message": "Request not found",
  "error": "No onboarding request found with the provided requestId"
}

POST /getuserdetails

Retrieves the full profile for a verified user, including their personal details pulled from BVN verification, all multi-chain wallet addresses provisioned by Strails, and any virtual accounts assigned to them.

curl -X POST https://api.strails.io/v1/getuserdetails \
  -H "Content-Type: application/json" \
  -H "x-api-key: YOUR_SECRET_API_KEY" \
  -d '{
    "userId": "user_uniqueID"
  }'

Request Parameters

string

required

The unique identifier for the user, returned as userId in the /onboardstatus response once onboarding is complete.

Response

{
  "status": "Success",
  "response_code": "00",
  "message": "User details retrieved successfully",
  "data": {
    "userId": "user_uniqueID",
    "isActive": true,
    "personalDetails": {
      "firstName": "John",
      "middleName": "Doe",
      "lastName": "Smith"
    },
    "walletDetails": {
      "evmWallet": "0x2KCC051A79dE65d7068542cB5D9D03754cc22F60",
      "bantuWallet": "GB63QBTTWQXRO5BNO3Z4RRAGBPQFDGAGWNHKHTGSJOZF3V2NKG7V4XTY",
      "solanaWallet": "HaXjvARhAxjKZRojmer86G31kXm52Nd4FZP4jrg4H2hf",
      "walletCreatedAt": "2025-08-20T10:15:00.000Z"
    },
    "virtualAccounts": [
      {
        "accountNumber": "1234567890",
        "accountName": "John Doe",
        "bankName": "Optimus Bank",
        "bankCode": "0000",
        "provider": "novac",
        "accountType": "user_permanent",
        "reference": "userId",
        "createdAt": "2026-05-29T12:42:45.034Z"
      }
    ]
  }
}

Error Responses

{
  "status": "Error",
  "response_code": "02",
  "message": "User not found",
  "error": "No verified user found with the provided userId"
}

POST /manageuserstatus

Activates or deactivates a user account. When deactivating, you must supply a reason - this is recorded in the audit trail. Deactivated users cannot initiate transactions or receive deposits until reactivated.

curl -X POST https://api.strails.io/v1/manageuserstatus \
  -H "Content-Type: application/json" \
  -H "x-api-key: YOUR_SECRET_API_KEY" \
  -d '{
    "userId": "user_uniqueID",
    "active": false,
    "reason": "Account suspended by customer request"
  }'

Request Parameters

string

required

The unique identifier of the user whose status you want to change.

boolean

required

Set to true to activate the account or false to deactivate it.

string

A human-readable explanation for the status change. Required when active is false. Recorded in the audit log for compliance purposes.

Response

{
  "status": "Success",
  "response_code": "00",
  "message": "User deactivated successfully",
  "data": {
    "userId": "user_uniqueID",
    "active": false,
    "changedAt": "2025-12-16T09:17:33.658Z"
  }
}

Error Responses

{
  "status": "Error",
  "response_code": "02",
  "message": "User not found",
  "error": "No verified user found with the provided userId"
}

{
  "status": "Error",
  "response_code": "01",
  "message": "Validation error",
  "error": "Reason is required when deactivating a user"
}

POST /listfintechusers

Returns a paginated list of all users belonging to your fintech, with summary wallet and virtual account information for each. Use limit and offset to page through large user sets, and status to filter by account state.

curl -X POST https://api.strails.io/v1/listfintechusers \
  -H "Content-Type: application/json" \
  -H "x-api-key: YOUR_SECRET_API_KEY" \
  -d '{
    "limit": 20,
    "offset": 0,
    "status": "all",
    "orderBy": "verifiedAt",
    "orderDirection": "desc"
  }'

Request Parameters

number

Number of users to return per page. Accepts values between 1 and 100. Defaults to 20.

number

Number of users to skip before returning results. Use with limit to paginate through the full list. Defaults to 0.

string

Filter users by account state. Accepted values: "active", "inactive", "all". Defaults to "all".

string

Field to sort results by. Accepted values: "createdAt", "verifiedAt". Defaults to "verifiedAt".

string

Sort direction. Accepted values: "asc", "desc". Defaults to "desc".

Response

{
  "status": "Success",
  "response_code": "00",
  "message": "Users retrieved successfully",
  "data": {
    "users": [
      {
        "userId": "abc123...",
        "firstName": "John",
        "lastName": "Doe",
        "isActive": true,
        "hasWallet": true,
        "wallets": {
          "evm": "0x...",
          "solana": null,
          "bantu": null
        },
        "virtualAccount": {
          "accountNumber": "1234567890",
          "accountName": "John Doe",
          "bankName": "Fidelity Bank",
          "bankCode": "070",
          "provider": "redbiller"
        },
        "verifiedAt": "2026-05-10T12:00:00.000Z",
        "createdAt": "2026-05-10T12:00:00.000Z"
      }
    ],
    "pagination": {
      "total": 150,
      "limit": 20,
      "offset": 0,
      "currentPage": 1,
      "totalPages": 8,
      "hasNextPage": true,
      "hasPreviousPage": false
    }
  }
}

array

Array of user summary objects, one per verified user belonging to your fintech.

number

Total number of users matching the applied filter, regardless of limit and offset.

number

Total number of pages available at the current limit setting.

boolean

true if there are more users beyond the current page. Increment offset by limit to fetch the next page.

boolean

true if the current offset is greater than 0, meaning a previous page exists.

User Default Wallet

By default, cNGN disbursed for a user is delivered to the Strails-managed smart wallet provisioned during onboarding. Setting an external default wallet redirects those deliveries to an address you control on behalf of the user - useful when the user self-custodies or when your fintech settles into its own treasury addresses. The external default wallet applies to three delivery paths only:

cNGN disbursed from a deposit into the user’s permanent virtual account
cNGN disbursed through /cngnonramp
Tokens swept when sweepToOfframp is enabled

Deposit and funding webhooks fire as normal; the destination address in the payload reflects the external wallet.

An external default wallet is a delivery destination only. Strails holds no keys for it, so swaps, offramp, and escrow continue to operate against the user’s Strails-managed wallet and never against this address. Funds delivered here must be moved by whoever holds the keys.

POST /setuserdefaultwallet

Sets or replaces the external default wallet for a user. Calling this endpoint again with a different address overwrites the existing configuration. The address must be valid for the specified blockchain.

curl -X POST https://api.strails.io/v1/setuserdefaultwallet \
  -H "Content-Type: application/json" \
  -H "x-api-key: YOUR_SECRET_API_KEY" \
  -d '{
    "userId": "user_uniqueID",
    "address": "0xc5422E03B8250917023501E4697c738E7427b540",
    "blockchain": "base",
    "label": "User payout wallet"
  }'

Request Parameters

string

required

The unique identifier of the user the wallet belongs to.

string

required

The external EVM wallet address (0x...) that should receive the user’s cNGN deliveries.

string

The EVM network the address belongs to (e.g. base, eth, bsc). Defaults to base. A network other than Base is accepted only when bridged settlement is available - see Settlement Network.

string

A human-readable name for the wallet (e.g. User payout wallet).

Response

{
  "status": "Success",
  "response_code": "00",
  "message": "Default wallet set successfully",
  "data": {
    "userId": "user_uniqueID",
    "defaultWallet": {
      "address": "0x52428ccd2529ff22d03c72a60aec877ca0a69308",
      "blockchain": "base",
      "type": "external",
      "status": "active",
      "label": "User payout wallet"
    },
    "note": "cNGN will be delivered to this wallet. Platform swaps/offramp do not operate on it."
  }
}

string

Always external for wallets registered through this endpoint.

string

Whether the wallet is currently receiving deliveries. active once set.

string

Plain-language reminder of the delivery-only behaviour of external default wallets.

Error Responses

{
  "status": "Error",
  "response_code": "02",
  "message": "User not found",
  "error": "No verified user found with the provided userId"
}

{
  "status": "Error",
  "response_code": "01",
  "message": "Validation error",
  "error": "Invalid wallet address for the specified blockchain"
}

POST /getuserdefaultwallet

Retrieves the external default wallet currently configured for a user. Returns defaultWallet: null when no external wallet is set - in that case cNGN is delivered to the user’s system smart wallet.

curl -X POST https://api.strails.io/v1/getuserdefaultwallet \
  -H "Content-Type: application/json" \
  -H "x-api-key: YOUR_SECRET_API_KEY" \
  -d '{
    "userId": "user_uniqueID"
  }'

Request Parameters

string

required

The unique identifier of the user whose default wallet you want to retrieve.

Response

{
  "status": "Success",
  "response_code": "00",
  "message": "Default wallet retrieved successfully",
  "data": {
    "userId": "user_uniqueID",
    "defaultWallet": null
  }
}

object

The configured external wallet. null if the user has no external default wallet.

Error Responses

{
  "status": "Error",
  "response_code": "02",
  "message": "User not found",
  "error": "No verified user found with the provided userId"
}

DELETE /removeuserdefaultwallet

Clears the external default wallet for a user. Once removed, cNGN deliveries revert to the user’s Strails-managed smart wallet.

curl -X DELETE https://api.strails.io/v1/removeuserdefaultwallet \
  -H "Content-Type: application/json" \
  -H "x-api-key: YOUR_SECRET_API_KEY" \
  -d '{
    "userId": "user_uniqueID"
  }'

Request Parameters

string

required

The unique identifier of the user whose default wallet you want to clear.

Response

{
  "status": "Success",
  "response_code": "00",
  "message": "Default wallet removed successfully",
  "data": {
    "userId": "user_uniqueID",
    "defaultWallet": null,
    "note": "Funding reverts to the user's system smart wallet."
  }
}

Removing a default wallet only changes where future deliveries go. Balances already sent to the external address remain there.

Settlement Network

The settlement network is the chain a user’s onramp cNGN is delivered on. Unless you set one, every onramp settles on Base. You can set a network per user, set a default for all of your users, or name one on a single /cngnonramp request. It applies to cNGN disbursed from a deposit into the user’s permanent virtual account and to cNGN disbursed through /cngnonramp.

How the network is chosen

Strails uses the first of these that is set:

settlementNetwork on the /cngnonramp request (that request only, optionally with a settlementAddress)
The user’s settlement network, set with /setusersettlementnetwork
The network the user’s external default wallet is registered for
Your fintech’s default, set with /setfintechsettlementnetwork
Base

Because steps 2 and 3 outrank step 4, a fintech default never overrides a user who has their own setting or an external default wallet.

Where the cNGN lands

A /cngnonramp request that sends settlementAddress is delivered to that address, whatever the user has registered. Otherwise: Off Base, cNGN is delivered only to an external default wallet registered for that network. The user’s Strails-managed smart wallet exists only on Base, so it is never a destination on another chain. On Base, cNGN goes to the user’s external default wallet if it is registered for Base, otherwise to their smart wallet.

Network	Destination
Base	External default wallet registered for Base, otherwise the user’s smart wallet
Other EVM networks (`bsc`, `eth`, `pol`, `atc`, `lisk`, `monad`, `arc`, `celo`)	External default wallet registered for that network
Tron, Solana, Bantu (`trx`, `sol`, `xbn`)	None today - external default wallets must be EVM addresses

Use /listusersettlementdestinations to check where a user can be paid before you pick a network.

Strails bridges the cNGN from Base to the settlement network and absorbs the bridge fee, so the user receives the same amount they would have received on Base. A bridged deposit is reported complete only after the bridge releases the cNGN on the destination network. If a bridge transfer can’t be started (for example, the amount is above the bridged-settlement limit), the cNGN is delivered on Base instead.

Permanent virtual account deposits always settle to a registered wallet, so a user’s settlement network other than Base needs an external default wallet on that network - /setusersettlementnetwork refuses it otherwise. If a user has no address on the resolved network, a permanent virtual account deposit is held rather than paid on another network, and Strails is alerted.A /cngnonramp request that names such a network in settlementNetwork without a settlementAddress is refused when you make it. For a /cngnonramp payment where the network comes from a stored setting instead, the cNGN is delivered on Base.

Network values

base, bsc, eth, pol, trx, sol, xbn, atc, lisk, monad, arc, celo. Common names such as ethereum, polygon, bnb, and celo chain are also accepted and normalised to these codes. A network other than Base can be stored only while bridged settlement is available on Strails. Otherwise the set endpoints, and /cngnonramp, return:

{
  "status": "Failed",
  "response_code": "01",
  "message": "Settlement on BNB Smart Chain is not available yet; only Base is supported"
}

POST /setusersettlementnetwork

Sets the network a user’s onramps settle on. Strails stores the network only if the user already has an address that can receive on it, so a stored setting is always one the onramp can honour.

curl -X POST https://api.strails.io/v1/setusersettlementnetwork \
  -H "Content-Type: application/json" \
  -H "x-api-key: YOUR_SECRET_API_KEY" \
  -d '{
    "userId": "user_uniqueID",
    "network": "pol"
  }'

Request Parameters

string

required

The unique identifier of the user.

string

required

The settlement network. See network values.

Response

{
  "status": "Success",
  "response_code": "00",
  "message": "Default settlement network set successfully",
  "data": {
    "userId": "user_uniqueID",
    "settlementNetwork": "pol",
    "networkName": "Polygon",
    "destinationAddress": "0xc5422E03B8250917023501E4697c738E7427b540",
    "destinationSource": "external_default"
  }
}

string

The address that will receive the user’s onramp cNGN on this network.

string

Which of the user’s wallets that address is: external_default (their external default wallet) or smart_wallet (their Strails-managed smart wallet, Base only).

Error Responses

{
  "status": "Failed",
  "response_code": "01",
  "message": "This user has no address that can receive on Polygon. Register an external default wallet for it first."
}

{
  "status": "Failed",
  "response_code": "01",
  "message": "\"polygonx\" is not a network Strails supports"
}

{
  "status": "Failed",
  "response_code": "03",
  "message": "Invalid user credentials for fintech"
}

POST /getusersettlementnetwork

Returns the network a user’s onramps settle on and the address that would receive them. When the user has no setting of their own, this reports Base.

curl -X POST https://api.strails.io/v1/getusersettlementnetwork \
  -H "Content-Type: application/json" \
  -H "x-api-key: YOUR_SECRET_API_KEY" \
  -d '{
    "userId": "user_uniqueID"
  }'

Request Parameters

string

required

The unique identifier of the user.

Response

{
  "status": "Success",
  "response_code": "00",
  "message": "Default settlement network retrieved successfully",
  "data": {
    "userId": "user_uniqueID",
    "settlementNetwork": "base",
    "networkName": "Base",
    "isExplicit": false,
    "destinationAddress": "0x2KCC051A79dE65d7068542cB5D9D03754cc22F60",
    "destinationSource": "smart_wallet"
  }
}

boolean

true when the user has a settlement network set with /setusersettlementnetwork. false means the user has no setting and Base is reported.

string

The address that would receive on settlementNetwork, or null if the user has none there.

This reports the user’s own setting only. When isExplicit is false, an onramp can still settle elsewhere through the user’s external default wallet network or your fintech default - see How the network is chosen.

POST /removeusersettlementnetwork

Clears a user’s settlement network setting. Onramps for the user then follow the rest of the precedence order.

curl -X POST https://api.strails.io/v1/removeusersettlementnetwork \
  -H "Content-Type: application/json" \
  -H "x-api-key: YOUR_SECRET_API_KEY" \
  -d '{
    "userId": "user_uniqueID"
  }'

Request Parameters

string

required

The unique identifier of the user.

Response

{
  "status": "Success",
  "response_code": "00",
  "message": "Default settlement network cleared successfully",
  "data": {
    "userId": "user_uniqueID",
    "settlementNetwork": "base",
    "note": "Onramps settle on Base again."
  }
}

POST /listusersettlementdestinations

Lists every supported network and whether the user can be paid on it. Call this before setting a user’s network or naming one on /cngnonramp - a network with canSettle: false would be refused or held.

curl -X POST https://api.strails.io/v1/listusersettlementdestinations \
  -H "Content-Type: application/json" \
  -H "x-api-key: YOUR_SECRET_API_KEY" \
  -d '{
    "userId": "user_uniqueID"
  }'

Request Parameters

string

required

The unique identifier of the user.

Response

{
  "status": "Success",
  "response_code": "00",
  "message": "Settlement destinations retrieved successfully",
  "data": {
    "userId": "user_uniqueID",
    "destinations": [
      {
        "network": "base",
        "canSettle": true,
        "destinationAddress": "0x2KCC051A79dE65d7068542cB5D9D03754cc22F60",
        "destinationSource": "smart_wallet",
        "requiresBridge": false,
        "networkName": "Base"
      },
      {
        "network": "bsc",
        "canSettle": false,
        "destinationAddress": null,
        "destinationSource": null,
        "requiresBridge": true,
        "networkName": "BNB Smart Chain"
      }
    ],
    "settleableNetworks": ["base"],
    "note": "A network with canSettle false has no address for this user. Register an external wallet for it first; off Base an internal wallet cannot receive."
  }
}

array

One entry per supported network, with network, networkName, canSettle, destinationAddress, destinationSource (external_default, smart_wallet, or null), and requiresBridge (true for every network except Base).

array

The networks where canSettle is true.

POST /setfintechsettlementnetwork

Sets the default settlement network for all of your users. It is a default, not an override: a user’s own setting and their external default wallet network both take precedence.

Strails can’t check this setting against each user’s wallets. A user with no address on the chosen network has their permanent virtual account deposits held rather than paid elsewhere, so register an external default wallet on that network for those users.

curl -X POST https://api.strails.io/v1/setfintechsettlementnetwork \
  -H "Content-Type: application/json" \
  -H "x-api-key: YOUR_SECRET_API_KEY" \
  -d '{
    "network": "pol"
  }'

Request Parameters

string

required

The default settlement network. See network values.

Response

{
  "status": "Success",
  "response_code": "00",
  "message": "Default settlement network set successfully",
  "data": {
    "settlementNetwork": "pol",
    "networkName": "Polygon",
    "note": "Users without their own setting are paid on Polygon. A user with no address on Polygon will have their deposit held rather than paid elsewhere, so give those users an external wallet for it."
  }
}

Error Responses

{
  "status": "Failed",
  "response_code": "01",
  "message": "\"polygonx\" is not a network Strails supports"
}

POST /getfintechsettlementnetwork

Returns your fintech’s default settlement network. When none is set, this reports Base.

curl -X POST https://api.strails.io/v1/getfintechsettlementnetwork \
  -H "x-api-key: YOUR_SECRET_API_KEY"

Response

{
  "status": "Success",
  "response_code": "00",
  "message": "Default settlement network retrieved successfully",
  "data": {
    "settlementNetwork": "pol",
    "networkName": "Polygon",
    "isExplicit": true,
    "note": "A user's own setting, and the network their external default wallet is registered for, both take precedence over this."
  }
}

boolean

true when a default is set. false means none is set and Base is reported.

POST /removefintechsettlementnetwork

Clears your fintech’s default settlement network. Users without their own setting or an external default wallet network settle on Base again.

curl -X POST https://api.strails.io/v1/removefintechsettlementnetwork \
  -H "x-api-key: YOUR_SECRET_API_KEY"

Response

{
  "status": "Success",
  "response_code": "00",
  "message": "Default settlement network cleared successfully",
  "data": {
    "settlementNetwork": "base",
    "note": "Users without their own setting are paid on Base again."
  }
}

​Endpoints Overview

​POST /onboarduser

​Request Parameters

​Response

​Error Responses

​POST /onboardstatus

​Request Parameters

​Response

​Error Responses

​POST /getuserdetails

​Request Parameters

​Response

​Error Responses

​POST /manageuserstatus

​Request Parameters

​Response

​Error Responses

​POST /listfintechusers

​Request Parameters

​Response

​User Default Wallet

​POST /setuserdefaultwallet

​Request Parameters

​Response

​Error Responses

​POST /getuserdefaultwallet

​Request Parameters

​Response

​Error Responses

​DELETE /removeuserdefaultwallet

​Request Parameters

​Response

​Settlement Network

​How the network is chosen

​Where the cNGN lands

​Network values

​POST /setusersettlementnetwork

​Request Parameters

​Response

​Error Responses

​POST /getusersettlementnetwork

​Request Parameters

​Response

​POST /removeusersettlementnetwork

​Request Parameters

​Response

​POST /listusersettlementdestinations

​Request Parameters

​Response

​POST /setfintechsettlementnetwork

​Request Parameters

​Response

​Error Responses

​POST /getfintechsettlementnetwork

​Response

​POST /removefintechsettlementnetwork

​Response

Endpoints Overview

POST /onboarduser

Request Parameters

Response

Error Responses

POST /onboardstatus

Request Parameters

Response

Error Responses

POST /getuserdetails

Request Parameters

Response

Error Responses

POST /manageuserstatus

Request Parameters

Response

Error Responses

POST /listfintechusers

Request Parameters

Response

User Default Wallet

POST /setuserdefaultwallet

Request Parameters

Response

Error Responses

POST /getuserdefaultwallet

Request Parameters

Response

Error Responses

DELETE /removeuserdefaultwallet

Request Parameters

Response

Settlement Network

How the network is chosen

Where the cNGN lands

Network values

POST /setusersettlementnetwork

Request Parameters

Response

Error Responses

POST /getusersettlementnetwork

Request Parameters

Response

POST /removeusersettlementnetwork

Request Parameters

Response

POST /listusersettlementdestinations

Request Parameters

Response

POST /setfintechsettlementnetwork

Request Parameters

Response

Error Responses

POST /getfintechsettlementnetwork

Response

POST /removefintechsettlementnetwork

Response