Developer Dashboard
Enable API access for your organization, work in sandbox, and move a Seev integration to production.
The Developer Dashboard is where you accept the developer terms, switch between sandbox and production, generate keys, inspect API transactions and customers, and configure webhooks. Each of those has its own page; this one covers the setup that comes first and the order to do things in.
Decide whether you need API access
Use the Developer Dashboard only when your own app, website, or backend creates payments programmatically. Dashboard invoices, payment links, storefronts, and POS need no API key and no developer access at all. If nobody on your team writes code, Get Paid with Seev Plus will get you further than this section.
Enable developer access
- Open Seev API in the Seev Dashboard.
- Review and accept the API terms and conditions for the active organization.
- Open the API Keys tab and generate a named sandbox key for the product you are integrating.
Accepting the terms enables developer access without creating any credential, so nothing works until you generate a key. The full procedure, including the view-once secret, IP restrictions, and rotation, is in API Keys.
Sandbox is available before organization verification is approved. Production requires an approved organization, so start verification early if you have a launch date.
Pick the product your key belongs to
Each product is a separate Seev service, and a key issued for one is rejected by another.
| Product | Status | Description |
|---|---|---|
| Checkout API | Available | Create checkout sessions and collect 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. |
Routes beginning with /api/organizations/{orgId}/... back the authenticated Seev Plus screens and are not merchant integration routes. Build against the routes in the Checkout API guide.
Work in the right environment
Developer access sits in one of three modes:
| Mode | Type | Required | Description |
|---|---|---|---|
sandbox | string | Yes | Test API requests. No real money moves. Available before verification. |
production | string | Yes | Live API requests against real customer funds. Requires an approved, active organization. |
disabled | string | Yes | Developer access is off for this organization and API actions are unavailable. |
Sandbox and production keep separate keys, transactions, customers, and webhook endpoints. A sandbox transaction is never evidence that a customer paid, and a sandbox key presented to production is rejected as an unknown key.
Integrate in this order
- Accept the developer terms.
- Generate one clearly named Checkout API sandbox key and store the secret.
- Create a sandbox checkout session from your backend.
- Test a success, a failure, and a repeated submission of the same order.
- Verify the payment on your server before you fulfil anything.
- Create a sandbox webhook endpoint, store its signing secret, and confirm a signed delivery reaches your handler.
- Complete organization verification.
- Generate a separate production key and run one controlled live payment before opening the flow to customers.
Confirm the integration is production ready
Before real customers reach it, check that your integration:
- Creates checkout sessions from a trusted server, never from browser code.
- Stores your own order alongside the Seev reference so the two can be reconciled.
- Sends a stable
Idempotency-Keywhen it retries a create request. See Idempotency. - Redirects customers only to the checkout URL Seev returned.
- Verifies payment results server-side before fulfilment, treating the browser redirect as a hint rather than a result.
- Deduplicates webhook events on the payment reference, because event IDs change on replay. See Webhooks.
- Shows customers a useful pending state and a useful failed state.
- Keeps sandbox and production credentials in separate secret stores.
Unblock a dashboard that will not let you proceed
| Message or symptom | Cause | What to do |
|---|---|---|
| Developer terms must be accepted | The active organization has not accepted the API terms. | Open Seev API and complete the terms step. Terms are per organization, so accepting them once does not cover the others. |
| Production requires verification | Organization verification is not approved. | Finish verification, or switch back to sandbox and keep building. |
| Developer account disabled | Developer access is in the disabled mode for this organization. | API actions are unavailable until it is re-enabled. Follow the guidance shown on the screen. |
| No keys are listed | You are looking at a different environment or a different organization from the one that owns the keys. | Check the environment selector and the organization selector, then reload the tab. |
Requests return 401 | The key does not match the product, the environment, or the current key format. | Work through the error table in API Keys. |
Find your money after a successful payment
Funds from successful API transactions are deposited into your main Seev account, where you can withdraw them or move them to another wallet. The Developer Transactions tab shows only API-created activity, so invoices, payment links, and storefront orders will not appear there. See Developer Transactions.