Developer Transactions

Understand how API transactions are displayed and settled in the Seev developer section.

⬡ Dashboard feature

No API or code integration required

The Developer Transactions tab shows transactions created through Seev API products. It does not replace your main account activity view; it is a focused view for API-created activity.

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

What appears here

Developer transactions include activity created by API products such as:

Product	Example transaction
Checkout API	A customer payment created through your app or server.
Exchange Widget API	An exchange transaction created through an embedded widget.
KYC	Verification-related activity when the product is available.

Dashboard-created activity such as payment links, invoices, or manual account transfers may appear elsewhere in the dashboard depending on how they were created.

Environments

Transactions are separated by environment:

Environment	Meaning
Sandbox	Test transactions from sandbox API requests.
Production	Live transactions from production API requests.

Use the environment switcher in the developer section to change which environment you are viewing.

Filtering transactions

The dashboard can request transactions by period and status.

Periods:

Period	Use case
`day`	View today's API activity.
`week`	Review recent API activity across the current week window.
`month`	Inspect longer trends and recent volume.
`year`	Review high-level activity over time.

Statuses:

Status	Meaning
`completed`	The transaction completed successfully.
`pending`	The transaction is still processing or waiting for confirmation.
`failed`	The transaction failed or could not be completed.

The overview graph uses these filters to summarize API activity, and the failed transactions section uses the failed status filter to focus on failed API transactions.

Transaction fields

Field	Description
Reference	Your transaction reference or the generated Seev reference.
Product	The API product that created the transaction.
Type	The transaction type, such as payment.
Amount	The transaction amount and currency.
Status	The current transaction status.
Date	When the transaction was created.

Select a transaction row to open its detail panel. The panel can include customer information, the developer and gateway references, description, metadata, creation and update timestamps, and any additional fields returned for that transaction.

Investigate a payment

When a customer reports a problem:

Confirm whether you are viewing sandbox or production.
Search for the reference stored with your own order.
Open the transaction and compare amount, currency, product, and timestamps.
Check the latest status.
Compare the Seev reference with your webhook logs and server logs.

Do not ask the customer to pay again while the first transaction is still pending. Wait for a final result or confirm that the original session can no longer complete.

Status	Recommended action
Completed	Fulfil only after server-side verification or a valid signed webhook.
Pending	Keep the order unpaid and check again; do not duplicate the payment.
Failed	Show a useful retry path and preserve the failed reference for investigation.

API customers

The overview also groups API transactions into read-only customer summaries. Customers are separated by sandbox and production environment and include transaction count, total volume, latest status, latest reference, and last activity. Records without a name or email use their customer, recipient, or transaction-derived identifier instead of rendering a blank row.