MonetLayer manages
- plans
- subscriptions
- invoices
- payment attempts
- collection state
- retry state
- settlement evidence
- reconciliation
- entitlements
- merchant API state
- merchant webhooks
Product
Revenue state around wallet-confirmed settlement.
MonetLayer is not a wallet checkout page. It records what has to happen before and after a customer-approved stablecoin payment becomes useful business state.
See the developer object model, Base Sepolia proof, reconciliation guide, and security boundaries.
Current authorization model
Direct Base v0 requires a customer wallet signature for every collection transaction.
Customer initiatedAllowance backedIndependently verifiedBase Sepolia testnet
Ownership boundary
Separate billing truth from payment execution.
Payment providers execute
- wallet interaction
- transaction submission
- routing
- gas handling
- chain execution
- cross-chain movement where supported
Live multi-provider production integrations are not claimed on this page.
Billing lifecycle
One connected path from plan to webhook.
Defines price, cadence, and entitlement rules for a commercial offering.
Creates the commercial template later invoices reference.
Binds a customer to a plan and schedules billing periods.
Opens recurring invoice generation without executing payment.
Represents the amount due and the expected collection state.
Becomes the durable record a payment attempt must settle.
Records that customer wallet confirmation is required.
Keeps collection state explicit until a signed action arrives.
Customer confirms the collection through a wallet signature.
Authorizes payment execution without MonetLayer custody.
Independently verifies transaction receipt and expected transfer evidence.
Separates submission from confirmed settlement.
Links verified onchain evidence to the billing record.
Closes the invoice and payment-attempt state safely.
Activates merchant-defined access after reconciliation.
Turns settlement into operable product access.
Notifies the merchant system of durable billing-state changes.
Lets merchant systems react without polling payment rails.
Failure and duplicate behavior
Incomplete action does not silently become paid state.
Customer action not completed
The payment attempt remains in a requires-action collection state. The invoice stays open until verified settlement arrives.
Transaction fails or cannot be verified
Billing state does not advance to paid. Settlement evidence must independently verify before reconciliation.
Webhook delivery retries
Merchant notification attempts are part of operational history. Consumers should treat deliveries as at-least-once and handle duplicates idempotently.
Idempotency and historical replay
Duplicate processing against the same payment evidence is designed to remain idempotent. The demonstrated proof rejected historical replay.
Feature status
Status labels stay honest.
Signature required for each demonstrated collection.
Independent receipt verification before billing-state updates.
Demonstrated in the public Base Sepolia lifecycle proof.
Architecture separates MonetLayer billing state from payment execution.
Not claimed as live.
Not live. Customer action remains explicit in the current model.
Need the contract preview? Explore the developer model or view technical proof.