A Claim Link turns a stablecoin balance into a shareable URL. If you hold USDT or USDC in your AllScale account, you generate a link, send it to anyone, and they claim the funds simply by opening it in a browser — no prior signup, and no gas fees on their side.
There are two claim paths:
If the recipient already has a wallet, they paste their address and receive the funds directly.
If they don't have a wallet, they sign in with an email, an AllScale wallet is created for them automatically, and the funds land there.
The system is non-custodial: AllScale never holds a complete private key and cannot move funds unilaterally. The balance behind each link has only two possible outcomes — it is claimed by the recipient, or returned to the sender. Any link left unclaimed for 14 days is automatically refunded in full to the sender's original address.
Sending money to a recipient who does not yet hold an account has traditionally carried significant overhead. The recipient must typically open a PayPal or Stripe account before receiving funds, payment-rail fees begin at 2–3%, and the sender must maintain supporting infrastructure — address mapping, order polling, and reconciliation logic — simply to distribute payments.
Claim Link reduces this overhead on both sides: the sender needs only a link, and the recipient needs only to open it.
Claim Link addresses two distinct audiences: consumers transferring funds to individuals, and merchants disbursing funds at scale.
An AllScale user sends funds to a friend, colleague, or family member by entering an amount in the app, copying the link, and sharing it through any channel. Typical applications include peer transfers, gifts, expense-sharing, and reward distribution — the recipient can claim regardless of prior crypto experience.
A merchant's backend calls the API to disburse funds programmatically — one link per payout (amount, token, chain, recipient email, and reference id) — with the system signing and executing each transaction without manual approval. This supports unattended, system-triggered disbursement, including:
Task and bounty payments — micro-task platforms, Q&A services, and content platforms paying contributors
Creator and influencer payouts — per-deliverable compensation
Game revenue sharing — distributing earnings to players
Recurring and batch disbursements — overnight settlement on streaming platforms, or scheduled ERP payout runs
A refund is functionally a payout to the customer and therefore runs through the same API — no separate refund capability is required.
Last updated
