Redact sensitive fields when logging external API requests #3004
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue: https://github.com/antiwork/gumroad-private/issues/52
Private repo PR: https://github.com/antiwork/gumroad-private/pull/78
Ref
Description
Problem
Several code paths log external service payloads directly at info level.
These logs may include sensitive credentials such as:
Logging these values in plaintext poses a security risk.
Solution
Introduce a centralized log redaction utility that safely sanitizes sensitive fields before logging
Before/After
Paypal rest API
Before
After (Authorization and Paypal-Auth-Assertion filtered)
Paypal payouts
Before
After (verify_sign filtered)
Stripe Connect
Before
After (token and stripe_publishable_key filtered)
AI Disclosure
Cursor - Claude Sonnet 4.5 for code generation, self reviewed by me