BursaPay Logo
Knowledge Base
Ticket Sign In
Help Center > Developer Platform & Gateway API > Developer API Key Rotation, Disable and Revoke

Developer API Key Rotation, Disable and Revoke

Published 2026-08-23 6 min read
Who is this article for?
This guide is for Developers, Security Teams seeking operational guidance on BursaPay workflows.

UI Navigation Path (Step-by-Step)

  1. Identify the active key.
  2. Rotate when a secret needs replacement.
  3. Update the application configuration.
  4. Disable or revoke the old credential after confirming the replacement works.
Verified BursaPay gateway workflow: Explains the API-key lifecycle actions exposed by the developer platform.

1. Overview & Purpose

The gateway supports key rotation and disabling; rotation invalidates the old key and is recorded in activity/audit history.

2. Requirements & Setup

Know which application is using the key before changing it.

3. Step-by-Step Workflow

  1. Identify the active key.
  2. Rotate when a secret needs replacement.
  3. Update the application configuration.
  4. Disable or revoke the old credential after confirming the replacement works.

4. Rules & Troubleshooting

A rotation is a credential change, not a harmless display action; plan for propagation across deployments.

5. Verification & Next Steps

Verify successful authenticated requests with the new key before removing the old deployment secret.

Was this article useful?

Related Articles

Developer API Key Types and Environment Prefixes Developer API Authentication Headers
Ask Bursa AI