# insimbi insimbi curates the right transaction, rails and record for every value movement, whether fiat, stablecoins, markets or tokens. For US enterprise merchants: you set the rules for routing, payouts and pricing, see every fee and every decision, and keep your data. Built for: Payments & finance leaders (/pricing/#finance); Engineering & platform leads (/developers/#platform); Operations leads (/product/#operations) ## The right rails. The right record. insimbi curates the right transaction, rails and record for every value movement, whether fiat, stablecoins, markets or tokens. For US enterprise merchants. You set the rules. You see every fee and why each payment went where it did. ## Every value movement Six kinds of value movement. Market figures from public sources, not insimbi's own numbers. Forecasts are marked. ### Fi Fiat · cards - **$11.903 trillion** spent with US-issued credit, debit and prepaid cards in 2024. Source: [The Nilson Report, March 2025](https://www.globenewswire.com/news-release/2025/03/19/3045828/0/en/merchant-processing-fees-in-the-united-states-exceeded-187-billion-in-2024.html) - **$187.20 billion** in processing fees paid by US merchants to accept card payments in 2024. Source: [The Nilson Report, March 2025](https://www.globenewswire.com/news-release/2025/03/19/3045828/0/en/merchant-processing-fees-in-the-united-states-exceeded-187-billion-in-2024.html) ### Sc Stablecoins - **$320 billion** stablecoin market capitalization, around this level as of end-May 2026. Source: [BIS Annual Economic Report, June 2026](https://www.bis.org/publ/arpdf/ar2026e3.htm) - **$28 trillion** estimated stablecoin transaction volume in 2025. Raw figure: the BIS notes volume net of transfers between a party's own wallets is far lower. Source: [BIS Annual Economic Report, June 2026](https://www.bis.org/publ/arpdf/ar2026e3.htm) ### Mk Markets - **15.3 billion** listed options and futures contracts cleared by OCC in 2025, a record. Source: [OCC 2025 Annual Report](https://annualreport.theocc.com/2025/a-message-from-leadership) ### Tk Tokens - **$39.11 billion** distributed value of tokenized real-world assets onchain, excluding stablecoins, as of Oct 13, 2026. Source: [RWA.xyz dashboard, as of Oct 13, 2026](https://app.rwa.xyz/) ### Mm Machine & agentic - **$3 trillion to $5 trillion** (forecast) of global consumer goods commerce that AI agents could mediate by 2030, under moderate assumptions. Source: [McKinsey, The agentic commerce opportunity, October 2025](https://www.mckinsey.com/capabilities/quantumblack/our-insights/the-agentic-commerce-opportunity-how-ai-agents-are-ushering-in-a-new-era-for-consumers-and-merchants) ### Vs Value-added services - **$10.9 billion** revenue from value-added services at one card network, Visa, in fiscal 2025. Source: [Visa Inc. Form 10-K, fiscal 2025](https://www.sec.gov/Archives/edgar/data/1403161/000140316125000089/v-20250930.htm) More on cards: - **$1.57** in fees for every $100 in card payments merchants accepted in 2024. Source: [The Nilson Report, March 2025](https://www.globenewswire.com/news-release/2025/03/19/3045828/0/en/merchant-processing-fees-in-the-united-states-exceeded-187-billion-in-2024.html) - **$34.12 billion** in interchange fees across all US debit and general-use prepaid card transactions in 2023. Source: [Federal Reserve Board, Regulation II data, 2023](https://www.federalreserve.gov/paymentsystems/2023-interchange-fee.htm) ## You can't see how your money moves. Most merchants can't see how their money moves. Fees are blended. Holds aren't chosen. Routing can't be inspected. insimbi picks the right transaction and rails for each movement, keeps the record, and shows you why. ## Four controls. You set each one. Turn a control off and watch the simulated payments change. - **Route**: Choose where each transaction goes. - **Pay out**: Choose when money lands. - **Price**: See every fee, line by line. - **Own**: Export your data, any time. | line | amount | |---|---| | authorization | gross amount | | network fee | at cost, itemized | | insimbi fee | our fee, itemized | | settled to you | net, on your schedule | ## Readable by people and by agents. Every page here also exists as markdown. Agents can read /llms.txt, follow /agents.md and use the API, with the same controls you have. ## Move one rule at a time. Connect, mirror, move. Run both setups side by side. Shift traffic by rule, and roll back in one step. ## What we can show you, and when. Procurement will ask. We list certifications, audit reports and uptime commitments only once they are real and audited. | item | status | |---|---| | PCI DSS | published once audited | | SOC 2 | published once audited | | Uptime SLA | published once contracted | | Trust documents | on request | ## Request access. Tell us how your payments run today. We will show you what you control with insimbi. ## Umuntu ngumuntu ngaBantu. It means a person is a person through other people. We think payments work the same way: a payment only completes when every party does its part. Our ring is drawn as iridium, the most corrosion-resistant metal known. We chose it on purpose. Payments should not corrode. Iridium is one of the rarest elements on Earth. South Africa mines about 80% of the world's supply, and the Bushveld Complex holds the largest reserves of the platinum-group metals it comes from. Source: [Royal Society of Chemistry, Periodic Table: Iridium](https://periodic-table.rsc.org/element/77/iridium) · Source: [International Platinum Group Metals Association, Iridium factsheet, March 2026](https://ipa-news.com/assets/pdfs/factsheets/2026-03-iridium-factsheet.pdf) Ask insimbi: open the command bar with ⌘K / Ctrl+K. --- # Product The right transaction, rails and record. Seven pillars, one ledger. Every value movement needs three choices: the transaction, the rails and the record. insimbi makes those choices by your rules, and shows you each one. Seven pillars cover every kind of value movement. One record sits under all of them. 1. **Transaction**: What is being paid for, by whom, under which mandate. 2. **Rails**: Which network, bank rail or chain carries it, chosen by your rule. 3. **Record**: One ledger line with its fees, its rule and its reconciliation. ### [Fe The record](/product/record/) One ledger under every movement. ### [Fi Fiat and cards](/product/fiat/) Accept, route and pay out across cards and bank rails. ### [Sc Stablecoins](/product/stablecoins/) Dollar stablecoins as one more rail, on the same record. ### [Mk Markets](/product/markets/) Funding and settlement for regulated venues. ### [Tk Tokens](/product/tokens/) Money in and out of tokenized assets. ### [Mm Machine and agentic](/product/agentic/) Let agents pay, inside limits you set. ### [Vs Value-added services](/product/value-added/) The extras, itemized and optional. ## Four controls across every pillar - [Routing](/product/routing/): Choose where each transaction goes. - [Payouts](/product/payouts/): Choose when money lands. - [Fee visibility](/product/pricing/): See every fee, line by line. - [Data](/product/data/): Export everything, any time. ## For operations leads Disputes, refunds, payouts and exceptions sit in one queue. Each item shows the rule that caused it. You don't need a support ticket to learn why money moved. - **Exception queue**: Disputes, refunds and failed payouts in one list. - **Rule attached**: Each exception shows the rule behind it. - **Payout reconciliation**: Each settlement is matched to its transactions. - **Audit log**: Who changed what, when, and what it touched. ## See it in a scenario Illustrative scenarios show how the pillars combine for a type of business. - [Use cases](/use-cases/): Eight illustrative scenarios, from marketplaces to agents. Request access: sales@insimbi.net _insimbi is in early access with design partners._ --- # Routing You choose where each transaction goes. Write the rules: by card type, region, amount or time. insimbi runs them across your processors and networks. You see which rule sent each transaction where. --- # Payouts You choose when money lands. Set when and where money lands, per account and per currency. The schedule is yours, and it is written down. --- # Fee visibility Every fee, line by line. Every transaction comes with its own fee lines: network, scheme and ours. Nothing is blended or rounded away. --- # Data Your data. Export it any time. Raw events, settlements and fees, streamed or exported. If you leave, your data leaves with you. --- # The record One ledger under every movement. Every payment, payout, fee and decision lands in one record. Finance, operations and auditors read the same lines. This is the base the other pillars build on. ## Capabilities - **Decision trace**: Every payment shows the rule that sent it where it went. - **Fee lines**: Network, scheme and insimbi fees, itemized per transaction. - **Reconciliation**: Each settlement row matched to the transactions behind it. - **Exception queue**: Disputes, refunds and failed payouts in one list, each with its rule. - **Search and export**: Find any record. Export it as a file, on request. - **Audit log**: Who changed what, when, and what it touched. - **Double-entry ledger**: Fiat, stablecoin and token balances in one set of books. - **Data streaming**: Raw events, settlements and fees into your warehouse. ## Protocols and standards Supports: ISO 20022, Double-entry accounting, CSV, Parquet and webhooks ## In a scenario - [A marketplace paying sellers in dollars and stablecoins](/use-cases/marketplace-payouts/): Illustrative scenario. - [An agent paying for API calls, one request at a time](/use-cases/agent-api-payments/): Illustrative scenario. - [A procurement agent buying from suppliers](/use-cases/procurement-agent/): Illustrative scenario. - [A retailer taking control of card costs](/use-cases/retailer-routing/): Illustrative scenario. - [An insurer paying claims on the fastest sensible rail](/use-cases/insurer-claims/): Illustrative scenario. - [A software platform billing people and agents](/use-cases/software-platform-billing/): Illustrative scenario. Related: [Fee visibility](/product/pricing/) · [Data](/product/data/) --- # Fiat and cards Accept, route and pay out across cards and bank rails. Cards and bank transfers carry most US commerce today. You choose the route for each transaction and see the cost of each choice. ## Capabilities - **Routing rules**: Rules by card type, region, amount or time. Reviewable and reversible. - **Debit network choice**: Send eligible debit to the network your rules pick. - **Multi-processor acceptance**: Run more than one acquirer behind one integration. - **Network tokens**: Store tokens, not card numbers. - **Bank payouts**: ACH, same-day ACH and instant bank rails, per account. - **Payout cutoffs**: See the next settlement window before it closes. - **Parallel run**: Mirror live traffic next to your current setup and compare each payment. ## Protocols and standards Supports: Visa and Mastercard, EMV 3-D Secure, Network tokens, ACH and Same Day ACH, RTP, FedNow, Fedwire (ISO 20022) ## In a scenario - [A marketplace paying sellers in dollars and stablecoins](/use-cases/marketplace-payouts/): Illustrative scenario. - [A procurement agent buying from suppliers](/use-cases/procurement-agent/): Illustrative scenario. - [A retailer taking control of card costs](/use-cases/retailer-routing/): Illustrative scenario. - [An insurer paying claims on the fastest sensible rail](/use-cases/insurer-claims/): Illustrative scenario. - [A software platform billing people and agents](/use-cases/software-platform-billing/): Illustrative scenario. Related: [Routing](/product/routing/) · [Payouts](/product/payouts/) · [Switch](/switch/) --- # Stablecoins Dollar stablecoins as one more rail, on the same record. Stablecoins settle around the clock. insimbi treats them as a rail you can choose per movement, delivered through regulated partners, with the same fee lines and record as a card or a bank transfer. ## Capabilities - **Stablecoin acceptance**: Take regulated dollar stablecoins at checkout or on invoice, through regulated partners. - **Stablecoin payouts**: Pay sellers, suppliers or partners in stablecoins, by rule. - **Convert to dollars**: Settle to your bank in USD through regulated partners. - **Chain choice**: Pick the network per payout by cost and speed. - **Wallet screening**: Screen counterparties before money moves. - **Unified balances**: Fiat and stablecoin balances in one view. - **Around-the-clock settlement**: Settle on weekends and holidays, not just banking hours. - **Mint and redeem**: Move between dollars and stablecoins at par through regulated partners. - **Stablecoin treasury**: Hold, sweep and rebalance stablecoin balances by rule. ## Protocols and standards Supports: USDC, USDT, PYUSD, Ethereum, Solana, Base, Tron, ERC-20 ## In a scenario - [A marketplace paying sellers in dollars and stablecoins](/use-cases/marketplace-payouts/): Illustrative scenario. - [An agent paying for API calls, one request at a time](/use-cases/agent-api-payments/): Illustrative scenario. - [An event-contract venue settling winners](/use-cases/prediction-market-settlement/): Illustrative scenario. - [A tokenized fund taking subscriptions and paying redemptions](/use-cases/tokenized-fund/): Illustrative scenario. - [An insurer paying claims on the fastest sensible rail](/use-cases/insurer-claims/): Illustrative scenario. Related: [Payouts](/product/payouts/) --- # Markets Funding and settlement for regulated venues. Exchanges, brokers and event-contract venues move customer money in and out all day. insimbi funds accounts fast and settles them correctly, with a record that holds up to review. ## Capabilities - **Account funding**: Fund customer accounts by card, bank or stablecoin. - **Settlement payouts**: Pay out after a contract resolves, on the rail the customer picked. - **Segregated balances**: Customer funds and house funds kept apart in the record. - **Cutoff preview**: See which payouts make the next window. - **Withdrawal rules**: Limits, holds and reviews you set and can explain. - **Instant withdrawals**: Pay out to debit cards, instant bank rails or stablecoin wallets around the clock. - **Venue connectivity**: Connect to regulated exchange and event-contract venue APIs for funding and settlement instructions. - **Trade-to-cash matching**: Match every fill, resolution and fee to the cash that moved. - **Customer funds statements**: Daily segregated-funds reports your compliance team can file. ## Protocols and standards Supports: FIX, CFTC-regulated venue APIs, ACH, RTP and FedNow, USDC ## In a scenario - [An event-contract venue settling winners](/use-cases/prediction-market-settlement/): Illustrative scenario. Related: [Payouts](/product/payouts/) --- # Tokens Money in and out of tokenized assets. Tokenized funds and assets still need cash to come in and go out. insimbi takes subscriptions and pays redemptions and distributions in dollars or stablecoins, and matches them to the asset's records. ## Capabilities - **Subscriptions**: Take subscriptions by wire, ACH or stablecoin. - **Redemptions**: Pay redemptions on the rail the holder picked. - **Distributions**: Pay yield or dividends to many holders in one run. - **Register matching**: Match each cash movement to the asset register. - **Holder screening**: Check eligibility before money moves. - **Permissioned token support**: Work with tokens that enforce transfer rules onchain. - **Cross-chain movements**: Move tokenized assets and their cash legs across chains with one record. - **Around-the-clock settlement**: Subscribe and redeem at any hour in stablecoins. - **Investor statements**: Holdings, cash movements and distributions per investor. ## Protocols and standards Supports: ERC-20, ERC-3643, Chainlink CCIP, Ethereum, Solana, USDC, PYUSD ## In a scenario - [A tokenized fund taking subscriptions and paying redemptions](/use-cases/tokenized-fund/): Illustrative scenario. Related: [Data](/product/data/) --- # Machine and agentic Let agents pay, inside limits you set. Software agents now buy things and pay for services. With insimbi, an agent acts for one principal, within one mandate, and every payment it makes lands in the same record. ## Capabilities - **Agent-readable docs**: Every page as markdown, plus llms.txt and agents.md. - **Scoped API access**: Credentials limited to one principal and one scope. - **Agent mandates**: Bind an agent to a principal, a spend limit and a scope. - **Payment intent preview**: Check a request against the mandate before it runs. - **Tool interface for agents**: MCP tools so agents work with insimbi directly. - **Per-request payments**: Charge or pay per API call over HTTP 402, in fiat or stablecoins. - **Agent card credentials**: Single-use or limited card credentials for agent purchases. - **Agent protocols**: Accept agent checkouts over AP2 and ACP, verify agents with network agent programs. ## Protocols and standards Supports: MCP, Agent Payments Protocol (AP2), Agentic Commerce Protocol (ACP), x402, Visa Intelligent Commerce, Visa Trusted Agent Protocol, Mastercard Agent Pay, Machine Payments Protocol (MPP), Universal Commerce Protocol (UCP) ## In a scenario - [An agent paying for API calls, one request at a time](/use-cases/agent-api-payments/): Illustrative scenario. - [A procurement agent buying from suppliers](/use-cases/procurement-agent/): Illustrative scenario. - [A software platform billing people and agents](/use-cases/software-platform-billing/): Illustrative scenario. Related: [Developers](/developers/) --- # Value-added services The extras, itemized and optional. Fraud tools, account updates and cost modelling add value when you can see what each one costs and turn it off. Each service is a line item. ## Capabilities - **Cost modelling**: Preview a routing or payout change before you make it. - **Fraud signals**: Bring your own fraud tools or use partners, scored per payment. - **Card account updates**: Keep stored cards current. - **Dispute handling**: Evidence and deadlines in the exception queue. - **Onboarding review**: Review a business, its owners and its agents in one place. - **Authentication**: Run 3-D Secure only when your rules or the issuer need it. - **Payee tax forms**: Collect payee tax details and produce year-end forms for payouts. - **Cross-border FX**: Show the rate and the spread as their own lines. ## Protocols and standards Supports: EMV 3-D Secure, Network tokens, Card account updater services ## In a scenario - [A retailer taking control of card costs](/use-cases/retailer-routing/): Illustrative scenario. - [A software platform billing people and agents](/use-cases/software-platform-billing/): Illustrative scenario. Related: [Pricing](/pricing/) --- # Use cases Illustrative scenarios. How the pillars fit together. **Illustrative scenario.** A fictional type of business, not a customer. No results are claimed. Each scenario describes a fictional type of business, not a customer. It shows the problem and how insimbi handles the transaction, rails and record. - [A marketplace paying sellers in dollars and stablecoins](/use-cases/marketplace-payouts/): Fi + Sc - [An agent paying for API calls, one request at a time](/use-cases/agent-api-payments/): Mm + Sc - [A procurement agent buying from suppliers](/use-cases/procurement-agent/): Mm + Fi - [An event-contract venue settling winners](/use-cases/prediction-market-settlement/): Mk + Sc - [A tokenized fund taking subscriptions and paying redemptions](/use-cases/tokenized-fund/): Tk + Sc - [A retailer taking control of card costs](/use-cases/retailer-routing/): Fi + Vs - [An insurer paying claims on the fastest sensible rail](/use-cases/insurer-claims/): Fi + Sc - [A software platform billing people and agents](/use-cases/software-platform-billing/): Mm + Fi + Vs Request access: sales@insimbi.net _insimbi is in early access with design partners._ --- # A marketplace paying sellers in dollars and stablecoins A US marketplace with 40,000 sellers, some in the US and some abroad. **Illustrative scenario.** A fictional type of business, not a customer. No results are claimed. ## The problem Sellers want to be paid on their own terms. US sellers want next-day bank deposits. Sellers abroad wait days for wires and lose money on conversion. Finance can't see what each payout really costs. ## Value anatomy 1. **Transaction**: Buyers pay by card. Each order splits into the seller's share and the marketplace fee. 2. **Rails**: A payout rule picks the rail per seller: same-day ACH for US sellers, a dollar stablecoin for sellers who ask for it. 3. **Record**: Every payout carries its fee lines and the rule that chose the rail. Each settlement reconciles to its orders. ## What it uses - **Routing rules**: Rules by card type, region, amount or time. Reviewable and reversible. - **Bank payouts**: ACH, same-day ACH and instant bank rails, per account. - **Stablecoin payouts**: Pay sellers, suppliers or partners in stablecoins, by rule. - **Wallet screening**: Screen counterparties before money moves. - **Fee lines**: Network, scheme and insimbi fees, itemized per transaction. - **Reconciliation**: Each settlement row matched to the transactions behind it. Request access: sales@insimbi.net _insimbi is in early access with design partners._ --- # An agent paying for API calls, one request at a time A US data provider selling an API, and the AI agents that call it. **Illustrative scenario.** A fictional type of business, not a customer. No results are claimed. ## The problem Agents need data now, not after a sales call and a monthly invoice. API keys and invoices don't fit software that buys on its own. The provider needs to know who is paying and to stop runaway spend. ## Value anatomy 1. **Transaction**: The API answers an unpaid request with a price. The agent's mandate allows it, so it pays and retries. 2. **Rails**: Small payments settle in a dollar stablecoin, or batch onto a card when the buyer prefers. 3. **Record**: Each call, its price and the mandate that allowed it land in one line. The buyer and the provider see the same record. ## What it uses - **Per-request payments**: Charge or pay per API call over HTTP 402, in fiat or stablecoins. - **Agent mandates**: Bind an agent to a principal, a spend limit and a scope. - **Payment intent preview**: Check a request against the mandate before it runs. - **Scoped API access**: Credentials limited to one principal and one scope. - **Fee lines**: Network, scheme and insimbi fees, itemized per transaction. Request access: sales@insimbi.net _insimbi is in early access with design partners._ --- # A procurement agent buying from suppliers A US manufacturer that lets an AI agent reorder parts from approved suppliers. **Illustrative scenario.** A fictional type of business, not a customer. No results are claimed. ## The problem The agent can find the best price, but finance won't hand it a corporate card. Every purchase needs a limit, a supplier list and a trail an auditor can follow. ## Value anatomy 1. **Transaction**: The agent proposes an order. insimbi checks it against the mandate: supplier, amount, category. 2. **Rails**: An approved order is paid with a single-use card credential, or by bank transfer for suppliers that invoice. 3. **Record**: Each purchase is tied to the agent, the person it acts for and the mandate. Refunds and disputes go to the exception queue. ## What it uses - **Agent mandates**: Bind an agent to a principal, a spend limit and a scope. - **Agent card credentials**: Single-use or limited card credentials for agent purchases. - **Payment intent preview**: Check a request against the mandate before it runs. - **Exception queue**: Disputes, refunds and failed payouts in one list, each with its rule. - **Audit log**: Who changed what, when, and what it touched. Request access: sales@insimbi.net _insimbi is in early access with design partners._ --- # An event-contract venue settling winners A US regulated event-contract venue with retail customers. **Illustrative scenario.** A fictional type of business, not a customer. No results are claimed. ## The problem Customers fund accounts at all hours and expect winnings fast when a contract resolves. Customer money must stay separate from the venue's own. Every withdrawal needs a reason on file. ## Value anatomy 1. **Transaction**: Customers fund by debit card, bank transfer or stablecoin. Funds land in segregated customer balances. 2. **Rails**: When a contract resolves, payouts go out on the rail each customer picked, inside the venue's withdrawal rules. 3. **Record**: Each payout links to the contract, the resolution and the rule that released it. ## What it uses - **Account funding**: Fund customer accounts by card, bank or stablecoin. - **Segregated balances**: Customer funds and house funds kept apart in the record. - **Settlement payouts**: Pay out after a contract resolves, on the rail the customer picked. - **Withdrawal rules**: Limits, holds and reviews you set and can explain. - **Cutoff preview**: See which payouts make the next window. Request access: sales@insimbi.net _insimbi is in early access with design partners._ --- # A tokenized fund taking subscriptions and paying redemptions A US asset manager running a tokenized short-term Treasury fund for qualified investors. **Illustrative scenario.** A fictional type of business, not a customer. No results are claimed. ## The problem Investors want to subscribe and redeem in stablecoins as well as dollars, at any hour. Operations must match every cash movement to the token register and check every holder's eligibility. ## Value anatomy 1. **Transaction**: An investor subscribes by wire or stablecoin. insimbi checks eligibility before accepting funds. 2. **Rails**: Redemptions and distributions go out in dollars or stablecoins, per holder instruction. 3. **Record**: Each cash movement matches to a register entry. Mismatches go to the exception queue. ## What it uses - **Subscriptions**: Take subscriptions by wire, ACH or stablecoin. - **Redemptions**: Pay redemptions on the rail the holder picked. - **Distributions**: Pay yield or dividends to many holders in one run. - **Register matching**: Match each cash movement to the asset register. - **Holder screening**: Check eligibility before money moves. Request access: sales@insimbi.net _insimbi is in early access with design partners._ --- # A retailer taking control of card costs A US omnichannel retailer with stores and an online shop. **Illustrative scenario.** A fictional type of business, not a customer. No results are claimed. ## The problem Card fees arrive as one blended number. Nobody can say why a payment went to one processor and not another, or what debit routing would save. ## Value anatomy 1. **Transaction**: Card payments run through rules the retailer writes: by card type, channel and amount. 2. **Rails**: Eligible debit goes to the network the rules choose. A second acquirer takes a share of traffic in a parallel run. 3. **Record**: Every payment shows its route, its rule and its fee lines, so finance can model the next change before making it. ## What it uses - **Routing rules**: Rules by card type, region, amount or time. Reviewable and reversible. - **Debit network choice**: Send eligible debit to the network your rules pick. - **Multi-processor acceptance**: Run more than one acquirer behind one integration. - **Parallel run**: Mirror live traffic next to your current setup and compare each payment. - **Cost modelling**: Preview a routing or payout change before you make it. - **Fee lines**: Network, scheme and insimbi fees, itemized per transaction. Request access: sales@insimbi.net _insimbi is in early access with design partners._ --- # An insurer paying claims on the fastest sensible rail A US property insurer paying claims to policyholders and repair shops. **Illustrative scenario.** A fictional type of business, not a customer. No results are claimed. ## The problem Claimants wait for checks. Some want money in minutes, others are fine with a bank transfer. Each claim payment needs a clear trail for the regulator. ## Value anatomy 1. **Transaction**: An approved claim creates a payout instruction with the payee and amount. 2. **Rails**: A payout rule picks the rail: instant bank payment where supported, ACH otherwise, a stablecoin for payees who ask. 3. **Record**: Each payout links to the claim, the rail chosen and why. Returns land in the exception queue. ## What it uses - **Bank payouts**: ACH, same-day ACH and instant bank rails, per account. - **Stablecoin payouts**: Pay sellers, suppliers or partners in stablecoins, by rule. - **Payout cutoffs**: See the next settlement window before it closes. - **Exception queue**: Disputes, refunds and failed payouts in one list, each with its rule. - **Reconciliation**: Each settlement row matched to the transactions behind it. Request access: sales@insimbi.net _insimbi is in early access with design partners._ --- # A software platform billing people and agents A US software company selling seats to people and usage to AI agents. **Illustrative scenario.** A fictional type of business, not a customer. No results are claimed. ## The problem Seats bill monthly by card. Agent usage arrives in millions of tiny calls. Today these sit in two systems that never agree. ## Value anatomy 1. **Transaction**: Seats renew by card. Agent usage is metered per call against each agent's mandate. 2. **Rails**: Cards for seats. Per-request payments in fiat or stablecoins for agent usage. 3. **Record**: Both streams land in one ledger, by customer, so revenue and fees reconcile in one place. ## What it uses - **Per-request payments**: Charge or pay per API call over HTTP 402, in fiat or stablecoins. - **Agent mandates**: Bind an agent to a principal, a spend limit and a scope. - **Card account updates**: Keep stored cards current. - **Fee lines**: Network, scheme and insimbi fees, itemized per transaction. - **Data streaming**: Raw events, settlements and fees into your warehouse. Request access: sales@insimbi.net _insimbi is in early access with design partners._ --- # Developers One API, for your team and your agents. Anything you can do in the dashboard, you can do through the API. Every page on this site also exists as markdown: add .md to the address. ## For engineering and platform leads Routing rules are code. You can review them, diff them and roll them back. ``` curl https://api.insimbi.net/v1/routes \ -H "Authorization: Bearer $INSIMBI_KEY" # endpoint not final ``` The API reference, SLAs and SDK list are shared with customers. To request access, write to sales@insimbi.net. ## Readable by agents - [llms.txt](/llms.txt): An index of this site for language models. - [llms-full.txt](/llms-full.txt): Every page in one file. - [agents.md](/agents.md): Instructions written for agents. --- # Changelog What changed, and when. ``` 2026-10 insimbi.net: seven product pillars, illustrative use cases, value anatomy, Request access 2026-10 insimbi.net: polish pass: real 404, sitemap, link previews, clickable contact links, sourced origin note 2026-10 insimbi.net: copy rewritten in plain language 2026-10 insimbi.net v2: segment market figures with sources, mobile navigation, full-width layout ``` --- # Pricing Fees you can read before you sign. We will publish our pricing. Every transaction shows its own fees: network, scheme and ours. Nothing is blended. - **Card-present**: on request - **Card-not-present**: on request - **Payouts**: on request - **Platform fee**: on request - **Contract term**: on request - **Volume tiers**: on request **Rates on request. Request access: sales@insimbi.net** ## For payments and finance leaders See what each transaction costs by network, region and route. Model a routing change before you make it. Your auditors see the same ledger you do. - Effective rate by network, region and route - Cost-model export Enterprise terms: sales@insimbi.net. --- # Switch Move at your own pace. Roll back any time. There is no big-bang migration. You run insimbi next to your current setup and move traffic one rule at a time. 1. Connect: bring in your current configuration. 2. Mirror: run live traffic through both and compare the cost and outcome of each transaction. 3. Move: shift traffic by rule, one region, card type or percent at a time. Roll back in one step. 4. Own: end the old contract when the numbers say so. To plan a parallel run, write to sales@insimbi.net. --- # Customers Merchants who run their own payments. We publish a customer story only when the customer approves it. Until then, there are no quotes and no numbers here. --- # Company We curate the right transaction, rails and record for every value movement. - **About**: We curate the right transaction, rails and record for every value movement: fiat, stablecoins, markets or tokens. Built for US enterprise merchants. - **Contact**: sales@insimbi.net ## Origin > Umuntu ngumuntu ngaBantu. insimbi is isiZulu for iron. Umuntu ngumuntu ngaBantu means a person is a person through other people. We think payments work the same way. A payment only completes when every party does its part. A merchant should get stronger through its network, not more dependent on a middleman. Our ring is drawn as iridium, the most corrosion-resistant metal known. We chose it on purpose: payments should not corrode. Iridium is one of the rarest elements on Earth. South Africa mines about 80% of the world's supply, and the Bushveld Complex holds the largest reserves of the platinum-group metals it comes from. Source: [Royal Society of Chemistry, Periodic Table: Iridium](https://periodic-table.rsc.org/element/77/iridium) · Source: [International Platinum Group Metals Association, Iridium factsheet, March 2026](https://ipa-news.com/assets/pdfs/factsheets/2026-03-iridium-factsheet.pdf) --- # Security What we can show you, and when. Procurement will ask, so the answers will live here. We list a certification, audit or uptime figure only once it is real and audited. ## Trust documents For our security questionnaire, DPA and subprocessor list, write to sales@insimbi.net. --- # Legal Terms and privacy. Our terms, privacy policy and licenses are available on request. Questions: sales@insimbi.net. --- # Status System status. Customers get a live status page. Questions: sales@insimbi.net.