Support · Troubleshooting
Flagged fee but we refunded separately
Promotional waivers and corrections refund application fees without touching the charge. Reasoning fee-first flags every one of them as a missing reversal that is not missing — the reasoning direction is the bug.
Why it happens
A fee refunded standalone creates an application_fee.refunded event with no corresponding charge refund. Checks that start from the fee and look outward see "fee refunded but transfer not reversed" — true, and completely fine.
The correct reasoning direction
Always start from the charge: did the charge refund? Then check transfer proportionality and fee proportionality together via net position. Standalone fee events attach to charges that were never refunded, and net position confirms the platform is whole.
What to do with the finding
Dismiss it with the standalone-fee-reason code. The dismissal requires the reason so the queue stays explainable — and if the same waiver flow keeps triggering findings, that flow deserves a policy note so future reviewers understand instantly.