21bit in the product funnel (marketing/dev ops note)
If your casino is crypto-friendly and attracts Aussie punters who like both AUD and crypto, consider listing a trusted partner like 21bit as an example of a dual-rail operator on your demo pages to show how Trustly + crypto can coexist in a UX. This gives commercial context for merchants evaluating performance and helps product teams visualise flows for both casual and VIP punters.
Regulatory & compliance checklist for AU operators
– Understand ACMA and state-level oversight (Liquor & Gaming NSW, VGCCC) even if operating offshore; have a legal opinion document.
– KYC/AML: collect photo ID, address proof (rates notice/bank statement) — Aussies are used to these checks before withdrawals.
– Age verification: 18+; show local help resources like Gambling Help Online (1800 858 858) and BetStop.
– Tax note: player winnings are not taxed in AU, but operators must consider POCT and local operator tax obligations.
Quick Checklist — For devs and product owners deploying Trustly in AU
– [ ] Confirm Trustly bank coverage for major AU banks (CommBank, ANZ, NAB, Westpac).
– [ ] Implement secure webhook handling with signature verification.
– [ ] Add PayID/POLi/BPAY as deposit fallbacks.
– [ ] Integrate KYC at registration; flag high-value withdrawals.
– [ ] Test on Telstra/Optus networks and on common devices (Samsung, iPhone).
– [ ] Communicate clear bet/wager rules for bonus funds and max-bet limits in AUD (e.g., A$5, A$50).
– [ ] Provide responsible-gambling links (Gambling Help Online, BetStop).
Common Mistakes and How to Avoid Them
– Chasing instant settlement without reconciling KYC: slow payouts on first withdrawal are normal; warn players to upload ID early.
– Ignoring small banks: include POLi/PayID to capture regional punters.
– Overlooking timezone/bank holiday impacts: Aussie bank holidays (Australia Day, ANZAC Day, Melbourne Cup Day) affect settlement times — plan customer messaging.
– Not negotiating fees: Trustly offers volume discounts; start conversations early.
Mini-FAQ (for Aussie devs & ops)
Q: Is Trustly legal for Australian players?
A: Trustly is a payment rail; legality depends on your platform’s licensing and how you accept players. ACMA enforces the Interactive Gambling Act for services offered to people in Australia; players aren’t criminalised, but operators must be careful.
Q: How fast are withdrawals via Trustly?
A: Many sites report T+0 visibility for deposits and T+0–T+1 settlements to operator accounts; first withdrawals are often delayed for KYC checks.
Q: Should I keep crypto rails if I add Trustly?
A: Yes — crypto remains popular with Aussie punters on offshore sites as a fast-payout fallback and for privacy; but factor in FX and on/off-ramp costs.
Q: What local payment rails should I support alongside Trustly?
A: POLi for bank-linked deposits, PayID/Osko for instant bank transfers, BPAY as a fallback, and Neosurf or crypto for privacy-minded punters.
Responsible-gaming note
18+ only. Include links to Gambling Help Online (1800 858 858) and BetStop for self-exclusion options, and offer deposit/session limits and voluntary cool-offs in your UX.
Sources
– ACMA & Interactive Gambling Act 2001 (official guidance)
– Trustly developer documentation (integration & webhooks)
– Australian banking Open Banking/PayID materials
– Industry posts and operator case studies (publicly available)
About the author
A product/engineering lead with hands-on experience integrating payment rails for AU-facing gambling products. Practical experience includes implementing Trustly, POLi and crypto on several offshore casinos serving Aussie punters; focused on UX-first integrations, KYC workflows, and low-lift developer implementations. (Just my two cents — test in sandbox with your legal counsel before going live.)
— End —