Skip to main content

Frequently Asked Questions

Get answers to the most common questions about reply.cash, the platform that lets you send stablecoins to anyone via their social accounts.

Getting Started​

Do I need a crypto wallet to receive payments?​

Nope. That's the magic of reply.cash - you don't need a wallet to receive payments. Just have an active account on supported platforms like Twitter or GitHub and you're good to go. When you claim your funds, reply.cash will create a secure wallet for you automatically, or you can connect an existing wallet if you prefer.

Do I need a crypto wallet to send payments?​

Yes, to send payments you'll need a wallet with funds. reply.cash supports NEAR wallets including HERE Wallet, Meteor Wallet, and MyNEAR Wallet. You can also create a new wallet directly through the reply.cash interface.

How do I get started sending money?​

  1. Visit reply.cash
  2. Connect your NEAR wallet (HERE, Meteor, MyNEAR Wallet)
  3. Select a platform (Twitter or GitHub)
  4. Enter the recipient's handle and amount
  5. Choose your asset (USDC or USDT)
  6. Confirm and send!

Supported Assets and Platforms​

What kind of money can I send?​

USDT and USDC are the supported stablecoin assets on reply.cash. Both are USD-pegged stablecoins that maintain stable value relative to the US dollar. These assets are available on the NEAR blockchain.

What platforms are currently supported?​

Currently Live:

  • Twitter/X - Send to any Twitter handle (@username)
  • GitHub - Send to any GitHub username

In Development:

  • WhatsApp - Phone number-based sending

Planned (Backlog):

  • Telegram, Facebook, LinkedIn, Instagram, Discord, Email, SMS

For detailed platform information, see our Supported Platforms page.

Which blockchains do you support?​

We currently support the NEAR blockchain as our primary network. Additional chains are supported through NEAR Intents technology, which enables cross-chain functionality.

Current Support:

  • NEAR Protocol (fully integrated)
  • USDC and USDT on NEAR

Future Support:

  • Ethereum, Polygon, Arbitrum, Base, and other chains via NEAR Intents

For complete blockchain details, see our Supported Chains & Assets page.

How It Works​

How does the recipient claim the money?​

Recipients claim money through a secure 4-step process:

  1. Receive notification via their social platform (DM, mention, etc.)
  2. Click the unique claim link provided in the notification
  3. Authenticate via their social platform (Twitter/GitHub OAuth)
  4. Complete wallet setup (automatic creation or connect existing)
  5. Confirm claim to receive funds in their wallet

The entire process is secured by platform authentication - no passwords or seed phrases needed for claiming.

How can you support new chains?​

We can support new chains quickly through NEAR Intents, however we need to:

  1. Add wallet selector service integration
  2. Ensure NEAR Intents already supports the target chain

See NEAR Intents asset and chain support documentation at docs.near-intents.org/near-intents/chain-address-support for current compatibility.

How does cross-chain functionality work?​

reply.cash uses NEAR Intents technology to enable cross-chain transactions. This allows:

  • Sending assets across different blockchains
  • Automatic routing to the most efficient chain
  • Unified user experience regardless of underlying blockchain
  • Cost optimization through smart routing

Security and Safety​

Is it secure?​

Yes, reply.cash is secured by multiple layers:

  • NEAR Intents technology for blockchain security
  • Platform OAuth authentication (Twitter, GitHub APIs)
  • Non-custodial wallets - you control your funds
  • Smart contract security on NEAR Protocol
  • Identity verification through social platforms
  • Anti-fraud measures including bot detection

What happens if I send money to the wrong account?​

Before claiming:

  • You can revoke unclaimed funds through the claim management feature
  • Use the reply.cash dashboard to cancel pending transactions
  • Funds return to your wallet automatically

After claiming:

  • Once funds are claimed by the recipient, transactions cannot be reversed
  • This is due to the blockchain's immutable nature
  • Always double-check recipient handles before sending

Do I need KYC verification to use reply.cash?​

No KYC required! reply.cash uses platform authentication instead of traditional KYC methods. We verify identity through:

  • Social platform OAuth (Twitter, GitHub)
  • Account ownership verification
  • Platform-native security features
  • No personal documents or identity verification needed

Costs and Limits​

How much does it cost to use reply.cash?​

For Recipients: Claiming funds is completely free

For Senders:

  • The reply.cash service itself is free to use
  • You only pay blockchain transaction fees (gas fees)
  • NEAR blockchain fees are very low (~$0.01 per transaction)
  • No hidden fees or platform charges

Are there any limits on how much I can send?​

Currently, there are no set limits on transaction amounts imposed by reply.cash. However:

  • Blockchain limits may apply based on network conditions
  • Wallet limits depend on your connected wallet's restrictions
  • Platform limits may apply for notification delivery
  • We recommend starting with smaller amounts as you get familiar with the platform

