Cowrie Research

nilos

4 min read

Nilos

  • Name: Nilos SAS
  • URL: https://www.nilos.io/
  • Category: cross-border payments operating company / emerging-markets treasury-and-FX control plane / stablecoin-enabled collection-and-payout operator
  • Summary: Nilos belongs in companies/ because the analytically useful surface is not a neutral cross-border payments protocol. One named operator packages multi-currency collection accounts, FX conversion, local payout rails, mobile-money connectivity, stablecoin-enabled liquidity, KYB onboarding, safeguarded-funds partnerships, API-key issuance, HMAC-signed request workflow, and support/compliance handling into one inherited operating shell. There is no especially useful standalone Nilos protocol doing separate control-surface work here; the live dependency is the company-managed money-movement stack and the jurisdictions, counterparties, and approval workflow around it.
  • What it does:
    • Operates a single integration surface for multi-currency collection accounts, FX conversion, local and cross-border payouts, and stablecoin-enabled treasury workflows
    • Packages local bank-transfer and e-wallet collection without requiring customers to open separate overseas bank accounts for each corridor
    • Connects banking rails and mobile-money rails across emerging-market-heavy payout corridors while marketing same-day settlement in most cases
    • Uses stablecoins as a liquidity mechanism inside a broader cross-border payment and treasury product rather than as the only product surface
    • Exposes a sandbox dashboard, API-key issuance, and HMAC-signed request flow for account and payment operations
    • Provides the legal and compliance shell around onboarding, KYB approval, safeguarded funds, liquidity access, and support escalation
  • Key claims:
    • The homepage says Nilos is the complete stack for cross-border money movement and that businesses can collect, convert, and pay out through a single integration while Nilos handles liquidity, compliance, and local rail connectivity
    • The homepage says Nilos supports payments in 120+ countries across Africa, LATAM, Asia, Europe, and North America, with most transactions settling same-day
    • The homepage says the infrastructure is SOC 2 Type II audited, licensed by the AMF in France, registered with FINTRAC in Canada as a Money Services Business, and uses Modulr Finance B.V. as the safeguarded-funds partner in Europe
    • The company page says Nilos is using stablecoins as a liquidity mechanism to make cross-border payments in emerging markets faster, more transparent, and more accessible
    • The API docs say integrations start in the Nilos Sandbox Dashboard, require API-key creation, and authenticate through HMAC signatures passed in X-Api-Key and X-Api-Signature headers
    • The homepage FAQ says account opening runs through Nilos compliance review and KYB approval, and that every account gets a dedicated account manager plus direct support from the integration team, which is unusually explicit evidence that the company workflow is the product boundary
  • Whitepaper: No standalone company whitepaper is the point here. The strongest primary materials are the homepage, company page, product pages, and API docs already captured in ../whitepapers/nilos-primary-sources-2026-04-30.md.
  • Sources:

Internal linkages

  • Project-layer alias: nilos.
  • Useful adjacent operator comparisons: openpayd, transfi, and bvnk.
  • Useful treasury-and-settlement contrast where programmable workflow matters but the fiat shell is broader and more enterprise-centric: modern-treasury.

Protocol / company boundary

  • There is no especially useful standalone Nilos protocol doing separate analytical work from the company-managed product shell.
  • The stronger lower layers are external payment rails, banking partners, mobile-money integrations, FX counterparties, and stablecoin liquidity rails rather than a proprietary shared protocol others independently operate.
  • Keep this note on the named operator that admits customers, runs compliance and KYB workflow, packages the account and payout surface, decides corridor and partner exposure, and publishes the API-and-support shell users actually inherit.
  • That split matters because how do Nilos account and payment flows work? and which company controls who gets access, under what compliance terms, with which rail and settlement assumptions? are related but not identical questions.

Control surface

  • Practical leverage sits in customer admission and KYB approval, supported-country and rail coverage, liquidity and FX partner selection, dashboard and API-key issuance, authentication workflow, safeguarded-funds and regulated-partner composition, payout timing, and support/escalation handling.

  • The sticky dependency is not one API route. It is that one named company normalizes account opening, corridor availability, conversion, local payout connectivity, stablecoin-assisted liquidity, and compliance review into a single operating perimeter.

  • Treat Nilos as a cross-border payments operating company first. The branded product surface matters, but the more durable authority sits in the company boundary that decides access, workflow, and partner composition.

  • Last reviewed: 2026-08-12 UTC

Graph View

Backlinks