Developer Documentation

QR Verification

Merchant QR Verification

Merchant QR payloads are intentionally minimal:

{
  "type": "sikaahub_merchant",
  "merchant_code": "SHB-MER-000001",
  "qr_token": "secure-random-token"
}

The QR payload never includes database IDs, wallet balances, phone numbers, emails, documents, or owner personal data.

Merchant QR Endpoints

• GET /merchants/me/qr
• POST /merchants/me/qr/regenerate
• POST /qr/verify

QR regeneration requires:

• authenticated merchant
• active merchant status
• X-Device-ID
• transaction PIN

When QR is regenerated, the old active QR is revoked.

Verification Response

POST /qr/verify

{
  "qr_token": "secure-random-token",
  "merchant_code": "SHB-MER-000001"
}

Returns safe display information:

• merchant code
• business name
• business type
• city
• region
• verification status
• whether payment and withdrawal are allowed