Developer Dashboard

Use the Seev developer section to manage API access, environments, API keys, transactions, and webhooks.

The Developer Dashboard is the control center for building with Seev API products. It is where you accept the developer terms, switch between sandbox and production, generate keys, inspect API transactions and customers, and configure webhooks.

Do I need the Developer Dashboard?

Use it only when your own app, website, or backend needs to create payments programmatically. You do not need API keys for Dashboard invoices, payment links, storefronts, or POS.

If you do not have a developer, start with Get Paid with Seev Plus before choosing the API route.

Get started

To enable developer access:

Open Seev API in the Seev Dashboard.
Review and accept the API terms and conditions.
Open the API Keys tab.
Generate a named key for the API product you are integrating.
Copy the view-once secret and build in sandbox mode.

Accepting the developer terms does not create keys automatically. Sandbox mode is available before organization verification is approved; production requires approved verification.

Authenticate API requests

Send the API key for the product and environment you are using from a trusted server. Never expose a secret key in browser code, a mobile application bundle, or a public repository.

Authorization: Bearer <your_api_key>
Content-Type: application/json

Sandbox and production credentials are separate. Use sandbox while developing and testing without live money movement. Production requires an eligible, verified organization and a separate production key.

Dashboard routes beginning with /api/organizations/{orgId}/... power authenticated Seev Plus screens. They are not public merchant integration routes. For a custom integration, use the routes in the Checkout API guide.

Developer products

Product	Status	What it is used for
Checkout API	Available	Create checkout sessions and accept payments from your own app or server.
Exchange Widget API	Available	Embed Seev exchange experiences in your product.
KYC	Coming soon	Verify customers or businesses through the API.

Each product belongs to a separate Seev service, so keys are generated per product. For example, a Checkout API key cannot be used as an Exchange Widget API key.

Dashboard tabs

API Keys

Generate product-specific API keys, name keys by app or service, and optionally restrict keys by IP address.

Transactions

Review API-created transactions by environment, period, and status.

API Customers

Review customers derived from API transactions in the selected environment.

Webhooks

Create webhook endpoints and inspect delivery logs for API events.

Checkout API

Learn how to create checkout sessions and verify payment results.

Sandbox and production

The developer section can be in one of three modes:

Mode	Meaning
`sandbox`	Test API requests without moving real money.
`production`	Live API requests can process real customer activity.
`disabled`	Developer access is disabled and API actions are unavailable.

Use sandbox mode while building locally, testing flows, or validating integration behavior. Switch to production only after organization verification is approved and your integration is ready for live traffic.

Sandbox and production data remain separate. A sandbox key cannot be used for production, and sandbox customers or transactions are not proof of live payment.

Recommended integration order

Accept the developer terms.
Generate one clearly named Checkout API sandbox key.
Store the view-once secret securely.
Create a sandbox checkout session from your backend.
Test successful and failed outcomes.
Verify the payment on your server.
Create and verify a signed webhook endpoint.
Complete organization verification.
Create a separate production key and perform a controlled live test.

Production checklist

Before processing live customer payments, confirm that your integration:

Creates checkout sessions from a trusted server
Stores your own order and Seev reference mapping
Uses stable idempotency keys when retrying create requests
Redirects customers only to the checkout URL returned by Seev
Verifies payment results on your server before fulfilment
Handles signed webhook events idempotently
Gives customers useful pending and failed states
Keeps sandbox and production credentials separate

If something is blocked

Message or symptom	What to check
Developer terms must be accepted	Open Seev API and complete the terms step for the active organization.
Production requires verification	Complete organization verification or switch back to sandbox.
Developer account disabled	API actions are unavailable for the organization; review the displayed guidance.
No keys are shown	Check the selected environment and organization.
Request returns unauthorized	Confirm product, environment, active status, and exact key value.

Where funds settle

Funds from successful API transactions are automatically deposited into your main Seev account. From there, you can withdraw them or send them to a different wallet.

The Developer Transactions view contains API-created activity only. Dashboard invoices, payment links, and storefront orders have their own operational views.