Supported Platforms

reply.cash enables sending stablecoins to recipients via their social media and messaging accounts. Recipients authenticate through their platform accounts to securely claim funds.

Platform Support Overview

The following table shows all platforms supported or planned for reply.cash social account integration:

Platform	Authentication Method	Account Format	Status	Notes
Twitter/X	OAuth 2.0 via Twitter API	@username	🟢 Live	Full integration with DM notifications
GitHub	OAuth 2.0 via GitHub API	@username	🟢 Live	Developer-focused platform
WhatsApp	Phone number verification	+1234567890	🔵 In Development	Business API integration planned
Telegram	Bot API integration	@username	🟠 Backlog	Bot-based claiming system
Facebook	OAuth 2.0 via Meta API	@username or profile ID	🟠 Backlog	Meta platform integration
LinkedIn	OAuth 2.0 via LinkedIn API	Profile URL or username	🟠 Backlog	Professional network focus
Instagram	OAuth 2.0 via Meta API	@username	🟠 Backlog	Part of Meta ecosystem
Discord	OAuth 2.0 via Discord API	username#1234	🟠 Backlog	Gaming and community focus
Email	Email verification	user@domain.com	🟠 Backlog	Traditional email claiming
SMS	Phone verification	+1234567890	🟠 Backlog	Direct mobile integration

Status Legend

• 🟢 Live: Fully integrated and available to users
• 🔵 In Development: Actively being developed
• 🟠 Backlog: Planned for future development

How Platform Authentication Works

Current Implementation (Twitter/X & GitHub)

Step 1: Recipient Notification

1. Sender initiates transfer via reply.cash app
2. Platform notification sent (DM, mention, or notification)
3. Unique claim link generated for the specific recipient

Step 2: Authentication Flow

1. Recipient clicks claim link from notification
2. Platform OAuth initiated (Twitter/GitHub login)
3. Identity verification confirms account ownership
4. Secure token exchange establishes authenticated session

Step 3: Account Verification

1. Platform API verification confirms account authenticity
2. Handle matching ensures correct recipient
3. Anti-fraud checks prevent impersonation
4. Session establishment for secure claiming

Step 4: Claim Process

1. Wallet creation or connection (if needed)
2. Transaction preparation with verified identity
3. Blockchain transaction transfers funds to recipient
4. Confirmation notification sent via platform

Platform-Specific Details

Twitter/X Integration

• Authentication: OAuth 2.0 with Twitter API v2
• Notification Method: Direct Messages (DMs)
• Account Verification: Real-time API verification
• Handle Format: @username (without @ symbol in input)
• Rate Limits: Managed to comply with Twitter API limits
• Security Features:
  • Account age verification
  • Activity verification
  • Bot detection

GitHub Integration

• Authentication: OAuth 2.0 with GitHub API
• Notification Method: GitHub notifications
• Account Verification: GitHub profile verification
• Handle Format: GitHub username
• Use Cases: Developer payments, open source contributions
• Security Features:
  • Repository contribution history
  • Account verification badges
  • Organization membership verification

WhatsApp (In Development)

• Authentication Method: Phone number verification + WhatsApp Business API
• Notification Method: WhatsApp messages via Business API
• Account Format: International phone numbers (+1234567890)
• Verification Process:
  1. SMS verification code
  2. WhatsApp Business API confirmation
  3. Phone number ownership verification
• Challenges: Business API requirements, phone number privacy

Platform Integration Requirements

Technical Requirements

• OAuth 2.0 Support: Platform must support secure OAuth authentication
• API Access: Programmatic access to user verification
• Notification System: Ability to send messages or notifications
• Rate Limiting: Reasonable API rate limits for scalability
• Security Standards: Platform security meets reply.cash standards

User Experience Requirements

• Wide Adoption: Platform has significant user base
• Easy Authentication: Simple login process for users
• Reliable Notifications: Consistent message delivery
• Mobile Friendly: Works well on mobile devices
• Global Availability: Platform accessible in target regions

Compliance Requirements

• Privacy Standards: GDPR, CCPA compliance
• Data Protection: Minimal data collection and storage
• Regional Regulations: Compliance with local laws
• Platform Policies: Adherence to platform terms of service

Security Considerations

Identity Verification

• Multi-factor Authentication: Platform-native 2FA when available
• Account Age Verification: Minimum account age requirements
• Activity Verification: Recent platform activity confirmation
• Reputation Scoring: Platform-specific reputation metrics

Anti-Fraud Measures

• Impersonation Prevention: Verified account badges and checks
• Bot Detection: Automated account detection and blocking
• Rate Limiting: Transaction limits per account/platform
• Suspicious Activity Monitoring: AI-powered fraud detection

Privacy Protection

• Minimal Data Collection: Only essential information stored
• Data Encryption: All sensitive data encrypted at rest
• Automatic Deletion: Temporary data automatically purged
• User Consent: Clear consent for data usage

Regional Platform Preferences

Americas

• Primary: Twitter/X, Instagram, WhatsApp
• Secondary: Facebook, LinkedIn, SMS
• Developer: GitHub

Europe

• Primary: WhatsApp, Twitter/X, Telegram
• Secondary: LinkedIn, Instagram, Email
• Compliance: GDPR-compliant implementations

Asia-Pacific

• Primary: WhatsApp, Telegram, WeChat (future)
• Secondary: Twitter/X, Line (future)
• Regional: Platform-specific integrations planned

Africa & Middle East

• Primary: WhatsApp, Telegram, Twitter/X
• Secondary: Facebook, SMS
• Focus: Mobile-first platforms

Development Roadmap

Phase 1 (Current)

• ✅ Twitter/X OAuth integration
• ✅ GitHub OAuth integration
• ✅ Basic notification system

Phase 2 (Q1 2024)

• 🔵 WhatsApp Business API integration
• 🔵 Enhanced security features
• 🔵 Mobile app optimization

Phase 3 (Q2 2024)

• 🟠 Telegram Bot API integration
• 🟠 Email verification system
• 🟠 SMS integration pilot

Phase 4 (Q3-Q4 2024)

• 🟠 Meta platforms (Facebook, Instagram)
• 🟠 LinkedIn integration
• 🟠 Discord integration
• 🟠 Regional platform expansions

Getting Started

For Senders

1. Select Platform: Choose from available platforms (Twitter/X, GitHub)
2. Enter Handle: Input recipient's platform username
3. Send Funds: Complete transaction via reply.cash
4. Track Status: Monitor claim status in dashboard

For Recipients

1. Receive Notification: Get DM or notification with claim link
2. Click Link: Open claim page via secure link
3. Authenticate: Log in via your platform account
4. Claim Funds: Complete wallet setup and claim process

Platform Integration Requests

Want to see a specific platform supported? We prioritize integrations based on:

• User Demand: Community requests and voting
• Technical Feasibility: Platform API capabilities
• Regional Importance: Geographic user distribution
• Security Standards: Platform security and compliance

Submit requests via:

• Telegram: t.me/replydotcash
• Twitter/X: @replydotcash
• GitHub: Feature requests on our documentation repo

---

For information about supported blockchain networks and assets, see our Supported Chains & Assets page.