API Credentials
View, copy, and rotate merchant API keys in the dashboard.
Your merchant API key authenticates payment API requests via the x-api-key header.
Portal management APIs use Bearer token — different from the payment API key. See Credentials & Security.
Where to find keys
Dashboard → Settings → API Credentials
| Environment | Dashboard |
|---|---|
| Fin staging | fin-admin.digetpay.com |
| Production | admin.digetpay.com |
How merchants receive credentials
| Channel | When |
|---|---|
| Onboarding | Issued after KYC — Account Activation |
| Dashboard | View masked key; rotate to reveal new key once |
| Portal API | GET /merchant/account/credentials |
Retrieve credentials (Portal API)
sequenceDiagram
autonumber
participant Merchant as Your Backend
participant DigetPay as DigetPay Portal API
Merchant->>DigetPay: GET /merchant/account/credentials<br/>Authorization: Bearer {portal_token}
DigetPay-->>Merchant: apiKeyMasked, apiKeyPlain?, issuedAt, environment
Rotate API key
sequenceDiagram
participant Merchant as Merchant Portal
participant DigetPay as DigetPay Portal API
participant Prod as Your Servers
Merchant->>DigetPay: POST /merchant/account/credentials/rotate
DigetPay-->>Merchant: apiKeyPlain (one-time)
Merchant->>Prod: Update secrets manager
Critical:
apiKeyPlainis shown once. Store immediately in your secrets manager.
Using your API key
{
"headers": {
"x-api-key": "YOUR_MERCHANT_API_KEY",
"Content-Type": "application/json"
}
}| Rule | Detail |
|---|---|
| Server-side only | Never embed in mobile apps or browser JavaScript |
| Per environment | Separate keys for Fin staging and production |
| Rotation | Update servers before revoking old key |
Related
Updated about 2 months ago
Did this page help you?
