title: Minnesota — Technical compliance: What must the platform meet? | advennt.io canonical: https://advennt.io/jurisdictions/minnesota/technical/ [Jurisdictions](https://advennt.io/jurisdictions/) [Minnesota](https://advennt.io/jurisdictions/minnesota/) Technical compliance Minnesota · Question 08 of 11 # Technical compliance: What must the platform meet? Mixed · Uncertain · AI-generated · [Back to full Minnesota report →](https://advennt.io/jurisdictions/minnesota/) Key section parameters | Jurisdiction | Minnesota (US-MN) | |---|---| | Regulator | Minnesota Gambling Control Board (GCB) & Alcohol and Gambling Enforcement Division (AGED) | | Favourability | Mixed | | Confidence | Uncertain | | Review status | AI-generated | | Last collected | 18 Oct 2026 | Summary answer The virtual-currency kiosk wind-down introduces a new technical-compliance requirement: operators removing kiosks statewide must complete customer payouts accompanied by blockchain-recorded proof of transfer by December 31, 2026, a documentary and technical recordkeeping standard that did not previo… ## Full section analysis The virtual-currency kiosk wind-down introduces a new technical-compliance requirement: operators removing kiosks statewide must complete customer payouts accompanied by blockchain-recorded proof of transfer by December 31, 2026, a documentary and technical recordkeeping standard that did not previously attach to the kiosk channel. This requirement is narrowly scoped to the kiosk wind-down obligation rather than to gambling operators' technical infrastructure generally, and it operates independently of House File 3709's bank-custody segregation and notice requirements, which impose their own but distinct technical and procedural obligations on state-chartered banks and credit unions. No RNG-certification, server-location, or gaming-specific technical-standards development was evidenced for Minnesota this cycle beyond this kiosk-channel recordkeeping requirement.