> ## Documentation Index
> Fetch the complete documentation index at: https://docs.northfond.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# Supported capabilities

> See which environments, chains, assets, directions, and payment methods NorthFond currently supports.

Use this page as the public capability boundary. A route must be enabled for your business environment even when it appears in the API reference.

## Environments

| Capability                       | Sandbox   | Live                     |
| -------------------------------- | --------- | ------------------------ |
| API authentication               | Supported | Supported after approval |
| Deterministic payment simulation | Supported | Not applicable           |
| Managed-wallet on-ramp           | Supported | Readiness-gated          |
| External-wallet off-ramp         | Simulated | Readiness-gated          |
| Managed-wallet off-ramp          | Simulated | Disabled by default      |

## Chains and assets

The initial Business API is EVM-only and uses canonical USDC.

| Chain     | API identifier | Current status                                  |
| --------- | -------------- | ----------------------------------------------- |
| Base      | `base`         | Initial validation chain                        |
| Polygon   | `polygon`      | Configuration-gated                             |
| Arbitrum  | `arbitrum`     | Configuration-gated                             |
| Optimism  | `optimism`     | Configuration-gated                             |
| Avalanche | `avalanche`    | Configuration-gated                             |
| Ethereum  | Not advertised | Requires separate end-to-end readiness approval |
| Solana    | Not supported  | Outside the initial B2B scope                   |

<Warning>Do not assume a chain is live because its identifier is accepted by a schema. Check your environment policy and the applicable readiness endpoint before presenting a route to a customer.</Warning>

## Local payment methods

Beneficiary requirements are dynamic. Request `GET /api/v1/business/beneficiaries/requirements` with the destination currency and payment method before collecting recipient details.

The API models these payment methods:

* `mobile_money`
* `bank_account`
* `buy_goods`
* `paybill`

Availability depends on currency, provider readiness, business policy, and configured transaction limits.