RubberDuckStrategiesQ: Why does it require my stripe API secret key?
When I go to connect my Stripe account, it asks for the secret API key in addition to the publishable key. On Stripe, I can only view the secret API key once before I have to generate a whole new one, which would mean redoing other integrations elsewhere I'd rather leave alone. I tried using a restricted API key instead of the secret key, because that has worked for other software integrations, but this time I got an error in Trafft saying that a restricted key wouldn't work. Why does Trafft need the secret key enabling full API access to Stripe? Is it possible to find a workaround and use a restricted key instead?
Nikola__Trafft
Mar 18, 2026A: Hi,
Trafft requires the full Stripe secret API key because this is how we enable Stripe to be fully white-labeled for agency accounts. This allows agency owners to manage payments for multiple sub-accounts while keeping the experience seamless for end users.
Unfortunately, using a restricted key isn’t compatible with this setup, and the only way to change the key is to revoke the current one and generate a new secret key. We understand this can be inconvenient if you have other integrations, but at the moment, full API access is necessary for the functionality we provide.