Minimum 2 weeks notice required for production launches. Contact support@onebalance.io early in your development process.
Custom API Key
- Request custom API key: Contact support@onebalance.io with the following information (minimum 2 weeks notice):
- Company details (name, website link, and social media links)
- Use case description (what you’re building, target users, and key features)
- Expected launch ETA (approximate date when you expect to go live)
- Volume estimates (expected transaction volume per day/month)
- Chain/asset preferences (select chains from supported networks and specify assets like USDC, USDT, ETH, SOL, or request custom assets)
- Fee requirements (choose your fee structure: percentage-based, flat per-chain, or combination)
- Set up team communication: OneBalance team will create a Telegram or Slack channel between your team and ours for faster support and coordination
- Implement authentication: Set up proper API authentication and secure key storage
Rate limits are configured by OneBalance based on your expected transaction volume. Contact us if you need adjustments.
Development Phase
- Complete getting started tutorials: First API Call and Chain-Abstracted Swap
- Understand core concepts: What is OneBalance and How it Works
Technical Setup
- Choose networks and assets: Select from supported networks and available assets
- Select account type: Choose EIP-7702 delegated accounts (recommended) or ERC-4337 smart accounts
- Pick wallet provider: Privy, Turnkey, or custom solution
- Determine advanced needs: Contract calls, multi-input transactions (see guides)
Testing & Launch Prep
- Test with custom API key: Verify transactions, fee collection (if applicable), and all supported chains
- Validate user flows: Test wallet integration and complete user journeys end-to-end
- Notify OneBalance for production readiness: Contact support@onebalance.io when testing is complete to make your custom API key production-ready
Monetization Setup
- Plan fee structure: Choose fixed per chain, percentage, or combination approach (see fee options)
- Set up Pimlico: Get API key and Policy ID for gas sponsorship (required for fee collection)
- Prepare beneficiary addresses: Where collected fees will be sent
Fee configuration is handled by OneBalance during API key setup. Without Pimlico, you’ll use our sponsored gas (no fee collection).
Launch
- Confirm launch date with OneBalance team and prepare rollback plan
- Verify first transactions work successfully and monitor for any issues
- Monitor ongoing performance and collect user feedback
Support & Resources
Getting Help
Developer Support
Use the Intercom chat widget for instant help or email support@onebalance.io
Discord Community
Connect with other developers building on OneBalance
Documentation Resources
API Reference
Complete API documentation and examples
Integration Guides
Step-by-step integration tutorials
Privy Integration
Complete Privy wallet integration guide
Contract Calls
DeFi, NFT, and gaming integration examples
Enterprise Solutions
Enterprise Support
Need custom rate limits, dedicated support, or enterprise features? Contact our sales team for tailored solutions.
Important Reminders
Timeline Requirements
Timeline Requirements
- Minimum 2 weeks notice required for production launches
- Early communication ensures smooth launch support
- Complex integrations may require additional time
Fee Collection Requirements
Fee Collection Requirements
- Pimlico setup required to collect user fees
- You’re responsible for paymaster account funding
- Test fee collection before production launch
Security Best Practices
Security Best Practices
- Never expose production API keys in client-side code
- Implement proper authentication server-side
- Set up proper error handling and logging
This checklist covers the essential steps for a successful OneBalance launch. Click the links for detailed documentation on each topic. Contact our support team early and often - we’re here to help.