Payments: keep a trail from sender to recipient
A payment can pass through a processor that is distinct from the service page. Before authorisation, read the final recipient, domain, currency, fees, and total amount. Conversion can change the charge from an advertised figure. A new domain in the payment flow needs its own identity check. If you cannot tell who receives money, stop and ask the provider to explain the route.
After an action, keep the bank reference and the service's reference separately. The two systems may update at different times. A pending bank entry does not establish an account credit; an account with no update does not prove the bank action will reverse. Compare the amount, date, and time zone before repeating anything. An additional transfer can create a second case while the first is still being processed.
Before withdrawing, read rules for identity checks, permitted methods, and amount limits. If what arrives differs from what was expected, ask for a breakdown from the responsible parties. An unsolicited demand for another payment to “unlock” money should be checked through the provider's published support channel, not the address in the demand.
Describe a mismatch precisely
State what was sent, when, the references from both systems, and each current status. Mask unrelated card and identity details. Ask for a case number. A chronological record can distinguish a processing delay from an unexplained difference.