Some request fields look like normal text, but they are actually catalog values. For example, coin, token, chain, and market should come from Simfy Business-supported values. Do not hard-code values unless Simfy Business has confirmed them for your environment.

Common examples

FieldWhere to get itUsed for
coin or tokenSimfy Business-supported asset list or GET /api/v1/utils/ratesWallet creation, swaps, and deposits
chainGET /api/v1/utils/{coin}/networksCrypto deposit addresses
marketGET /api/v1/wallets/marketsMarket display and rate checks
bankCodeYour approved payout bank-code sourceNGN payout preview

Why this matters

These values can change when assets, networks, markets, or payout routes are added, renamed, or disabled. Discovery endpoints keep your integration in sync.
  1. Fetch the available options.
  2. Store the selected ID only for the current flow.
  3. Preview the payout before confirmation.
  4. Submit the confirmation only after the user confirms the preview.
If you cache catalog responses, keep the cache short-lived and refresh it when Simfy Business returns a validation error.