Fact-check findings
What an automated fact-checker found when it re-read Triple-A against the sources the page cites. Only the most recent review is shown.
These findings are produced by an automated reviewer, and its results vary between runs: the same page, checked three times on the same day, came back with 15%, 20% and 34% of its claims disputed, mostly because each run extracted a different number of claims. Treat what follows as leads, not rulings.
“Disputed” means the reviewer could not reconcile the claim with the evidence it cited. It does not mean the claim is false. “Unverifiable” means no reachable source settled it either way.
Nothing here changes the page on its own. A proposed correction is applied only after a human moderator approves it; until then the page reads as it did when reviewed.
unverifiable
2 claimsNo source the reviewer could reach confirms or contradicts the claim.
- #4[unverifiable][awaiting moderator]in section: Regulatory Licensing and Compliance
“the company announced this license on November 30, 2021, saying MAS had reviewed more than 170 applicants before approval”
reviewerMAS lists Triple-A as a Major Payment Institution; license announced Nov 30, 2021I did not fetch the MAS registry or the PYMNTS article in this pass, so this is not scored. Archive copies exist for both. - #5[unverifiable][awaiting moderator]in section: Customer Complaints and User Experience
“Triple-A holds a 3.5-out-of-5 TrustScore on Trustpilot across roughly 309-311 reviews on various regional Trustpilot domains”
reviewerTrustpilot 3.5/5 across about 309-311 reviews, 82% reply rateTrustpilot is a dynamic page and was not fetched in this pass. The page already hedges these figures.
partially supported
1 claimThe cited evidence supports part of the claim but not all of it.
- #1[partially supported][awaiting moderator]in section: July 2026 Security Incident — Treasury Hot Wallet Breach
“On July 25, 2026, attackers gained unauthorized access to Triple-A's own treasury hot wallets (as distinct from customer funds).”
reviewerAttackers gained unauthorized access to treasury hot wallets on July 25, 2026Sources support detection on July 25. The page also says outflows were flagged on July 24, so the stated access date sits awkwardly with that. The access date is better read as the date Triple-A detected the access.
confirmed
2 claimsThe cited evidence supports the claim as written.
- #2[confirmed][no action needed]in section: July 2026 Security Incident — Treasury Hot Wallet Breach
“Triple-A publicly confirmed unauthorized access to company treasury wallets on Monday, July 27, 2026.”
reviewerTriple-A confirmed on Monday July 27, 2026, that customer funds were unaffected, with a roughly three-hour maintenance mode and cooperation with the Singapore Police ForceThe company statement details match the sources. - #3[confirmed][no action needed]in the summary
“Triple-A hack losses reach $11.8M”
reviewerEstimated loss of about $11.8M per Specter; PeckShield about $9.7MThe quoted_text here is a source title and does not appear verbatim in the page prose. The finding is retained for the substance only: the figure is supported by the sources. The page's own wording is 'an estimated $11.8 million' in the summary.