---
title: "Infinite vs Natural: how do they compare?"
description: "How Infinite compares with Natural: compliance model, accounts, rails, settlement, developer surface, and jurisdictions, cited against public documentation."
updated: "2026-08-09"
canonical: "https://infinite.net/resources/learn/insights/compare/infinite-vs-natural"
---

# Infinite vs Natural: how do they compare?

Infinite is the global financial network built on a compliance system of intelligence: one API for dedicated bank accounts at bank partners, payments across SWIFT, US rails, stablecoins, and FX, and network-wide counterparty review. This page compares Infinite and Natural across the criteria below; every cell in Natural’s column was verified against Natural’s own public documentation on August 9, 2026, with its source shown beneath it.

## Comparison

| Criterion | Infinite | Natural |
| --- | --- | --- |
| **Compliance model**: Who runs KYC/KYB, sanctions screening, and transaction monitoring, and whether counterparty review repeats for every relationship. | KYC/KYB, sanctions screening, and ongoing transaction monitoring run under Infinite’s compliance program. Review is network-wide: a counterparty vetted once is vetted for every business on the network. | Natural’s docs state every party must clear KYB for businesses and KYC for individuals, its services agreement states Natural verifies the identity of every party, and its Connect docs state “Natural handles the compliance” for end-customer verification. Agent-initiated transactions run under per agent-customer-pair permissions and limits: a payment over a hold-type limit “isn’t rejected; it holds as an Approval” for the party’s owners or admins, and agent-attributed money-movement calls without an instance identifier are rejected. |
| **Onboarding**: How customers actually get live: who collects what, in whose brand, and how long first-time review takes. | Customers onboard through hosted whitelabel flows in your brand or headless via API: Infinite runs the KYC, KYB, and screening underneath. Full first-time counterparty review closes in 1–2 days, versus the roughly 30 days such review typically takes industry-wide under one-off, per-relationship manual processes. | Onboarding is self-serve (its docs state “Sign up at natural.com/signup and complete onboarding in the dashboard”), branching agent operators to its hosted MCP server and software builders to API credentials. Platforms onboard end customers through hosted invitation flows where Natural handles the customer communication and verification in its hosted interface; review or decision timelines, for business onboarding or end-customer KYC decisions, are not published as of the verification date. |
| **Data access**: What your systems can see about compliance state: review and RFI states, reasons, and the audit trail behind decisions. | Compliance reviews and requests for information are explicit states your systems can query and subscribe to, with webhooks for every state change and every case assembled and documented before an analyst opens it. Decisions are auditable. | A webhook event catalog covers payment and deposit lifecycles plus customer-connection activation, and an approvals endpoint lists held payments with pending and approved statuses and resolution timestamps. Agent actions are attributed via required instance IDs its docs describe as grouping executions for transaction observability (“Every payment is observable and fully auditable”); an endpoint for reading a party’s KYC state and request-for-information states are not described in its public documentation as of the verification date. |
| **Account primitives**: What the customer actually holds: a dedicated bank account, a virtual sub-ledger on a pooled account, or a wallet. | Dedicated demand deposit accounts (DDAs) established at Infinite’s bank partners, unique to each customer with their own account and routing numbers, offered as USD bank accounts and Wallet Accounts (stablecoin custody); a Deposit Account is coming soon. | Customers hold USD wallets, one created automatically per verified party, usable one-per-agent or shared, plus a non-spendable reserve wallet product. Its disclosures state Natural “is a financial technology company, not a bank,” with wallet accounts and banking services provided through a bank partner and deposits described as FDIC-insured on a pass-through basis; payments to recipients not yet on Natural sit in escrow until the recipient onboards. |
| **Rails coverage**: Which payment rails one integration reaches: US bank rails, SWIFT, stablecoins, and FX. | ACH, Fedwire, RTP, SWIFT, and stablecoin transfers (USDC, USDT, OUSD, USDG) from the same account, plus FX across GBP, EUR, MXN, and BRL, with Transfer Routes selecting the rail per corridor. | Its docs enumerate ACH deposits and withdrawals from linked external bank accounts, internal wallet-to-wallet transfers, debit and charge card issuance, and merchant acceptance of cards and bank transfers, with its services agreement defining transaction methods under the ACH, RTP, FedNow, wire, and card network rulebooks. Examples are USD-denominated throughout; stablecoin and FX rails do not appear in its public documentation as of the verification date. |
| **Settlement**: When funds actually arrive, including nights, weekends, and rail cutoffs. | Stablecoin transfers settle 24/7, weekends and bank holidays included. USD payments past the ACH cutoff can route to RTP the same day; most SWIFT wires settle same day to two business days once released. | Its transfer docs state deposits and withdrawals “settle over a few business days, so the balance change is not immediate,” with deposit objects returning an expected-available-at field rather than a fixed window, and conditionally enabled instant withdrawals alongside standard delivery; timing for internal wallet-to-wallet payments is not separately published as of the verification date. Rail-by-rail settlement times and cutoffs are not published as of the verification date. |
| **Developer surface**: The API, webhooks, hosted flows, and dashboard an engineering and operations team works with. | One typed payments API across every rail, webhooks for every state change, hosted onboarding flows (in your brand or headless via API), and an operations dashboard. Developer documentation at docs.infinite.net. | A REST API with a published OpenAPI spec, Python and TypeScript SDKs, a CLI, and a hosted MCP server using browser OAuth that exposes its operations to agent tools including Claude and Codex, plus a docs-search MCP, a sandbox with simulation endpoints, a webhook catalog, and a dashboard its docs describe as “for humans only,” with agent access split between agent-scoped and user-scoped grants. |
| **Jurisdiction coverage**: Where the provider operates and onboards customers, and under what licensing or partner structure. | Businesses onboard from the United States and the further markets listed at infinite.net/solutions/embedded#supported-markets; payments reach further over SWIFT, with local rails in EUR, GBP, MXN, and BRL. Services are not available in OFAC-sanctioned or otherwise restricted countries, and accounts are provided through a bank partner. | The operating entity is Natural AI, Inc., described in its disclosures as a financial technology company, not a bank, with banking services through a bank partner. Its services agreement defines permitted geographies as individuals physically located in the United States or US-located financial instruments, with documentation examples USD-only. |

