Open Beta

Fluent is actively being developed. Payments settle directly to the account you configure, and Fluent does not custody merchant funds.

Products, plans, invoices, customer records, and other application data may be affected by updates or unexpected faults. Persistence is designed across upgrades but is not yet guaranteed. Use the beta with caution and keep independent copies of critical business records.

Sovereign billing on the Internet Computer

Billing infrastructure that settles to you.

Accept one-off and recurring payments in ckUSDC, ICP, and ckBTC, directly to your wallet. No banks, no card rails, and no platform custody between you and your revenue.

See how Fluent works
  • Non-custodial by design
  • ckUSDC, ICP, and ckBTC
  • One-off and recurring billing
Merchant dashboard

Good morning

Settlement activity at a glance

Settlement

Direct to wallet

Payment assets

ckUSDC + ICP

Billing

One-off + recurring

Custody

Merchant controlled

Recent activity

Live
Subscription renewed1m
Payment settled2m
Invoice created3m

Non-custodial

Your wallet remains the destination

ICP-native

Built for ckUSDC, ICP, and ckBTC settlement

Cardless

No bank or card network dependency

Borderless

Share hosted checkouts globally

Why Fluent

The billing layer for sovereign software.

Everything you need to create plans, accept payments, understand customers, and reconcile settlement—without handing custody to the billing platform.

Direct wallet settlement

Funds settle to the receivable address you configure. Fluent never becomes the custodian of your revenue.

Hosted payment links

Turn a plan into a focused checkout you can share, embed in a workflow, or send directly to a customer.

Recurring billing

Create subscription plans with explicit approval scopes and a clear customer-controlled payment lifecycle.

ICP-native assets

Accept ckUSDC, ICP, and ckBTC without introducing card rails, bank settlement windows, or a custodial balance.

Usage billing

Organize metered events and billing workflows alongside plans, customers, invoices, and payment activity.

Agent-ready controls

Use bounded payment intents and approval guardrails for software that needs to transact predictably.

How it works

From plan to proof in four clear steps.

Fluent keeps the merchant journey short and the settlement model explicit. Configure once, then operate from a single dashboard.

01

Create a product and plan

Choose one-off or recurring billing in ckUSDC or ICP.

02

Configure settlement

Add the wallet address that should receive customer funds.

03

Share the checkout

Publish a hosted link or connect Fluent to your application.

04

Track the proof

Follow payment, invoice, and settlement activity from one place.

Built for software operators

Predictable payments for the agentic economy.

Give applications and agents explicit payment intents, bounded approvals, and verifiable settlement records. Automation gets guardrails; merchants retain control of the destination wallet.

Payment guardrail

Explicit intent · auditable outcome

Active

Asset

ckUSDC

Approval

Bounded

Destination

Merchant wallet

Proof

Settlement record

Settlement verified

intent_••••••••••••_proof

Built to operate

One connected view of your billing.

Create plans, share checkouts, support customers, and track payment and settlement activity without stitching together disconnected tools.

Fluent dashboard showing ckUSDC, ckBTC, and ICP settlement with recurring revenue and agent billing charts

Merchant dashboard

Plans, customers, payments, invoices, and settlement in one operating view.

Fluent payment-intent checkout ready to confirm with an OISY wallet

Customer checkout

Focused hosted payment flows with clear asset and approval context.

Fluent Help Centre with guide navigation, search, and getting-started steps

Help Centre

Task-oriented guidance for setup, billing, and troubleshooting.

Your products. Your customers. Your wallet.

Launch ICP-native one-off and recurring billing without adding banks, card networks, or platform custody to the payment path.