Paddle
For SaaS teams running Paddle as merchant of record, Strkr surfaces subscription state, invoice history, and payment status on the matching account. CS and finance read from the same record.
Everything Paddle does inside Strkr.
- Subscription status on the account
- Invoice history visible to CS
- Payment-failed alerts into Flows
- Multi-currency, multi-geo tax handled by Paddle
Native code, not a shim.
OAuth where available
Paddle will ship with a native OAuth flow when it lands. No pasted credentials for admins to rotate manually.
KMS-encrypted tokens
Access and refresh tokens are envelope-encrypted at rest using a dedicated customer-managed KMS key. Decryption only happens in Lambda memory during an active API call; plaintext tokens never land in a log.
Shared by the workspace
A workspace admin connects Paddle once; every teammate uses the shared connection without re-authenticating.
Disconnect at any time
Admins or users can disconnect Paddle from inside Strkr. Stored tokens are deleted and the provider's revocation endpoint is called within 24 hours.
Paddle is on the roadmap.
We ship integrations as first-class native code, which takes a little longer than a Zapier shim. If Paddle is a dealbreaker for your evaluation, reply to the welcome email after you start a trial and we'll flag it to the roadmap.