The case reports that Polybetting was embedded into an existing operator wallet for already eligible and verified users. It also reports $1M of handle by day 7 and that, after the casino cross-sell flow went live on day 14, roughly 22% of defined Polybetting sessions touched a casino product in the same session.
These are anonymised partner-reported observations, not proof of incremental acquisition or retention. Publication-grade use requires contract and go-live dates, handle-counting method, eligible sessions, denominator, bot/test exclusions, product-touch event, sample size and source export. The delivery case does not establish permission in another jurisdiction.
The launch is an input to a LATAM rollout plan, not a universal template. Operators should separately scope product authorization, wallet/KYC controls, venue rights, settlement and a controlled cross-sell measurement plan; contact the team for the defined implementation scope.