Transform Online Casino into Sweepstakes Platform

Hi we have a platform for online casino, we want to transform it into sweapstake. We need to remove most of the games and it needs to remain only 11/12 slot games. Hi,

I’m building a U.S. sweepstakes casino platform. I want the first version built with the following structure.

1. Accounts

* Players must be 21+.
* One account per person.
* Registration should collect name, DOB, email, phone, address, and other required information.
* Build the system so KYC/identity verification can be integrated before redemption.
* Add fraud detection and duplicate-account detection.

2. Gold Coins (GC)

* New eligible users receive 10,000 GC free after registration.
* GC can also be purchased through packages.
* GC have no cash value and cannot be redeemed.
* The GC package system needs to support a promotional SC bonus attached to qualifying purchases.

Example:
$19.99 → [GC amount] + [SC amount] promotional bonus

Important: SC must NOT be presented as something the customer is directly purchasing.

3. Sweeps Coins (SC)

SC can be awarded through:

* Qualifying GC purchase promotions
* Daily bonuses
* Promotions
* Referral rewards
* AMOE

The backend needs a complete SC ledger showing:

* Date/time
* Source of SC
* Amount
* Promotional ID
* Play-through status
* Amount wagered
* Redeemable balance
* Redemption history

4. Slot Games

Initially I only want slot games.

The system needs to support:

* GC gameplay
* SC gameplay
* Bet amount
* Win amount
* Loss amount
* Game/session ID
* Transaction ID
* SC play-through tracking

Every SC wager needs to count toward the player’s play-through requirement.

5. SC Play-Through

Our initial rule will be:

1× play-through requirement.

Example:

Player receives 150 SC.

They must wager at least 150 SC through eligible slot gameplay before that SC becomes eligible for redemption.

They do NOT have to lose the 150 SC.

Example:
150 SC deposited/promotional balance → 150 SC total wagered → requirement completed.

If the player finishes with 180 SC, the 180 SC can remain in their account and potentially become redeemable once all other requirements are satisfied.

Please build a visible progress tracker:

Redemption Progress: 125 / 150 SC

The exact accounting needs to be done on the backend, not just displayed on the frontend.

6. Redemption

Minimum redemption:

150 SC = $100

The player should not be able to submit a redemption request until:

* They have at least 150 redeemable SC;
* Required play-through has been completed;
* KYC has been completed;
* Their account is eligible;
* Their physical location is eligible.

Redemption options should support:

* Cash
* Gift cards

Please build redemption as a separate wallet/ledger system rather than simply subtracting the player’s displayed SC balance.

7. KYC

Before a player can redeem, integrate a KYC provider.

The system should support:

* ID verification
* DOB verification
* Name verification
* Address verification
* SSN/tax verification where required
* Fraud/risk checks

The KYC status should be stored as something like:

Unverified
Pending
Verified
Failed
Manual Review

8. Geolocation

We need geolocation because the site will not be available everywhere in the U.S.

Build a geolocation layer that can:

* Determine the player’s physical state;
* Block restricted states;
* Prevent VPN/proxy/location spoofing where reasonably detectable;
* Re-check location when appropriate;
* Prevent gameplay/redemption when the player is in a restricted jurisdiction.

DO NOT hard-code the final state list yet.

Create an admin-controlled configuration such as:

Eligible States:

* State A
* State B
* State C

Restricted States:

* State X
* State Y

I need to be able to change state availability without deploying new code.

9. AMOE

Build an AMOE system/page.

It should be possible to:

* Publish AMOE instructions;
* Define eligibility;
* Define SC award amount;
* Track AMOE requests;
* Approve/reject requests;
* Prevent duplicate/abusive requests;
* Keep a complete audit trail.

The exact AMOE method and requirements will be provided after legal review.

10. Promotions

Build a promotion engine that can support:

* Daily SC bonuses
* Signup promotions
* Purchase-linked SC bonuses
* Referral bonuses
* Promotional campaigns
* Expiration dates
* Maximum awards
* Eligibility rules
* Play-through requirements

Every promotion should have its own ID and configuration.

11. Admin Dashboard

I need an admin dashboard where we can manage:

* Users
* GC balances
* SC balances
* Transactions
* Game activity
* Play-through progress
* Redemptions
* KYC status
* Fraud flags
* Geolocation status
* Promotions
* AMOE requests
* State availability
* Account suspensions
* Customer support notes

Every important action needs an audit log.

12. Payments

Do NOT integrate a normal payment processor until the business/payment model has been approved by the appropriate payment provider.

The architecture should allow us to connect a specialized payment processor later.

Payment records should include:

* Transaction ID
* User ID
* Amount
* Package purchased
* GC awarded
* Promotional SC awarded
* Payment status
* Refund/chargeback status
* Timestamp

13. Wallet/Ledger

This is extremely important.

Do not use a simple editable balance field.

Create an immutable transaction ledger for both GC and SC.

Every balance change should have:

* User ID
* Currency type
* Amount
* Transaction type
* Source
* Reference ID
* Timestamp
* Before balance
* After balance

This needs to make it possible to audit exactly how a player obtained and used every SC.

14. Security

Implement:

* 2FA/admin security
* Encryption
* Secure authentication
* Rate limiting
* Fraud monitoring
* Device/IP monitoring
* Duplicate-account detection
* Admin activity logs
* Secure payment-token handling
* Database backups
* Disaster recovery

Never store raw card numbers.

15. Responsible Gaming / Account Controls

Build the system so we can later add:

* Account limits
* Self-exclusion
* Session/time controls
* Account closure
* Cooling-off periods
* Responsible-play information

16. Important Legal/Compliance Requirement

Do NOT hard-code statements such as:

“Legal in all 15 states.”

The legal team will provide the final state list.

The platform must be configurable so individual states can be enabled/disabled instantly.

Also, the legal team will provide the final:

* Official Sweepstakes Rules
* AMOE rules
* Terms & Conditions
* Privacy Policy
* Redemption rules
* Promotion rules
* State restrictions

The developer should build the system to support these rules, but should not make independent legal assumptions.

17. Main Player Flow

The intended user experience is:

Register
↓
Receive 10,000 GC
↓
Play slots
↓
Purchase GC package if desired
↓
Receive promotional SC with qualifying package
↓
Play SC through eligible slots
↓
Reach 1× play-through
↓
Accumulate at least 150 redeemable SC
↓
Complete KYC
↓
Request $100+ redemption
↓
Compliance review
↓
Cash or gift-card payout

Please design the database and architecture around this flow from the beginning so we don’t have to rebuild the wallet, ledger, redemption, and promotion systems later.