Recurring SaaS billing
Issue recurring invoices, collect customer-confirmed stablecoin payments, and activate product access after verified settlement.
Stablecoin billing & revenue operations
Stablecoin billingthat closes the loop.
From invoice to verified settlement, entitlement, and webhook—MonetLayer turns wallet-confirmed USDC payments into an operable revenue system.
For SaaS platforms, API businesses, marketplaces, and wallet-native products.
BASE SEPOLIA TESTNETCUSTOMER-INITIATED COLLECTIONEARLY ACCESS
Current public evidence demonstrates a completed customer-confirmed lifecycle on Base Sepolia. It does not represent mainnet production availability or automatic recurring wallet debit.
Settlement trace
- 01InvoiceINV-2048OPEN
- 02Payment attemptATTEMPT #1REQUIRES_ACTION
- 03Customer transaction0x030C…BB0E5SUBMITTED
- 04Base SepoliaTESTNET VERIFIEDVERIFIED
- 05Settlement0.100000 USDCCONFIRMED
- 06EntitlementACCESS ACTIVATEDACTIVE
- 07WebhookMERCHANT SYSTEM200 DELIVERED
02 / Market Signals
The rails arealready moving.Revenue operationsare still catching up.
Stablecoins are moving value at global scale. Turning that movement into subscriptions, invoices, verified settlement, entitlements, and merchant workflows requires a billing system around the rail.
Adjusted stablecoin transaction volume over the last 12 months: 10.2 trillion US dollars
Year-over-year growth in adjusted stablecoin volume in adjusted stablecoin volume: 63 percent
Global stablecoin circulating supply global stablecoin supply: more than 272 billion US dollars
Source: Visa Onchain Analytics. Adjusted volume applies a methodology designed to filter identified inorganic activity. Figures accessed July 2026. Visa Onchain Analytics methodology
Money movement is scaling.The operational layer around it still has to be built.
03 / Category
Stablecoin acceptance starts a payment.
Revenue operations close the record.
Moving money is one event. Billing systems still need durable state for the workflow around it.
subscription staterequires system state
invoice lifecyclerequires system state
retry historyrequires system state
reconciliationrequires system state
entitlementsrequires system state
merchant notificationsrequires system state
operational historyrequires system state
04 / Use cases
Operational outcomes around wallet-confirmed payments.
Usage-based API billing
Turn metered usage into invoice state, payment attempts, settlement evidence, and merchant webhooks.
Wallet-native memberships
Connect wallet-confirmed payments to time-bound or renewable access without making payment execution your entire billing system.
05 / How it works
From money movement to business state in one connected lifecycle.
- 01Create a billing plan
Define price, cadence, and the entitlement that should unlock after verified settlement.
- 02Issue an invoice
Open a durable amount-due record for the billing period instead of treating payment as a one-off event.
- 03Request customer wallet confirmation
Create a customer-initiated collection that requires an explicit signature before execution.
- 04Verify and reconcile onchain settlement
Confirm receipt evidence independently, then bind it to invoice and payment-attempt state.
- 05Activate entitlement and notify the merchant
Update access state and deliver merchant webhooks only after reconciliation succeeds.
06 / Billing lifecycle
A billing period becomes an invoice, an attempt, and a retryable record.
MonetLayer records the lifecycle around a wallet-confirmed payment instead of treating settlement as the whole product.
Lifecycle objectINV-2048
01SUBSCRIPTIONcustomer access stateActive
02BILLING PERIODbilling stateJul 30 - Aug 29
03INVOICEbilling stateOpen
04PAYMENT ATTEMPTbilling stateRequires action
05RETRY POLICYbilling stateWaiting for customer
07 / Settlement verification
Customer action is explicit. Verification happens after transaction submission.
Direct Base v0 is customer initiated, allowance backed, and signature required for each collection. It is not automatic debit, relayer initiated, or delegated authorization.
Settlement verificationBASE SEPOLIA
01CUSTOMER ACTIONintentwallet signature required
02TRANSACTIONsubmittedsubmitted by customer
03ONCHAIN RECEIPTverified43 confirmations
04VERIFICATIONmatchedreceipt and event matched
05RECONCILIATIONclosedinvoice marked paid
Evidence orderCustomer signature → onchain receipt → reconciled invoice
08 / Revenue operations
Verified money movement updates application state.
Record
payment_attempt.succeededinvoice.paid
Activate
entitlement.activeaccess provisioned
Deliver
webhook.200merchant notified
Reject
replay.detectedduplicate ignored
07 / Base Sepolia proof
Built on evidence,
not payment
assumptions.
Testnet evidence. Technical proof.
Not a production-mainnet claim.
Customer signedReceipt verifiedWebhook delivered
BASE SEPOLIATESTNET VERIFIED
Settlement0.100000USDCRaw units: 100000
Fee0.001000USDCRaw units: 1000
Merchant net0.099000USDCRaw units: 99000
Customer payment
- customer-signed USDC renewal
- receipt captured
Verification
- transaction receipt verified
- confirmations reached
Reconciliation
- invoice reconciled to paid
- payment attempt succeeded
Business state
- one entitlement activated
- one webhook delivered
Historical replay rejectedIdempotent duplicate processing
10 / Developer architecture
State boundaries stay visible to merchant systems.
Use integer-string monetary values, tenant-scoped access, idempotent mutations, provider-neutral execution, independently verified settlement, and merchant webhooks.
Conceptual billing object
{
"invoice_id": "inv_preview",
"amount": {
"raw": "100000",
"decimals": 6,
"formatted": "0.100000",
"currency": "USDC"
},
"collection_method": "customer_initiated",
"payment_status": "requires_action",
"network": "base-sepolia"
}11 / FAQ
Clear answers on custody, collection, and proof scope.
Does MonetLayer custody funds?
No. MonetLayer does not custody merchant or customer funds. It records billing state around wallet-confirmed payments.
Does MonetLayer store private keys?
No. Wallet interaction and private-key control remain on the customer or payment-provider side.
Does MonetLayer automatically debit customer wallets?
No. The demonstrated Direct Base model is customer initiated and requires a signature for each collection.
Which network is currently supported?
Public evidence is on Base Sepolia (chain ID 84532) using USDC as the billing asset.
Is MonetLayer live on mainnet?
No. Current public evidence is testnet-only and does not represent Base mainnet production availability.
What does “customer initiated” mean?
The customer must explicitly confirm the collection through a wallet signature before payment execution proceeds.
How does MonetLayer verify settlement?
After transaction submission, MonetLayer independently verifies receipt evidence and reconciles it to invoice and payment-attempt state.
Can MonetLayer work with different payment providers?
The architecture is provider-ready: MonetLayer owns billing state while payment providers execute wallet interaction and chain submission. Live multi-provider production integrations are not claimed here.
What happens when a payment fails?
Failed or incomplete customer action keeps the payment attempt in an actionable collection state instead of silently marking the invoice paid.
What happens if an event or webhook is delivered twice?
Duplicate processing is designed to remain idempotent. The demonstrated proof rejected historical replay against the same payment evidence.
What does the Base Sepolia proof demonstrate?
One completed customer-confirmed lifecycle: verified transaction, reconciled invoice, succeeded payment attempt, activated entitlement, delivered webhook, rejected historical replay, and idempotent duplicate handling.
12 / Early access
Build your stablecoin revenue stack on MonetLayer.
Share your billing model, customer approval flow, settlement requirements, and merchant integration needs. The public site does not connect wallets or collect payments.
Secondary contact: hello@monetlayer.com