Net sales by day
Sales minus refunds. Refunds count on the day they were made.
| Period | Sales | Gross | Refunds | Net |
|---|
No sales or refunds in this period.
| Paid | Customer | Amount | Status | Payment |
|---|
No payments found.
Sales minus refunds. Refunds count on the day they were made.
| Period | Sales | Gross | Refunds | Net |
|---|
No sales or refunds in this period.
| Paid | Customer | Amount | Status | Payment |
|---|
No payments found.
Most recent 300 events since the server last started. Payments themselves are stored permanently. See the Payments tab.
Nothing yet. Events appear here as they happen.
SECRETS_ENCRYPTION_KEY. On the server, run npm run create-encryption-key,
back up the key it creates, and restart. Until then, values are read from .env only.
Payment provider credentials. Secrets are encrypted in the database (AES-256-GCM) and are never shown again after saving; only their last four characters are displayed. Saving or removing one asks for your admin password, and changes apply immediately.
Keys let other systems subscribe to the payment feed at
A key only receives payments and refunds of its mode. Use a Test key for staging and development, and a Live key for production systems. You can change a key's mode later.
Copy this key now. It won't be shown again. Only a hash is stored.
Clients send it as Authorization: Bearer <key> when connecting.
| Name | Key | Mode | Created | Last used | Connections | Status | Actions |
|---|
No keys yet. Create one above to let a system connect.