Keep your applications clear.
Use named keys to identify your website, mobile app or business system without adding fields to each request.
A stable application identity
A merchant can create up to 10 named keys. Each named key is the application’s stable identity and has a live secret plus an optional sandbox secret. Use names such as “Online store” or “School fees” to make the dashboard easy to understand.
Responses and webhooks include application_id. New payments snapshot application_name, so renaming a key does not change historical payment attribution. project_id remains an alias of the same ID.
Transaction and webhook boundaries
A key can read only API payments created by its own application and environment. Each application can have one configured HTTPS webhook endpoint. Request history can be filtered by application and environment in the dashboard.
Regenerating a secret preserves application identity, payment reads and idempotency scope. Deleting a key removes access; its previously dispatched payments can still settle. Undispatched API payouts are cancelled and refunded when processed after deletion.