Borderless: stablecoin payments orchestration API

Borderless (borderless.xyz, docs at docs.borderless.xyz) is a stablecoin payments orchestration network. You integrate one HTTP API; they connect that traffic to regulated partner financial institutions (PFIs) that run local on-ramps and off-ramps. Marketing cites 14+ providers, 95+ countries, and 63+ currencies — treat coverage tables in docs as the source of truth for any corridor you ship.

The design choice that matters for compliance and treasury: Borderless is not in the flow of funds and does not take custody. It is a gateway. Settlement and licensing sit with the PFIs you enable (Bridge, Bitso, Walapay, Yellowcard, Cobre, Infinia, and others listed on their network page).

Click to zoom

Products

Object model

Integration order in the quick start is deliberate. You cannot jump straight to payouts without the parent objects.

Accounts can wrap existing blockchain addresses. Docs describe generating withdrawal instructions and pre-built transaction payloads that you broadcast with your own wallet infrastructure — Borderless does not hold the keys. Asset labels in examples look like USDC_BASE, USDC_POLYGON; confirm Solana asset codes in the live API/catalog for your org (coverage is PFI- and corridor-specific).

Authentication

Access is not self-serve for production. Request onboarding (docs point at [email protected]). After invite, create API keys in the dashboard Developers section, then exchange client id/secret for an M2M access token (OAuth 2.0). Endpoints expect Authorization: Bearer …. Webhooks are signed.

curl -X POST "https://sandbox-api.borderless.xyz/v1/auth/m2m/token" \
  -H "Content-Type: application/json" \
  -d '{
    "clientId": "your-client-id",
    "clientSecret": "your-client-secret"
  }'
# → { "accessToken", "tokenType": "Bearer", "expiresIn": 3600 }

Many mutating routes require an Idempotency-Key header (UUID). Reuse the same key only for safe retries of the same operation.

Integration path

Sandbox base URL used in docs: https://sandbox-api.borderless.xyz. There is a dedicated sandbox testing guide under Developer Guides.

PFI integrations

The API reference includes a large integrations-config surface: Bridge, Bitso, Brale, Capa, Cobre, Dfns, Finity, Infinia, Koywe, Trace Finance, Walapay, Yellowcard, Utila, and more. Older one-endpoint-per-provider setup routes still exist; docs also describe a consolidated credentials endpoint that replaces the long list over time. Organization “network defaults” pick default PFIs per country and operation type.

When this fits (and when it does not)

Compared with single-provider APIs (e.g. one Bridge-only integration), Borderless is the multi-PFI control plane. Compared with a pure Solana payments stack (Solana Pay, local USDC transfer), Borderless is about fiat corridors and licensed partners, not replacing on-chain settlement between wallets.

Resources

• docs.borderless.xyz · llms.txt
• Quick start · Auth · Coverage
• Product site · Benchmark
• DevRels organisation

Summary

Borderless is a multi-provider stablecoin on/off-ramp gateway with a single REST surface: OAuth M2M tokens, identities, accounts, payment instructions, and transactions. Funds stay with licensed PFIs and your own wallets. Start at the quick start, confirm corridor coverage and PFI credentials for the countries you need, then wire webhooks and idempotency before production volume.