How long does a recipient have to claim their funds?​

Flexible claiming periods:

  • Recipients can claim their funds at any time by default
  • Senders can set expiration dates for their gifts
  • Senders can manually revoke unclaimed funds anytime
  • Typical expiration: 7-30 days when set by sender
  • No expiration by default - funds remain claimable indefinitely

Geographic and Business Use​

Can I use reply.cash in my country?​

reply.cash is designed to be accessible globally. You can use our service if you have:

  • Access to supported social platforms (Twitter, GitHub)
  • Access to the NEAR blockchain (not restricted in your region)
  • Internet connection for web app access

Regional considerations:

  • Some social platforms may have regional restrictions
  • Blockchain access varies by jurisdiction
  • Check local regulations regarding cryptocurrency use

How can businesses use reply.cash?​

Businesses can leverage reply.cash for various use cases:

Customer Engagement:

  • Customer rewards and loyalty programs
  • Promotional campaigns to social media followers
  • Contest prizes and giveaways
  • Referral program payments

Employee & Contractor Payments:

  • Freelancer payments via social handles
  • Employee bonuses and rewards
  • Remote team payments globally
  • Developer bounties and contributions

Marketing & Growth:

  • Influencer payments via social accounts
  • Community building incentives
  • User acquisition campaigns
  • Social media engagement rewards

Benefits for Businesses:

  • No need to collect banking information
  • Global reach via social platforms
  • Instant payments and settlements
  • Reduced payment processing complexity

Technical Questions​

What wallets are supported?​

NEAR Wallets (Currently Supported):

  • HERE Wallet - Mobile-focused NEAR wallet
  • Meteor Wallet - Web and browser extension wallet
  • MyNEAR Wallet - Official NEAR web wallet

Future Wallet Support:

  • MetaMask (via NEAR Intents for EVM chains)
  • WalletConnect compatible wallets
  • Hardware wallets (Ledger, Trezor)

How do transaction confirmations work?​

Transaction Process:

  1. Initiation - You confirm send transaction
  2. Blockchain processing - Transaction submitted to NEAR
  3. Confirmation - Usually completes in 1-2 seconds on NEAR
  4. Notification - Recipient receives claim notification
  5. Claiming - Recipient can claim immediately after confirmation

Tracking:

  • All transactions have unique transaction hashes
  • View status in reply.cash dashboard
  • Check on NEAR block explorer for verification

What happens during network congestion?​

NEAR Network Benefits:

  • Very low congestion due to efficient consensus
  • Consistent ~1-2 second transaction times
  • Minimal fee fluctuation during high usage

If delays occur:

  • Transactions queue automatically
  • No failed transactions due to gas estimation
  • Real-time status updates in dashboard
  • Customer support for extended delays

Troubleshooting​

I can't connect my wallet​

Common solutions:

  1. Clear browser cache and cookies
  2. Disable ad blockers temporarily
  3. Try incognito/private browsing mode
  4. Update your wallet to latest version
  5. Check wallet connection to NEAR mainnet
  6. Try different browser (Chrome, Firefox, Safari)

The recipient didn't receive a notification​

Check these items:

  1. Verify the handle is spelled correctly
  2. Check recipient's DM settings (Twitter) or notification preferences
  3. Platform may have delays - wait 5-10 minutes
  4. Ask recipient to check spam/filtered messages
  5. Try resending the notification from dashboard

Troubleshooting steps:

  1. Check link expiration - may have expired
  2. Verify complete URL - ensure full link was copied
  3. Clear browser cache and try again
  4. Try different browser or device
  5. Contact sender to verify gift was sent correctly

Transaction is taking too long​

Expected timeframes:

  • NEAR transactions: 1-2 seconds normally
  • Cross-chain via Intents: 2-5 minutes
  • Claim processing: 30 seconds to 2 minutes

If longer delays:

  • Check transaction hash on block explorer
  • Verify network status at status.near.org
  • Contact support with transaction details

Getting Help​

Where can I get support?​

Community Support:

Documentation:

How do I report bugs or request features?​

Bug Reports:

  • Telegram community with detailed description
  • Include transaction hashes and error messages
  • Screenshots help identify UI issues

Feature Requests:

  • Community voting via Telegram
  • Twitter mentions for public requests
  • GitHub issues for technical suggestions

Is there a mobile app?​

reply.cash is currently a Progressive Web App (PWA) that works excellently on mobile devices:

  • Mobile-optimized interface
  • Add to home screen for app-like experience
  • Works offline for basic functions
  • Push notifications support (coming soon)

Native mobile apps are planned for future development based on user demand.

Still have questions? Join our Telegram community or check out our other documentation pages for more detailed information.