### Sources

- Infinite, Compliance model: /accounts/managed, /solutions/embedded
- Infinite, Onboarding: /agents/embedded-compliance, /agents/compliance
- Infinite, Data access: docs.infinite.net, /resources/funds-flow/third-party, /agents/compliance
- Infinite, Account primitives: /accounts/managed, /accounts/wallets
- Infinite, Rails coverage: /payments/usd, /payments/stablecoins, /payments/fx, /accounts/routes
- Infinite, Settlement: /payments/stablecoins, /payments/usd, /payments/swift
- Infinite, Developer surface: docs.infinite.net, /accounts/managed, /agents/embedded-compliance
- Infinite, Jurisdiction coverage: /solutions/embedded, /payments/swift, /payments/fx, /accounts/managed
- Natural, Compliance model: docs.natural.com/guides/concepts/parties, docs.natural.com/guides/concepts/agents, natural.com/nsa, docs.natural.com/guides/connect/invite-customer (verified 2026-08-09)
- Natural, Onboarding: docs.natural.com/guides/overview/start-here, docs.natural.com/guides/connect/invite-customer (verified 2026-08-09)
- Natural, Data access: docs.natural.com/guides/controls/approvals, docs.natural.com/guides/concepts/agents, docs.natural.com/guides/products/accept (verified 2026-08-09)
- Natural, Account primitives: docs.natural.com/guides/concepts/wallets, docs.natural.com/guides/products/wallet, natural.com/disclosures (verified 2026-08-09)
- Natural, Rails coverage: docs.natural.com/guides/transfers/deposit-and-withdraw, docs.natural.com/guides/concepts/wallets, natural.com/nsa (verified 2026-08-09)
- Natural, Settlement: docs.natural.com/guides/transfers/deposit-and-withdraw (verified 2026-08-09)
- Natural, Developer surface: docs.natural.com/guides/platform/mcp, docs.natural.com/guides/overview/start-here, docs.natural.com/api-reference/about (verified 2026-08-09)
- Natural, Jurisdiction coverage: natural.com/nsa, natural.com/disclosures (verified 2026-08-09)

Last updated August 9, 2026