BursaPay Logo
Knowledge Base
Ticket Sign In
Help Center > Developer Platform & Gateway API > Gateway API Key Security and Storage Rules

Gateway API Key Security and Storage Rules

Published 2026-08-24 5 min read
Who is this article for?
This guide is for Developers, Engineering Teams, Platform Operators seeking operational guidance on BursaPay workflows.

UI Navigation Path (Step-by-Step)

  1. Create a key in the developer portal.
  2. Copy the secret value at creation time.
  3. Store it in your application's secret store.
  4. Use only the masked prefix for logs or support references.
Verified BursaPay workflow: Explain how developer API keys are stored and which key material must never be exposed.

1. Overview & Purpose

DeveloperApiKey stores key prefixes and hashes; only test secret-key plaintext may be retained in encrypted form for the sandbox proxy.

2. Requirements & Setup

Keep secret keys on a server-side secrets manager and limit live-key access.

3. Step-by-Step Workflow

  1. Create a key in the developer portal.
  2. Copy the secret value at creation time.
  3. Store it in your application's secret store.
  4. Use only the masked prefix for logs or support references.

4. Rules & Troubleshooting

Live secret-key plaintext must never be persisted by application code. Never put secret keys into frontend bundles, screenshots or logs.

5. Verification & Next Steps

Rotate compromised keys immediately and review recent API logs afterward.

Was this article useful?

Related Articles

API Key Rotation, Disable and Revocation
Ask Bursa AI