Protecting credentials to move money.
WHAT SECRETS EXIST IN PAYMENT SYSTEMS
Provider interface keys Signing secrets for notifications Encryption keys Database credentials
WHAT A COMPROMISED PROVIDER KEY ENABLES
Initiating payments, refunds and payouts as you.
WHY THAT IS THE MOST SERIOUS EXPOSURE
It moves money directly.
WHAT TO NEVER DO
Commit keys to version control Put them in client-side code Send them in messages or tickets Share one key between environments
WHAT SEPARATE KEYS PROVIDE
Containment, and the ability to revoke one without stopping everything.
WHAT TO USE
A secret management system, with access controlled and logged.
WHAT TO RESTRICT
Which systems may use which key What each key is permitted to do, where the provider supports scoping
WHY SCOPING MATTERS
A key that can only read cannot initiate a payout.
WHAT TO ROTATE
Keys, on a schedule and immediately on any suspicion.
WHAT TO TEST
That rotation works, before you need it urgently.
WHAT TO MONITOR
Use of keys from unexpected sources Actions outside normal patterns
WHAT TO PREPARE
A revocation procedure, executable in minutes.
