Short version: when a withdrawal via Trustly (or a bank wire/instant bank-transfer workflow that looks like Trustly) sits in “Requested” or “Processed” on an offshore cashier for more than five business days, panic is understandable — but there are rational steps to take that significantly raise your odds of a clean resolution. This guide is written for Australian mobile players who use Fairgo and similar offshore sites. It explains the queue mechanics you need to check, where miscommunication usually happens, the limits of KYC troubleshooting, and the pragmatic script and escalation path to get an answer from finance rather than canned support replies.
How the “pending” lifecycle usually works (and why 5 days isn’t always a catastrophe)
On many offshore sites the withdrawal lifecycle has at least three visible states: Requested, Processed, and Paid (or equivalent labels). “Requested” normally means your withdrawal is live in the operator’s queue and awaiting a manual or batch action from finance. “Processed” commonly means the operator has completed internal clearing and handed the transfer to their payment partner or bank. The final “Paid” stage is when the receiving bank shows a credit.
Key trade-offs and practical realities for Aussies:
- Manual reviews: Operators run anti-fraud and KYC checks. Even with KYC approved previously, a separate payment review can flag additional checks or require a wire batch number.
- Batching and cut-offs: Many sites send outbound wires in batches a few times per week. If you miss a batch cut-off by hours, you may wait several business days before your transfer is grouped and sent.
- Intermediary banks: Offshore operators sometimes route payments through correspondent banks; each hop adds 24–72 hours depending on weekends and public holidays in routing countries.
- Australian banking delays: Once the payment hits the Oz banking system, some small banks and processing rules can add another 24–72 hours — weekends and public holidays matter.
So a >5 business day pending period is a clear sign to escalate, but not necessarily proof of loss. It more often indicates a missing batch, additional verification or a routing problem that Finance or the payment partner must fix.
Immediate checklist: three status checks you must run right now
When you spot a withdrawal older than five business days, follow these three checks in order so you and support are talking about the same thing.
- Check Status Label: Is the cashier showing “Requested” or “Processed”? If it’s “Requested”, your request is still in the operator queue — you have not been paid nor has the payment left the operator’s finance desk. If it’s “Processed”, the operator claims to have handed it off to payments; that’s when you push for a wire/batch reference.
- Check Email Thoroughly: Search your mailbox (including spam) for keywords Fair Go uses: “Fair Go Verification”, “Finance”, “Payment”, or the exact site email headers. Operators often request additional ID or bank proof via email rather than an onsite alert.
- Time Window: Confirm that >5 business days have passed, not calendar days. Weekends and public holidays in AU do not count as business days for many bank processes.
Script and escalation: what to paste into chat or email
If you’ve done the checks and the withdrawal is still pending after five business days, use a tight, unambiguous escalation script. It reduces back-and-forth and forces support to engage Finance rather than regurgitate policy text.
Use this exact message (copy-paste):
My withdrawal requested on [DD/MM/YYYY] is still pending. My KYC is approved. Please escalate to the finance team for an update on the wire batch number.
Add your account ID and the withdrawal ID in the same message. On mobile, screenshot the cashier status and attach it. That combination (date, KYC approved, wire-batch request + screenshot) is the minimal, high-value data Finance needs to locate the payment in their internal ledger.
Where support usually trips up (and how to avoid their common replies)
Typical low-value replies from chat: “We are processing your request,” “KYC is pending,” or “Please wait 24–48 hours.” These are useful when true, but they become frustrating if repeated after you’ve shown KYC is approved. To force a meaningful response, keep escalating until you have:
- Confirmation of the status label used by Finance (Requested vs Processed).
- The wire batch number or payment reference Finance used when sending the transfer.
- The name of the payment partner or bank used for the outbound wire (so you can chase your bank with the reference).
If chat refuses to escalate, switch channels: open a fresh email to their support address, include the script above, attach your KYC approval screenshot, and request a ticket number or reference.
Risks, trade-offs and limitations
Understanding risk helps you make decisions under uncertainty rather than panic.
- No guarantees with offshore operators: Because stable project facts for Fairgo’s internal payout cadence aren’t public here, you should treat every delay as a risk that requires documentation. Offshore operators are not regulated under Australian casino rules, so enforcement options are limited.
- KYC approved ≠ instant payout: KYC clearance removes one common cause of delays, but payment reviews and AML holds can still trigger additional requests (proof of source of funds, proof of bank ownership, etc.).
- Chargebacks and frozen funds: If you used a card deposit and then request a withdrawal, operators sometimes require a bank wire to the same card-owner bank account. Card networks can impose holds that create extra steps.
- Escalation friction: Finance teams are transactional and may need time to trace routed payments. You may reach a resolution faster if you provide precise info (date, withdrawal ID, screenshots) upfront.
Quick comparison: What to expect by payment type (practical AU mobile player view)
| Method | Typical total time | Main delay points |
|---|---|---|
| Crypto (BTC/USDT) | 3–7 days | Operator pending + blockchain confirmations |
| Trustly / Instant Bank-style | 5–10 business days | Operator queue, batch sends, correspondent banks |
| Bank wire (card refunds) | 7–15 business days | Manual review, card network holds, intermediary banks |
What to watch next (decision cues)
If you get a wire batch number from finance, call or message your bank (CommBank/ANZ/NAB/Westpac/Macquarie) with that reference. If the bank locates an inbound holding, you’re close to resolution. If neither operator nor your bank can produce evidence after reasonable escalation, preserve all records (screenshots, chat logs, timestamps) and consider an external complaint route — though remember enforcement options for offshore sites are limited from Australia.
Q: My cashier shows “Requested” for 7 business days — is my money lost?
A: Not necessarily. “Requested” usually means still in the operator’s internal queue. Use the escalation script to force a finance trace and request a batch/wire reference. Loss is a last-case scenario; start with documentation and escalation.
Q: Support keeps saying “KYC pending” but I already uploaded docs — what now?
A: Ask for the specific KYC field they claim is missing. Attach a screenshot of your KYC-approved status and the timestamp. If their messages remain generic, move to email and explicitly request a ticket number and a finance escalation.
Q: Should I cancel the withdrawal and try again?
A: Only if support confirms the transaction hasn’t been sent to payments (status: Requested) and cancelling won’t trigger additional holds. Cancelling a withdrawal after it’s been handed to payments can complicate the trace.
Practical record-keeping tips (do this immediately on mobile)
- Screenshot the cashier page showing the withdrawal ID, status, and timestamp.
- Save the chat transcript (copy-paste into a note) and tag each message with date/time.
- Forward any verification or finance emails to a dedicated folder and keep originals — don’t rely on in-app alerts only.
For a broader operator overview or to check the site’s user-facing policies before escalation, see a focused review at fairgo-review-australia.
About the author
William Harris — senior analytical gambling writer focused on player protection and casino payment workflows. I research banking mechanics, KYC friction points, and practical escalation strategies so mobile players can resolve withdrawals with less stress and better documentation.
Sources: Operator payment mechanics described here are drawn from general industry practice and known offshore payout behaviours; no fresh project-specific news or validated internal Fair Go payout schedules were available at the time of writing. Always treat delays as an operational risk and document everything.