Accounts & verification
Organizations, team members and payout KYC.
Developer accounts
Sign up at dev.spuke.com with email, Google or GitHub. Your account is separate from any merchant account — the same person can hold both, and sessions are isolated.
Organization
Every developer account belongs to one organization. The organization owns:
- apps and their listings
- API credentials and webhook endpoints
- sandbox environments
- the payout account and earnings
Team roles
| Role | Can do |
|---|---|
| Owner | Everything, including payouts and deleting the organization |
| Admin | Apps, credentials, environments, team invites |
| Developer | Apps, credentials, sandbox — no payout access |
| Read-only | View dashboards and logs |
Invites are email-based and expire; revoked members lose API access immediately.
Verification
Verification unlocks live mode.
- Sandbox: verification is instant. No documents, no bank account, no real identity check.
- Live: you complete payout onboarding with our payout partner — legal entity, representative identity, and a bank account in a supported country.
While a payout account is restricted or disabled, publishing and payouts are paused automatically and you receive an in-app notification plus an email reminder until it is resolved.
Notifications
The bell in the developer dashboard carries anything that needs action: verification requirements, review results, webhook failures, rate-limit warnings and payout events. Critical items are mirrored to email.