Fulfillment policy

SubScript's own services are digital and delivered entirely online: dashboard access, hosted checkout pages, payment links, subscription billing, prepaid metered vaults, signed webhooks, receipt pages, and the developer API. Nothing SubScript sells is shipped physically.

For purchases made from a merchant through SubScript, the merchant is the seller and is responsible for delivering what was purchased. Section 4 explains how that works.

Account access is provisioned immediately at sign-up. Checkout pages, payment links, receipts, and the API are available as soon as they are created.

SubScript Premium activates when its payment confirms on-chain — typically within seconds to a few minutes of the transaction being submitted. Your merchant tier is upgraded automatically after confirmation; no manual step is required.

If a Premium payment confirms on-chain but your tier does not activate within one hour, contact compliance@subscriptonarc.com with the transaction hash and we will reconcile it.

Recurring charges execute automatically per billing period against the bounded authorization you approved. After each successful renewal you receive an in-app receipt message with the amount and a verifiable transaction link.

If a renewal cannot execute (insufficient balance or allowance), service entitlements may pause. You are notified and can top up or cancel; repeated failures stop the subscription rather than letting charge attempts pile up.

When you pay a merchant through SubScript, SubScript's role completes when the payment settles on-chain and the merchant is notified through a signed webhook carrying the Checkout Intent ID. Delivery of the purchased goods or services is then the merchant's obligation, on the merchant's stated timeline.

Merchants must verify webhook signatures and fulfill from verified events. A merchant's failure to deliver after a verified payment is a dispute between you and the merchant — your SubScript receipt and the on-chain transaction are your proof of payment.

If a merchant repeatedly fails to fulfill verified payments, report it to compliance@subscriptonarc.com; this violates our Terms of Service.

Vault-based services activate when your committed escrow reaches the merchant's required commitment. The merchant renders service during the cycle; settlement draws only the metered usage at cycle end and automatically returns every unused unit to your wallet.

If a matured cycle is never settled within the grace window, you can reclaim your full escrow directly from the contract — service fulfillment failures can never permanently lock your funds.

SubScript is in public beta on the Arc testnet. We target high availability but do not guarantee uninterrupted service during the beta: contracts may be redeployed, data may be reset, and features may change as part of hardening for mainnet.

Scheduled resets or breaking changes that affect your integrations will be announced in the dashboard or by email where possible.

Fulfillment questions, activation issues, or non-delivery reports: compliance@subscriptonarc.com. Include your wallet address or account email plus the receipt ID or transaction hash.