Guides
  1. Authentication & Credentials

SDK Tokens

How SDK tokens work for SoftPOS, SmartPOS, and mobile SDK apps.

SDK tokens authenticate DigetPay SoftPOS and mobile SDK applications. Manage them from the dashboard or Portal API.

📘

SDK tokens are separate from payment x-api-key values. Use Portal Bearer auth for token API endpoints. For more details about SDK token authentication and provisioning, see SDK Tokens & Authentication.

Use cases

ProductGuide
SoftPOSSoftPOS Overview
SmartPOSSmartPOS Overview
Mobile SDKSDK Overview

Dashboard flow

  1. Settings → SDK Tokens (label may appear as Terminals on some accounts)
  2. Generate token — assign userId, label, terminal ID if applicable
  3. Copy tokenPlain once and provision to device over secure channel
  4. Deactivate lost or compromised tokens immediately

Generate token (Portal API)

sequenceDiagram
    autonumber
    participant Admin as Merchant Portal
    participant DigetPay as DigetPay Portal API
    participant Device as SoftPOS App

    Admin->>DigetPay: POST /merchant/account/sdk-tokens
    DigetPay-->>Admin: tokenPlain (once), tokenMasked, active
    Admin->>Device: Secure provisioning
{
  "userId": "terminal-user-001",
  "label": "Store Terminal 1"
}
❗️

Critical: tokenPlain is shown once. Provision immediately to the device.

Deactivate token

{
  "active": false
}

PUT /merchant/account/sdk-tokens/USERID

🚧

Lost device: Deactivate before issuing a replacement token.

Portal API endpoints

ActionMethodPath
Generate / rotatePOST/merchant/account/sdk-tokens
Update statusPUT/merchant/account/sdk-tokens/USERID
List tokensGET/merchant/account/sdk-tokens

API Reference →

Security

  • One token per terminal or app instance where possible
  • Never commit tokens to Git or share in chat
  • Rotate on staff change or device loss
📘

For additional guidance on SDK token authentication, provisioning, and token usage, see SDK Tokens & Authentication.

Related

Updated about 1 month ago

Did this page help you?