Wallet provider track
For wallets and platforms that want production resolution access. Companies, individual developers, and organizations can apply.
Apply and approval
/dashboard/provider/apply is the application entry point. Provider API keys, namespaces, and production tooling stay locked until operator approval.
submitted → under review → approved
↘ rejected → reapplyProvider workflow
- Submit the provider application and describe your wallet integration.
- After approval, create a provider API key in the dashboard.
- Use the key for resolver traffic from your protected runtime.
- Choose resolver-only or resolver-plus-merchant-setup integration.
- Use namespaces only for names owned by your provider.
Dashboard modules
- Overview
- Integration
- API Keys
- API Usage
- Webhooks
- Sandbox
- Namespaces
- Settings
Provider credentials authorize resolution and optional merchant-setup facilitation. Approved providers can also manage their own namespaces; they never replace controller authorization for registry mutations.
Provider application