Terms of service

By accessing SubScript websites, dashboards, hosted checkout pages, APIs, SDKs, smart contract interfaces, receipt pages, or documentation, you agree to these Terms of Service. If you do not agree, do not use SubScript.

SubScript is experimental financial software. You are responsible for understanding your local laws, tax obligations, wallet security, and the risks of blockchain transactions.

SubScript is currently in PUBLIC BETA and operates on the Arc TESTNET. All payments, balances, subscriptions, vault commitments, and receipts created during the beta settle in Arc testnet USDC, which is a test asset with NO monetary value and cannot be exchanged for real funds.

During the beta, smart contracts may be redeployed or upgraded, accounts and balances may be reset, features may change or be removed, and history may be wiped as part of the migration to mainnet. Do not treat testnet balances or receipts as stores of value or proof of real payment.

Beta features are provided for evaluation and integration testing. Production (mainnet) availability, pricing, and feature scope may differ from what the beta offers.

SubScript is a Web3 payment and subscription routing protocol built around USDC, Arc Network transaction memos, Checkout Intent IDs, signed merchant webhooks, and human-readable digital dollar receipts.

The protocol is designed to reduce subscription abuse, including unwanted recurring charges, duplicate billing, hidden cancellation traps, opaque receipt disputes, and card-style failed-payment penalties.

SubScript provides payment software and protocol infrastructure. SubScript is NOT a bank, money transmitter, deposit-taking institution, or investment platform, and testnet balances are not deposits.

For purchases you make from a merchant through SubScript, THE MERCHANT — not SubScript — is the seller and merchant of record for that transaction. The merchant is responsible for the goods or services sold, product claims, taxes, invoicing obligations, and its own refund and fulfillment commitments. SubScript routes the payment, produces the receipt, and notifies the merchant.

SubScript is the seller only for SubScript's own offerings, such as the SubScript Premium merchant plan. For those offerings, the Refund Policy and Fulfillment Policy on this site apply directly to SubScript.

You can use SubScript with an external self-custody wallet that you control. SubScript never asks for seed phrases and cannot move funds in an external wallet without a transaction you authorize.

If you sign up with email onboarding, SubScript provisions an embedded wallet through Circle developer-controlled MPC wallet infrastructure. For these embedded wallets, key material is managed by SubScript's custody provider so the platform can execute the actions you request (subscribing, paying, cancelling) on your behalf. Embedded wallets are therefore CUSTODIAL: treat them as an operating balance for payments, not as long-term storage.

A wallet may be registered as either a user account or a merchant account, not both, unless SubScript explicitly supports a migration or reset process.

Subscribers should see the advertised USDC payment amount before confirming a payment. SubScript aims to avoid hidden customer maintenance fees, failed-card penalties, and unpredictable gas surprises.

Merchants may pay SubScript a transparent processing fee, currently intended as 1% of successful payment volume unless another written arrangement applies.

Blockchain transactions are generally irreversible. SubScript cannot guarantee refunds, chargebacks, or reversals after a payment is confirmed on-chain.

You can revoke a recurring authorization at any time by cancelling the subscription from your dashboard; cancellation stops all future charges for that subscription.

Refund handling depends on who the seller is, whether the network is testnet or mainnet, and the on-chain state of the payment. The full policy — including how to cancel subscriptions, how billing errors are handled, and what applies during the testnet beta — is published in our Refund & Cancellation Policy at /refunds and is incorporated into these Terms.

Merchants are responsible for mapping their own Web2 users, orders, plans, and entitlements to SubScript Checkout Intent IDs.

SubScript may send signed webhook events to merchant servers. Merchants must verify webhook signatures, enforce idempotency, and avoid granting access from unsigned or replayed events.

SubScript is not responsible for merchant fulfillment failures, incorrect entitlement logic, or merchant-side database errors. How SubScript's own services are delivered is described in the Fulfillment Policy at /fulfillment, which is incorporated into these Terms.

SubScript may use Arc Network memo capabilities to create human-readable receipt identifiers and index payment metadata.

Some blockchain data is public, permanent, and outside SubScript's ability to delete. Receipt pages are meant to make payment proof easier to understand, but they do not erase the underlying public-chain nature of settlement.

You may not use SubScript to facilitate fraud, sanctions evasion, malware, credential theft, deceptive billing, spam, harassment, illegal goods or services, or unauthorized access to third-party systems.

You may not abuse APIs, bypass rate limits, forge webhook events, attack smart contracts, scrape private dashboards, or attempt to compromise users, merchants, or SubScript infrastructure.

SubScript may integrate with third-party services including wallets, RPC providers, Circle infrastructure, Supabase, Vercel, Resend, analytics tools, and blockchain explorers.

Third-party services are governed by their own terms and privacy policies. SubScript is not responsible for outages, policy changes, or data practices controlled by third parties.

SUBSCRIPT IS PROVIDED “AS IS” AND “AS AVAILABLE”, WITHOUT WARRANTIES OF ANY KIND, EXPRESS, IMPLIED, OR STATUTORY. To the maximum extent permitted by law, SubScript disclaims all implied warranties, including merchantability, fitness for a particular purpose, title, non-infringement, and any warranty arising from course of dealing or trade usage.

We do not warrant that the services will be uninterrupted, secure, or error-free; that smart contracts are free of defects; that RPC providers, wallets, or block explorers will function correctly; that data will never be lost; or that the services meet the laws of every jurisdiction. This is especially true during the public beta, where breaking changes are expected. Some jurisdictions do not allow certain warranty exclusions, so parts of this section may not apply to you.

To the maximum extent permitted by law, SubScript and its contributors, operators, and suppliers are not liable for any indirect, incidental, special, consequential, exemplary, or punitive damages, or for lost funds, lost profits, lost data, loss of goodwill, failed or delayed payments, contract reverts, delayed webhooks, wallet compromise, market volatility, or third-party service failures — even if advised of the possibility of such damages.

To the maximum extent permitted by law, SubScript's total aggregate liability for all claims arising out of or relating to the services is limited to the greater of (a) the total protocol fees you paid to SubScript in the twelve months before the event giving rise to the claim, or (b) 100 USD. During the testnet beta, transactions settle in valueless test assets, and SubScript's aggregate liability for beta-only usage is limited to the amount in (b).

Nothing in these Terms excludes liability that cannot be excluded under applicable law, such as liability for fraud or for willful misconduct.

You agree to indemnify and hold harmless SubScript and its contributors from claims, damages, and reasonable legal costs arising from your misuse of the services, your violation of these Terms, your violation of applicable law, or — if you are a merchant — the goods or services you sell to your customers, including your tax, refund, and fulfillment obligations.

We may update these Terms as SubScript evolves — including at the transition from testnet beta to mainnet. Material changes will be reflected by updating the “Last Updated” date on this page. Continued use after an update means you accept the revised Terms.

Questions about these Terms, refunds, or account issues: compliance@subscriptonarc.com. Include the email or wallet address connected to your account so we can locate the relevant records.