Figo API

One API moves money across currencies and crypto. Anything in, anything out. You can take money in as a local currency or as a digital asset. You can send money out as a local currency or as a digital asset.

The source and the destination are fully independent. Thus one request can do a movement that other APIs cannot do in one call. Two examples are naira in with Bitcoin out, and USDT in with euros out.

You work in USD. We operate the local rails, the currency exchange, and the on-chain settlement.

Integrate in minutes

There are three ways in. Select one by how much code you want to write.

{
  "mcpServers": {
    "figo-docs": {
      "type": "http",
      "url": "https://docs.spendfigo.com/mcp"
    }
  }
}

curl https://devapi.spendfigo.com/v1/balance \
  -H "x-api-key: $FIGO_KEY"

curl -X POST https://devapi.spendfigo.com/v1/payment-links \
  -H "x-api-key: $FIGO_KEY" \
  -H "Content-Type: application/json" \
  -d '{"amount": 25, "title": "Design retainer"}'

What you can build

Common shapes: cross-border payroll, marketplace payouts, local-currency checkout with USD settlement, crypto on/off-ramps, and treasury movement between assets.

Orchestrate — anything in, anything out

This is our most important endpoint. Most payment APIs collect in one currency and pay out in the same currency.

Figo makes the two sides independent. Each side is fiat, a local currency, or crypto, any asset on any chain. We connect the two sides for you:

SOURCE  →  ( settled in USD )  →  DESTINATION

One endpoint, every combination. → Orchestrate reference · Recipes

The focused flows

When you need only one side, use the single-purpose endpoints:

• Collect — accept a local currency by bank transfer or mobile money, or accept crypto. We add USD to your balance.
• Virtual accounts — give a customer a permanent account number. The customer can pay into it at any time, and each payment adds to your balance.
• Pay out — send a local currency or crypto to a recipient. We subtract the USD from your balance.
• Track — follow each movement on a clear timeline. You can also get webhook events.

Below all of this, your balance is USD. Money comes in and settles through a stablecoin rail. You never touch that rail. The money then goes out in the form that the destination needs.

This is what makes anything to anything possible, and it keeps the pricing honest. For a crypto side, you work in the exact asset and network. For a fiat side, you work in the local currency.

Start here

1. Getting started — your first successful API call in under five minutes.
2. Authentication — API keys, environments, and headers.
3. Conventions — response envelope, pagination, idempotency, and errors. Read once; it applies to every endpoint.
4. The money model — how corridors, balances, and settlement fit together. The mental model that makes the rest obvious.
5. Transaction lifecycle — stages, statuses, and the progress timeline you render to your users.

Are you new here? The Recipes give complete flows for the most common movements. Build with AI shows you how to connect the API to an agent.

The interactive reference is at /api-reference. There you can send requests to sandbox from your browser.

API reference

Base URLs & dashboard

All endpoints live under the /v1 prefix. Start in sandbox — test keys (sk_test_…) move no real money.

Your balance is USD

We show all amounts and fees in USD. A fiat side also shows the local currency that your customer pays or receives. A crypto side shows the exact asset and network that you selected. We hide nothing.