The platform

Got an audience?
You run the game.
We run the pot.

Game developers, media brands, social channels and charities can all use Plucky to provide real money competitions to their audience — outsourcing payments, the prize handling, the compliance/regulation and the record-keeping, without building any of it.

We call it BaaS (Betting as a Service). You run the competition and the standings; Plucky runs the real money contest.

Registering tells us who you are. It does not create a commercial agreement — we will talk to you before anything goes live.

Fig. 1 — the stackHow a partner competition layers onto a Plucky contestThree stacked planes. At the top, the partner’s competition holds the rules, the tickets and the standings. Beneath it, the Plucky contest holds entries, the pot and settlement. At the base, the platform: compliance, payments, the double-entry ledger that records every movement of money, and reporting. Plucky reads the competition and shadows it with the contest; the contest and the platform are the same system.CompliancePaymentsLedgerReportingevery movement of moneyPlucky contestentries · pot · settlementYour competitionrules · tickets · your standings

The integration

Three crossings of the boundary

That is the whole contract. One document we read from you, one link your player follows, one webhook we send you. You never create, close or settle a contest — there is no call that could. Taking the money, holding it, paying by your ranks: all of it happens below the line.

Fig. 2 — what crosses, and what never doesWhat crosses the boundaryA horizontal line divides the partner’s side above from Plucky’s side below. The competition snapshot comes across by push or pull, players cross on a deep link, state updates follow, and notifications go back. Customer identity, card details and wallet balances stay below it and never reach the partner.YOUR SIDEPLUCKY’S SIDEcompetition snapshot (push/pull)deep link (player)state updatesnotificationsNEVER CROSSESnames · email · card details · wallet balances
  1. 01plucky → you

    Publish your competition

    GET {competitionUrlBase}/{partnerCompetitionId}

    One document per competition: its state, entrants, closing time and table. We pull it when a player arrives and periodically while a contest is live. The same closed document is fine until the result changes; send intermediate rankings only if you want them displayed in the Plucky app.

  2. 02your player → plucky

    Send a player across

    GET /p/{slug}/competitions/{id}

    A signed link says who the player is on your platform and which competition they came from. Nothing more. We open the contest, take the stake, and remember them through sign-up and verification.

  3. 03plucky → you

    Hear what happened (optional)

    contest.entry.paid · contest.payout.completed

    One webhook URL, one signed POST per event. When your standings go final we settle by your ranks, pay winners into their Plucky wallet, and tell you we did.

Yours

Your competition, our contest

Bring the competition and the audience. Plucky opens the contest, takes the entries, holds the money and pays by your standings.

Ours

Built for scrutiny

Every entry, prize and payment is recorded in a double-entry ledger — the same numbers we report on.

Yours

Your people, your account

Invite colleagues into your organisation and manage who can act for it.

In numbers

5min
Signed-link window

How long a signed link stays valid. We remember the player after that.

7tries
Webhook attempts

One immediate, then a backoff ladder out to 24 hours.

60/min
Partner API rate

Per key, every route. Over it, a 429 carries Retry-After.