Credentials
Everything you copy from the dashboard before the first API call.
Portal
Sign in at the dashboard. The workspace must be active before API keys work. Owners create keys and set the webhook. The dashboard session cannot call /v1.
- Open Settings → Developer — copy Merchant ID, Base URL, and create an API key (shown once). Two active keys is the limit. Revoke one before creating another.
- Open Settings → Notifications — save your callback URL and store the signing secret on the server.
- Open Settings → Merchant for workspace name and logo, then Settings → Checkout for timeout, redirects and tolerances.
Values
| Field | Where | Used for |
|---|---|---|
Merchant ID | Settings → Developer | Support and reconciliation. Not sent on API calls. |
API key | Settings → Developer | Authorization: Bearer pk_… |
Base URL | Settings → Developer | All /v1 routes. https://api.bytix.ai |
Webhook URL + secret | Settings → Notifications | Order and payout notifications, with an optional separate payout URL. One secret signs both. Rotate to reveal it once. |
Display name / logo | Settings → Merchant | Shown in the checkout popup |
Timeout, return URLs, tolerances | Settings → Checkout | Popup defaults and payment matching |
Deposit deduction | Settings → Fees | Optional shortfall allowance per asset. Off until you turn it on. |
Rotate
Resetting keys revokes every active prefix immediately. Update the CRM env var before the next create. Rotating the webhook secret invalidates the previous HMAC — deploy the new secret first, then rotate, or deliveries fail until you catch up.