Checkout Intents
Merchant backends create bounded payment sessions, store intent IDs, and let SubScript map on-chain payment activity back to off-chain users or orders.
Integration docs
SubScript Protocol turns payment permission into programmable stablecoin commerce.
The Unified Payment Authorization model gives one-time checkout, subscriptions, usage billing, invoices, sponsored payments, and AI-native transactions the same shape: create an intent, authorize a bounded USDC action, record an Arc memo receipt, and fulfill with a signed webhook.
Protocol status
Launch-ready primitives plus scoped roadmap targets
Direct Arc USDC hosted checkout is the live payment rail.
CCTP checkout stays disabled until Arc-side memo settlement is bound in one verifiable flow.
Private-key export, fiat onramps, Paymaster, Chainlink Automation, ArcaneVM, and quantum-resilience claims are deployment-scoped.
Live protocol surface
What the platform provides now
Hosted Payment Links
Merchants can create Arc USDC payment links with titles, amounts, receipt tokens, QR-friendly URLs, usage limits, and webhook fulfillment.
Arc Memo Receipts
Each checkout uses a receipt token such as rcpt-... as the memo binding payment amount, merchant address, and receipt page state.
Event-Sourced Signed Webhooks
Payment events are written to an append-only merchant_events ledger before dispatch. Each delivery attempt is tracked individually with HTTP status and response body. Endpoints are environment-scoped (TEST/LIVE) with secret rotation and grace-period overlap. Merchants verify HMAC signatures and fulfill by intent ID without trusting browser callbacks.
Metered Vault Billing
Usage-based products can deduct prepaid micro-USDC balances for API calls, AI tokens, storage, media, and other consumption events.
Google Wallet Onboarding
User-controlled embedded wallet flows reduce seed phrase and setup friction for mainstream subscribers, with encrypted export/backup tracked as the non-custodial completion target.
Merchant Recovery Flows
Retry, reconciliation, keeper-triggered billing, and failure-state routes provide the foundation for smart dunning and automated revenue recovery.
Problems solved
Why UPA exists
Legacy subscription systems are built around merchant-side pull billing, card network constraints, dollar-card friction, and private reconciliation records. SubScript moves the critical payment state into bounded, auditable stablecoin flows.
Unwanted recurring charges
Users authorize bounded payment flows and can stop relying on opaque merchant-side pull billing.
Double billing
On-chain settlement and idempotent verification reduce duplicate fulfillment from retry races.
Hidden card costs
USDC-native pricing removes virtual card setup fees, maintenance fees, FX markups, failed-card penalties, and billing-address failures from the user journey.
Receipt disputes
Arc memo receipts give merchants and payers a shared, auditable payment record.
Wallet reconciliation
Checkout Intent IDs replace raw wallet-address matching as the merchant fulfillment key.
Usage mismatch
Metered vaults let product value and payment amount move closer together for usage-heavy services.
Protocol targets
What should remain deployment-scoped
These are part of the protocol direction from the feature brief, but they should not be described as fully live until production schema, contracts, automation, and external Arc/Circle deployment settings prove them.
Dedicated Invoice Engine
Payment links and external references cover invoice-like collection today. First-class invoice numbers, custom due terms, lifecycle states, reminders, and payer records remain protocol expansion work.
Fiat-to-USDC Onramps
The product target is bank-transfer funding that automatically converts fiat into USDC and deposits it into the user's SubScript wallet. This needs provider, compliance, and reconciliation work before live launch.
Sponsor Relationships
The protocol model supports parent, employer, and team sponsorship. Dedicated sponsor tables, spending caps, beneficiary policies, and privacy rules should be added before marketing it as fully live.
Merchant Commitments
Service lock windows, minimum commitments, and grace periods need explicit schema, contract, and UI disclosure before enforcement. The product ceiling is 72 hours for digital goods and 30 days for SaaS seats.
Smart Dunning Schedules
Billing retries exist at the platform level. Configurable Day 1, Day 3, and Day 7 retry policies plus email/SMS top-up reminders should be formalized before marketing this as fully live.
Decentralized Keepers
Cron and keeper-compatible routes exist. Chainlink Automation should be treated as deployment-scoped until production upkeep registration is verified.
Paymaster Sponsorship
The product targets a zero-hidden-fee customer experience. Production Circle Paymaster or Gas Station sponsorship must be confirmed in deployment settings.
ArcaneVM Privacy
Privacy Premium surfaces exist with a 10 USDC/month baseline target. ArcaneVM confidentiality and governed visibility should remain deployment-scoped until verified against the live Arc environment.
1% merchant fee target
Pricing is designed around transparent merchant-paid processing.
Retry-aware billing
Cron, reconciliation, and failure-state routes support recovery flows.
Invoice-like links
Payment links and external references cover collection while first-class invoices mature.
Consumer control
The model is designed to reduce unwanted recurring charges, card penalties, and opaque charge disputes.