Support & contact
Real humans read every message. Include the email or wallet address on your account — plus a receipt ID or transaction hash if it's about a payment — and we can usually resolve things in one reply.
Public beta notice: SubScript currently runs on the Arc testnet. Beta payments settle in testnet USDC, which has no monetary value.
Telegram support group
t.me/subscriptsupportThe fastest way to reach the team and other builders. Ask anything — checkout issues, integrations, or just say hi.
Community + team, usually same day
General & product support
support@subscriptonarc.comIntegration questions, activation issues, dashboard problems, wallet onboarding, payment links, webhooks, and anything else about using SubScript.
Acknowledged within 2 business days
Billing, refunds, privacy & legal
compliance@subscriptonarc.comBilling errors, refund requests, privacy/data requests, account disputes, deceptive-merchant reports, and questions about the Terms or policies.
Acknowledged within 5 business days (per the Refund Policy)
Security disclosures
compliance@subscriptonarc.comFound a vulnerability in the app, API, or smart contracts? Email with the subject line [SECURITY]. Please report privately before any public disclosure — we take every report seriously.
Prioritized ahead of all other mail
Common questions
How do I cancel a subscription?
Open your dashboard, find the subscription, and choose Cancel current plan. Cancellation is free, works immediately or at period end, and revokes the on-chain billing authorization itself — no future charge can execute after that.
I was charged incorrectly (wrong amount, duplicate, or after cancelling).
Email compliance@subscriptonarc.com with your wallet address or account email, the receipt ID or transaction hash, and what you expected. During the testnet beta these are treated as launch-blocking bugs and your account state is corrected; on mainnet, billing errors by SubScript are refunded in USDC to the paying wallet.
I paid a merchant but didn't receive what I bought.
The merchant is the seller of record — contact them first; your SubScript receipt and its on-chain transaction are your proof of payment. If a merchant repeatedly fails to deliver after verified payments, report them to compliance@subscriptonarc.com — that violates our Terms of Service.
My Premium upgrade paid on-chain but didn't activate.
Activation is automatic and usually takes seconds. If it hasn't applied within one hour of on-chain confirmation, email support with the transaction hash and we'll reconcile it.
The dashboard is asking me to back up a private key. Is that real?
Yes — for email wallets that support key export, the dashboard stays locked until you download and verify your recovery key. SubScript will never ask for your key by email or DM; export happens only inside the dashboard with an OTP check.
My webhooks aren't arriving (merchants).
Open Dashboard → Webhooks for the live delivery inspector: every attempt, its payload, and a replay button. Verify the x-subscript-signature HMAC header and check that your endpoint returns 2xx. The developer docs cover signature verification with copy-pasteable code.
Is this real money?
Not during the beta. SubScript currently runs on the Arc testnet, so all payments settle in testnet USDC, which has no monetary value. Balances and history may be reset before mainnet.
Developers
Start with the developer docs — quickstart, API reference, webhook verification, and SDK usage. Product and protocol updates are posted on @SubScript_onarc.