Your account type determines which InFlow operations your application can use.

Choose Seller when integrating payment acceptance, even if your job title is developer. A Developer account does not grant access to seller configuration.

A Seller account can also make payments. You do not need a separate Developer account just because your service purchases from other services.

User / Operator accounts are intended for people authorizing agents to act on their behalf. For CLI login, follow the separate Unlock and authenticate guide. The API-key setup below applies to Developer and Seller accounts.

Start with Sandbox for development and controlled integration tests.

Register in the environment you intend to use. Sandbox and production have separate accounts and credentials.

All four SDKs default to production. Set the environment explicitly when configuring your application, especially during testing.

Selecting Sandbox configures the InFlow connection. It does not make an external service, payment processor, or blockchain use test funds. Check the test setup for your chosen payment method before paying.

1. Log in to your Developer or Seller account in the chosen environment.
2. Open Configuration → API Keys.
3. Select Add API Key.
4. Enter a descriptive name, such as Report service — Sandbox, and select Save.
5. Use the value shown under Private Key as your application’s API key.

The Public Key is not the API credential used by these SDK integrations.

Open Sandbox API Keys or Production API Keys to manage your keys in the chosen environment.

Configure these two settings together:

• Environment: Sandbox for integration tests, or production for live payments.
• API key: the Private Key created in that environment.

Load the key from your application’s private configuration and pass it to the SDK. Use the setup instructions for Go, Node.js, Python, or Rust for the exact configuration syntax.

Logging in with the InFlow CLI does not configure your application’s SDK client. The application needs its own configuration.

An API key authenticates your application. It does not add funds or complete payment-method setup. Before testing, follow the setup instructions for the payment option you intend to use.

Keep API keys in server-side configuration or your deployment’s secret manager.

• Do not include keys in browser code or distributed mobile applications.
• Do not commit keys to source control or print them in logs.
• Do not paste keys into coding-agent conversations, integration plans, or support requests.
• If a key is exposed, replace it in your application and delete the exposed key from API Keys.