API Customers
Understand customer summaries derived from Seev API transactions.
API Customers is a read-only view generated from transactions created by your API integration. It helps you see who has paid through Checkout API without creating or maintaining a separate customer record in the Developer Dashboard.
What the table shows
| Field | Description |
|---|---|
| Customer | Customer name when available, otherwise the best available email, phone, customer ID, recipient ID, or record ID. |
| Email and phone | Contact information supplied by the API transaction, when available. |
| Transactions | Number of API transactions associated with the customer. |
| Total volume | Sum of the customer's API transaction amounts in the reported currency. |
| Last status | Status of the most recent API transaction. |
| Last reference | Latest payment or session reference. |
| Last activity | Date and time of the most recent API transaction. |
Sandbox customers are visibly marked and remain separate from production customers. Changing the Developer Dashboard environment reloads the customer list for that environment.
Some sandbox transactions do not contain a name, email, or phone number. The dashboard displays a fallback identifier so these records remain inspectable.
Customer creation and editing are not available in this view. To manage customers saved for invoices and payment links, use the Dashboard Customers guide.
Use the view to answer common questions
- Who has used my API integration? Check customer identity and environment.
- How often have they transacted? Review transaction count.
- What is their total API volume? Review total amount and currency.
- What happened most recently? Check last status, reference, and activity time.
Open the related transaction using the last reference when you need request metadata, timestamps, or payment details.
Missing customer details
Some integrations or sandbox sessions do not provide a name, email, or phone. Seev shows the strongest remaining identifier instead of a blank row.
If production customer details are unexpectedly absent, review the recipient fields your integration sends when it creates checkout. Do not edit the summary to guess the customer's identity.
Environment safety
Sandbox and production customer summaries are separate. Always check the environment badge before using customer totals for reporting or support.