A multi-tenant billing platform that collects by ACH and settles clean USDT or USDC to your wallet — automatically, net of fees, with KYT and sanctions screening handled quietly in the background.
One API and one dashboard for the whole flow — invoicing to on-chain settlement, with compliance and reconciliation built in rather than bolted on.
Multi-tenant invoice creation with itemized lines, discounts, terms, and branded PDF generation with live status tracking.
Domestic bank payments are the collection rail. Payments taken elsewhere — card or wire — can be recorded against an invoice so reconciliation and dispute matching stay complete.
Received dollars convert to USDT or USDC and settle to your wallet, net of platform fees, with no manual steps.
Every destination wallet is screened before funds move, on every settlement. Screening is fail-closed: no pass, no conversion, no disbursement.
Flexible fee rules — percentage, flat, per-vertical, or floors — with a reserve ledger per tenant.
Signed webhook events for every state change, plus daily reconciliation exports available to your finance team, tying every dollar to every settlement.
When an invoice is paid, BaaS runs the whole pipeline for you: screen the destination wallet, deduct the platform fee, convert to stablecoin, and settle net USDT/USDC to your wallet. Fail-closed by design — if screening doesn't pass, funds don't move.
Send a magic link. Your customer completes a short, Infinihash-branded KYB flow in minutes — approval then comes back from our regulated payments partner and takes as long as their review takes. Identity documents pass through to our partner and are never retained in your systems or ours; we keep only the business record needed to run your account. You watch every applicant move from invited to approved in one console.
| Business | Owners | Status |
|---|---|---|
| Meridian Trading Co. | 1 | approved |
| Northgate Wholesale | 2 | in review |
| Cedar & Vine LLC | 1 | in progress |
| Harbor Freight Co. | 3 | submitted |
Balances, settlement volume, fees earned, and reserves held — across all your clients or brands, reconciled daily. Know exactly what settled, what's held, and where the stablecoin went.
From straightforward B2B billing to the verticals that need extra controls — the same rails, tuned to how you get paid and pay out.
Bill customers in dollars, settle your treasury in USDT/USDC, and automate fees and payouts across every account.
Run each seller, vendor or brand as its own tenant — isolated data, its own API keys, its own destination wallet, and screening on every settlement.
Collect ACH and settle stablecoin to partners in the countries our payment partner supports — the onboarding flow tells you before you start — without correspondent-bank friction or wire delays.
Run the entire invoice-to-settlement experience under your own brand, on isolated multi-tenant infrastructure.
Elevated review, reserve holds, and velocity caps switch on per vertical — a capability, not your identity.
A treasury view over every tenant: what settled, what's held, and where the stablecoin went — reconciled daily.
Create an invoice, collect payment, and settle stablecoin with a few calls. Signed webhooks keep your system in lockstep with every state change.
# Create an invoice curl -X POST https://rails-api.infinihash.com/api/v1/invoices \ -H "Authorization: Bearer $IHB_KEY" \ -H "Content-Type: application/json" \ -d '{ "number": "INV-2001", "customer": "Northgate Wholesale", "lineItems": [ { "description": "Wholesale order", "quantity": 1, "unitCents": 204120 } ] }' # → invoice created · ACH link issued · webhook on settle
https://rails-sandbox.infinihash.com runs the same application code as production with mocked screening and settlement — invoicing, screening, settlement and webhooks end to end, with no real money and no email. Sandbox keys are not self-serve: they are issued on request after a person reviews your onboarding application. One deliberate difference from production: the sandbox screens through a mock KYT adapter, not the live vendor — /health reports kyt.mock: true there and false in production. It is deterministic rather than permissive: a destination address containing BLOCKED, SANCTION or OFAC is declined, so you can exercise a real fail-closed decline before you go live. Settlement in the sandbox goes through a mock settlement adapter (/health reports the adapter in use), not the Bridge rail, so no real payment rail is exercised; invoicing, the API surface, webhooks and reserves run the production application code.2.5% per settlement, the same rate at every volume. No card networks and no hidden line items. Businesses in high-risk verticals also carry a rolling reserve — a percentage of each settlement held for a defined period and then released; the amount, the release date and every release are shown in your portal. We confirm any reserve before you sign.
Net USDT or USDC after the platform fee, on Tron or Base, to a stablecoin wallet you control. Infinihash never holds your funds — the rail converts and sends in one movement, so there is no point at which we custody your money.
Your customer pays by ACH. Once funds are received and the destination wallet clears screening, dollars are converted to stablecoin through our regulated payments partner and settled — fail-closed at every gate, so nothing moves until checks pass.
Yes. Every destination wallet is KYT- and sanctions-screened on every settlement, fail-closed. Business verification (KYB) of each tenant runs through a branded onboarding flow with our partner. We do not currently perform identity verification on your end customers.
Every tenant has isolated data and its own API keys. Run many clients or brands on one platform — ideal for MSBs, ISOs, and platforms white-labeling the flow.
Yes. There is a real sandbox at https://rails-sandbox.infinihash.com — the same application code as production with mocked screening and settlement, with no real money moved and no email sent. You can read the API reference and the capability endpoint there right now without talking to anyone; making calls needs a key, and sandbox keys are issued on request after a person reviews your onboarding application. The live demo runs the whole invoice-to-stablecoin flow if you would rather just watch it work. One deliberate difference from production: the sandbox screens through a mock KYT adapter, not the live vendor — /health reports kyt.mock: true there and false in production. It is deterministic rather than permissive: a destination address containing BLOCKED, SANCTION or OFAC is declined, so you can exercise a real fail-closed decline before you go live. Settlement in the sandbox goes through a mock settlement adapter (/health reports the adapter in use), not the Bridge rail, so no real payment rail is exercised; invoicing, the API surface, webhooks and reserves run the production application code.
Start onboarding yourself — the form takes a minute and you do not have to email anyone. Prefer to talk it through first? Sales is one click away.