Separation of duties on money
A fee change, a payout or a refund needs a proposer and a different approver, both identified, both recorded. The database refuses a record where the two are the same person, so it is a structural control rather than a policy anyone can decide to skip.
Changes are appended, never overwritten
Pricing and fee rules are never edited in place. A change closes the old rule and opens a new one, so what a customer was charged last year remains explicable this year. A settled payment stores the numbers it was charged under rather than a pointer to a rule that can move.
Identity is proven, not asserted
Internal systems do not take another system's word for who is calling. Staff identity is carried by a signed assertion the receiving service verifies itself, so holding a shared secret is not the same as being an administrator.
Customer content is not a product
We do not scan customer mail or files, and we do not sell customer data. There is no advertising product pointed at customer content, which is what makes that a structure rather than a promise.