Assign funding sources (NGN Static Accounts)

Static Accounts NGN and Crypto (USDT, USDC, EUSD)

PUT /api/v1/user/subwallet-fund-source

Use this endpoint to assign a funding source to a user’s subwallet. The funding source can be a fiat account or a cryptocurrency address, depending on the selected fund_type, chain, and currency.

Authorization

ItemValue
Authentication{{API_KEY}}

Headers

HeaderValueDescription
Content-Typeapplication/jsonSpecifies that the request body contains JSON data.
x-merchant-refYour merchant referenceIdentifies the merchant making the request.

Example Request

{
  "user_ref": "{{vault:Merchant-user-ref}}",
  "wallet_id": "LBWEUSD:MOB677851297ADB454BB35E1EEE16214E9B00EJU",
  "fund_type": "STATIC_CRYPTO_ADDRESS",
  "chain": "MOB",
  "currency": "EUSD",
  "account_reference": "SEUSD0000012301-500-93",
  "user_kyc": {
    "name": "Tes Aola",
    "email": "[email protected]",
    "address": "No 6 Sars Road",
    "phone": "2348044",
    "bvn": "22301781",
    "dob": "1987-05-03"
  }
{
	"user_ref": "{{vault:Merchant-user-ref}}",
	"wallet_id": "{{vault:usdt_wallet}}",
	"fund_type": "STATIC_CRYPTO_ADDRESS",
	"chain": "POL",
	"currency": "USDT",
	"account_reference": "demo-crypto-500-952_1",
	"user_kyc": {
		"name": "Emanov nior",
		"email": "[email protected]",
		"address": "No 6 sars road",
		"phone": "232044",
		"bvn": "223081",
		"dob": "1987-05-03"
	}
}
{
	"user_ref": "UREFB57BE10C22F04348B429E20E8D62DB7A003F7",
	"wallet_id": "LBWNGNE2EC9DE6B9924C27B756282B7FCDD60C00BS4",
	"fund_type": "STATIC_VIRTUAL_ACCOUNT",
	"chain": "FIAT_ACCOUNT",
	"currency": "NGN",
	"account_reference": "Rava_001_1",
	"user_kyc": {
		"name": "Ebine Arowolo",
		"email": "[email protected]",
		"address": "Lagos, Nigeria",
		"phone": "2348024210779",
		"bvn": "22142307845",
		"dob": "1980-09-23"
	}
}

Request Body

ParameterTypeDescription
user_refstringReference of the user receiving the funding source.
wallet_idstringIdentifier of the subwallet to which the funding source will be assigned.
fund_typestringType of funding source to assign, such as STATIC_CRYPTO_ADDRESS.
chainstringBlockchain network associated with the funding source, such as MOB.
currencystringCurrency associated with the funding source, such as EUSD.
account_referencestringReference associated with the funding source or account.
user_kycobjectUser identity information required for the funding source assignment.

user_kyc Object

ParameterTypeDescription
namestringUser's full name.
emailstringUser's email address.
addressstringUser's residential address.
phonestringUser's phone number.
bvnstringUser's Bank Verification Number, where applicable.
dobstringUser's date of birth in YYYY-MM-DD format.

Response

{
  "status": "success",
  "message": "Assigned successfully",
  "fiat_data": {
    "funding_source_id": "",
    "account_number": "",
    "bank_code": "",
    "currency": ""
  },
  "crypto_data": {
    "funding_source_id": "9fecf7e0-2818-44a4-aa74-693905974cac",
    "address": "7EPZGJvmgP35sULHZzJozNRyprExd6nKYveHxsMgayP1u9oMYXEcFnCYUc9TTrbegLiCGvPa5xgKcoTSr1hWn1BfmRxZB4jazWjwkJErJYb",
    "chain": "MOB"
  }
}

Response Parameters

ParameterTypeDescription
statusstringIndicates the outcome of the request.
messagestringDescribes the result of the operation.
fiat_dataobjectContains funding source details for fiat accounts, when applicable.
fiat_data.funding_source_idstringIdentifier of the assigned fiat funding source.
fiat_data.account_numberstringAccount number associated with the fiat funding source.
fiat_data.bank_codestringBank code associated with the fiat funding source.
fiat_data.currencystringCurrency of the fiat funding source.
crypto_dataobjectContains funding source details for cryptocurrency addresses, when applicable.
crypto_data.funding_source_idstringUnique identifier of the assigned cryptocurrency funding source.
crypto_data.addressstringCryptocurrency address assigned to the user.
crypto_data.chainstringBlockchain network associated with the cryptocurrency address.

Status Codes

Refer to the API's returned HTTP status code and response message to determine whether the request succeeded or failed.

Notes

  • Ensure the user_ref and wallet_id belong to the intended user and wallet.
  • The fund_type, chain, and currency values must be compatible with the selected wallet and supported funding source.
  • The user_kyc object should contain valid user information in the required format.
  • Depending on the funding source type, the response may populate fiat_data or crypto_data. Empty fields may indicate that the corresponding funding source type does not apply to the request.
  • Treat the returned funding source ID and address as important integration data and store them securely where needed.

Did this page help you?