Setting Up a Bitnob Account

Building on Bitnob starts with creating and configuring your developer account. Follow the steps below to test in our Sandbox environment and go live in Production once you’re ready.

Create Your Account

2

Enter a valid email address and a strong password (at least 12 characters, mix of letters, numbers, symbols).

3

Check your inbox and click the confirmation link. If you don’t see it, look in your spam folder.

Log In to Your Dashboard

4

After email confirmation, go to Dashboard.

5

Enter your email and password to sign in.

6

Familiarize yourself with the main sections: API Keys, Wallets, Transactions, and Usage Reports.

Bitnob account setup process
Tip

If you plan to collaborate with others, invite your colleagues through your account settings.


Complete Basic Profile Setup

Add Company and Contact Info

1

In the Profile section, enter your company name or project name.

2

Provide a contact phone number and mailing address (used for invoices and notifications).

3

Optionally upload a logo or avatar to personalize your dashboard view.

KYC and Compliance (Optional for Sandbox)

1

For sandbox testing, you can skip verification and operate under default limits.

2

To lift transaction limits and unlock Production, submit your business registration documents, ID proofs, and bank account details under Identity & Compliance.

3

Verification usually completes within 24–48 hours. You’ll get an email update once approved.

Sandbox vs. Production Environments

Bitnob uses the same application URL for both sandbox and production. The difference is the API keys used, not separate endpoints. Always isolate your keys to avoid mixing environments.

Sandbox Environment

Use sandbox keys to test wallet creation, payments, and webhooks without moving real funds.

Sandbox data may reset periodically; don’t rely on it for long-term records.

Production Environment

Use production keys to process real transactions and manage live balances.

Only switch after fully testing all flows and completing any required KYC.

Caution

Before moving to production, ensure your code points to the correct base URL and uses your production client ID and secret key. Mixing keys across environments causes authentication failures.


Generate HMAC Client ID and Secret Key

Secure your integration by generating separate credentials for sandbox and production.

Locate API Keys Section

In the left menu, select Developer > API Keys.

You’ll see existing keys (if any) and the option to create new ones.

Create New Key Pair

Click Create Key. Choose Sandbox or Production from the dropdown.

Give each key a recognizable name (e.g., dev-sandbox-key, prod-main-key).

After creation, copy the Client ID and Secret Key immediately; you won’t see the secret again.

Secure Storage

Store credentials in environment variables or a secure vault (e.g., AWS Secrets Manager, HashiCorp Vault).

Never hardcode keys or check them into source control.

Rotate keys regularly and revoke unused ones.

Example .env File

Auth key

BITNOB_CLIENT_ID=yourClientId***

Auth key

BITNOB_SECRET_KEY=yourSecretKey***

Verify Your Setup

A quick call to the /api/balances endpoint confirms you’ve set up your account and keys correctly. To learn about authenticating your API requests, refer to our Authentication Guide Here’s an example using a sandbox key:

API Request Example
Note

If everything is working properly, you’ll receive a 200 OK with JSON data about your Bitnob wallets.


Next Steps

1

Explore the Quickstart: Follow our guide to create wallets, send test payments, and handle callbacks.

2

Review Core Concepts: Understand how Bitnob’s rails, wallets, and events connect across the platform.

3

Check Tutorials: See real-world use cases—like airtime top-ups and Lightning transactions—before diving into the full API Reference.

That’s It!

With your Bitnob account created and your API credentials verified in sandbox, you’re ready to integrate with confidence. Move on to advanced features and scale your application for production when you’re ready.


Share on
Share on FacebookShare on XShare on LinkedIn
Did you find this page useful?