Home/Developers/Docs
What PlayForge does for your game
You build the game. PlayForge handles publishing, players, payments and rewards, so you can spend your time on what makes the game fun.
- Publishing: one integration puts your game in every game centre on the network.
- Audience: fans arrive from PSL and partner channels. No cold start.
- Payments: pay in and pay out are built and tested. You write none of it.
- Rewards: coins, daily rewards and prizes work the same way in every game.
- Advertising: brands sponsor games and prizes, and your game earns from that too.
- Revenue: every play and every rupee is visible in your console.
How the pieces fit
- Build: make your game with the engine you already use.
- Plug in: add the PlayForge SDK to connect coins, rooms and results.
- Publish: submit a build from the console. After review, it goes live across the network.
- Earn: your share of every room and every sponsorship shows in the console.
What games do well here
Casual mobile games that are quick to learn and finish in a few minutes: sports, board, word, puzzle and arcade. Local themes such as cricket, kite flying and classic board games do especially well.
Next steps
Follow the Quickstart to get a test game running in the sandbox, then work through the Submission checklist.
Before you start
- A PlayForge developer account. Apply from the Developers page; the partnerships team replies to every submission.
- A build of your game: Android (APK or AAB) or HTML5.
- About an hour for your first integration.
Step 1: Open the console
When your account is approved, you receive an email invitation to the developer console. Sign in, then create your game under Games → New game. The console gives your game a Game ID.
Step 2: Get your sandbox keys
Go to Settings → API keys and copy your sandbox key. Sandbox keys only work with test coins and never touch real money.
Step 3: Add the SDK to your game
Start the SDK when your game loads, then report each player's score when a round ends.
Step 4: Play a test round
Open your game from the console's Sandbox tab, join a test room and finish a round. Your result appears under Sandbox → Rounds within a minute. If it does not, check that your Game ID matches and that reportResult runs once per player.
Next steps
Work through the Submission checklist, then submit your first build.
Reviewers check every item below. Games that pass all of them usually go live on the first review.
Game
- Build is under 50 MB.
- Playable within 5 seconds on a 4G connection.
- Runs smoothly on a phone with 2 GB of memory.
- Recovers from a dropped connection without losing the round.
- No crashes across ten full rounds.
- Sound can be muted.
Integration
- The SDK starts with your live Game ID.
- A result is reported for every player, every round.
- Coins are only awarded through the SDK.
- Tested end to end in the sandbox.
Art
- Icon, banner and screenshots match the Art and brand kit sizes.
- No text in the outer 10% of the icon.
Game page
- Name and a one-line description.
- How to play, in three short steps.
- Players per round and round length.
- Languages and age rating.
- Studio name.
Content
Your game must follow the content rules in the Developer Agreement: no gambling mechanics outside PlayForge rooms, no adult content and no third-party characters or logos you do not have rights to use.
Next steps
Submit your build from the console, then read the Review process to see what happens next.
Most PlayForge players use mid-range and low-cost Android phones on mobile data. These requirements make sure your game works well for them.
At a glance
| Area | Requirement |
|---|---|
| Build size | Under 50 MB |
| First play | Within 5 seconds on 4G |
| Android | 8.0 and above |
| Memory | Runs on 2 GB RAM phones |
| Frame rate | Steady 30 fps on low-cost phones |
| Orientation | Portrait |
| Languages | English required, Urdu recommended |
Size and load time
Load only what the first round needs, and download the rest in the background. Compress textures and audio, and remove unused assets before you build.
Devices and screens
Design for screens from 5 to 6.8 inches. Keep buttons at least 48 pixels high and away from the screen edges, where notches and gesture bars sit.
Network
Expect 3G speeds and dropped connections. If the connection drops during a round, the game should keep the player's progress and reconnect within 30 seconds. If it cannot, PlayForge treats the round as unfinished for that player.
Next steps
Prepare your icon, banner and screenshots with the Art and brand kit.
Assets you need
| Asset | Size | Format | Notes |
|---|---|---|---|
| Game icon | 512 × 512 px | PNG | No transparency. We round the corners for you. |
| Game banner | 1200 × 500 px | JPG or PNG | Shown at the top of your game page and in featured spots. |
| Screenshots | 1080 × 1920 px | JPG or PNG | Three to five, portrait. |
| Gameplay video | 15 to 30 seconds | MP4 | Optional. No sound needed. |
Icons that get the tap
- Show one clear object or character, large enough to read at thumb size.
- Keep text out of the icon, or out of the outer 10% if you must use it.
- Use a bold, solid background. Thin lines and gradients disappear on small screens.
PlayForge colours and fonts
- Green (#2BE38B) is for actions, such as buttons.
- Gold (#FFC83D) is only for rewards and prizes.
- Headings use Sora. Body text uses Inter.
Using the PlayForge name and logo
You may say your game is "Available on PlayForge" and use the badge from the kit. Do not change the logo's colours or shape, place it inside your game icon, or suggest that PlayForge made your game.
Download the kit
The kit includes icon and banner templates, the "Available on PlayForge" badge and the colour palette. Download it from the console under Resources → Brand kit.
Coins, rewards and prizes
- Coins are for free play. Players earn them from daily rewards and rewarded videos.
- Rewards are money in the player's balance, paid from a room's reward table.
- Prizes are items from sponsors, such as match tickets.
Rooms and reward tables
Every contest is a room with a fixed number of seats: 10, 100 or 1,000. Players see the entry fee and the full reward table before they join, and the table does not change once the room opens. PlayForge runs the room. Your game runs the round.
How your game reports results
When a round ends, report each player's score. PlayForge ranks every player in the room and pays rewards when the room closes.
What your game must not do
- Show or calculate reward amounts itself. PlayForge shows the room's reward table.
- Award coins outside the SDK.
- Let one player affect another player's score in a solo room.
- Change the rules of a round after it starts.
Next steps
Read Pay in and pay out to see what PlayForge handles for you.
What PlayForge handles
Pay in and pay out are built and tested. You write none of it. PlayForge handles:
- Adding money from a mobile wallet or card.
- Player balances and entry fees.
- Paying rewards when a room closes.
- Withdrawals to the player's mobile wallet.
- Refunds when a room is cancelled.
What your game does
Your game only needs to know which room the player is in and report their result. Joining a room, paying the entry fee and receiving rewards all happen in the PlayForge screens before and after your game.
What your game never handles
- Card numbers, wallet numbers or PINs.
- Player balances.
- Withdrawal requests.
Testing
In the sandbox, every test account starts with 10,000 test coins. Test coins behave exactly like real money in rooms, so you can check the full flow from joining a room to receiving a reward.
Next steps
Read Urdu and English before you design your screens.
Many PlayForge players read Urdu first. Games that offer Urdu are easier to pick up and keep players for longer.
Fonts
- Noto Nastaliq Urdu for titles and longer text.
- Noto Naskh Arabic for small text such as labels, where Nastaliq gets hard to read.
- Make Urdu text about 20% larger than English, with a line height of at least 1.8.
Right-to-left text
- Mirror menus and lists in Urdu, so they start on the right.
- Keep numbers, scores and timers left to right.
- Never add letter spacing to Urdu text. It breaks the joins between letters.
What stays in English
Your game's name, buttons and scores stay in English, so players can move between games without relearning the controls. Instructions, hints and story text can be in Urdu.
Game page in two languages
Add your game's one-line description and "how to play" steps in both English and Urdu in the console. If you skip Urdu, the English text shows for every player.
Next steps
Read the Review process.
After you submit
Your console shows the status of every build. A new game goes through these steps:
| Step | What happens | Usual time |
|---|---|---|
| 1. Submitted | Your build and game page details are received. | Instant |
| 2. Automated checks | Size, load time, crashes and SDK setup are tested. | Under 1 hour |
| 3. Review | A reviewer plays your game and checks content and rewards. | 3 to 5 working days |
| 4. Approved | You choose when the game goes live. | Your choice |
If something needs fixing, the status changes to Changes requested, with notes from the reviewer. Fix it and submit a new build; you keep your place in the queue.
Common reasons a game is sent back
- It crashes or freezes on phones with 2 GB of memory.
- A result is missing for some players in a room.
- Icon or screenshots do not match the kit sizes.
- The game page is missing how to play or the age rating.
If you disagree with a decision
Reply in the review thread in the console within 14 days and explain why. A different reviewer looks at it again.
Next steps
Read Releases and updates to plan your first update.
Shipping a new version
- Build your update with a higher version number.
- Upload it under Games → Releases → New release.
- Add short release notes: what changed for players.
- Submit it for review. Updates are usually reviewed within 1 to 2 working days.
Updating without downtime
When an update goes live, rooms already in progress finish on the old version. New rooms use the new version. Players never lose a round because of an update.
Version numbers
Use three numbers: major, minor and fix, for example 2.4.1. Each new build must have a higher number than the last.
Rolling back
If an update causes problems, go to Games → Releases, pick the previous approved build and choose Roll back. New rooms use the older version within a few minutes. No review is needed to roll back.
Next steps
Read Game centres to see where your game appears.
Where your game appears
One integration puts your game in the catalogue, and it goes live across the network:
- Telco game centres: inside mobile network apps.
- Bank and wallet apps: a games section inside the app.
- Brand game centres: in a brand's own name and colours.
How games are placed
- Every game appears in its category, such as Cricket, Board or Word and trivia.
- New games get a New spot for their first two weeks.
- Featured spots are chosen by the PlayForge team each week, based on ratings and how often players come back.
Opting out of a game centre
Each partner chooses which categories they show. If you need your game kept out of a particular game centre, for example because of an exclusive deal, contact developer support.
Next steps
Read Revenue reports to see how your game is doing.
What the console shows
| Number | What it means |
|---|---|
| Plays | Rounds started in your game, in free and paid rooms. |
| Players | Different accounts that played at least one round that day. |
| Revenue | What your game earned from rooms and sponsorships, as set out in your Developer Agreement. |
| Payout history | Every payout made to you, with its date and amount. |
When numbers update
Plays and players update every hour. Revenue is final at midnight Pakistan time each day.
Filtering and comparing
Filter by date range, game centre and room size. Compare any two periods to see the effect of an update.
Exporting reports
Download any report as a CSV file from the Export button at the top of the page.
Next steps
Read Payouts to see when and how you are paid.
Your share
Your revenue share from paid rooms and sponsorships is set in your Developer Agreement. You can see it at any time in the console under Earnings.
Payout schedule
PlayForge pays once a month for the previous month's earnings. The console shows the date of your next payout.
How you are paid
Payouts are made in Pakistani rupees by bank transfer to the account in your console. Add or change your bank details under Earnings → Payout details. Changes take effect from the next payout.
Minimum payout
If your earnings for a month are below the minimum in your Developer Agreement, they carry over to the next month.
Tax and statements
Every payout comes with a statement showing your earnings and any tax deducted as required by law. Download statements from Earnings → Statements.
Next steps
Read Advertising to add another way to earn.
Ad formats in your game
- Sponsored game: a brand's name on a game people already love.
- Sponsored prize: a brand funds a prize, and players see who it is from.
- Branded tournament: a brand's name on a league, a leaderboard and the final.
- Rewarded video: players choose to watch an ad to earn coins.
Sponsorships are arranged by PlayForge. You do not need to find advertisers yourself.
Your share
Your share of ads and sponsorships in your game is set in your Developer Agreement and appears under Earnings in the console.
Adding rewarded video
Offer a video only when the player asks for it, for example "Watch a video for 50 coins". Never play one automatically.
Brand safety
- No ads during a round. Ads only appear before or after.
- No ads for gambling, alcohol, tobacco or adult content.
- No ads in games rated for children.
Use the server API for anything your game server does: checking rooms, reporting results from the server and reading reports. Your game itself uses the SDK.
Authentication
Send your secret key in the Authorization header of every call. Use your sandbox key while testing and your live key in production. The base address for each is shown under Settings → API keys.
Calls
| Call | What it does |
|---|---|
GET /v1/games/{gameId} | Your game's details and live version. |
GET /v1/rooms/{roomId} | A room's size, players and status. |
POST /v1/rooms/{roomId}/results | Report a player's result from your server. |
GET /v1/reports/daily | Plays, players and revenue for one day. |
Example: report a result
Errors
| Code | Meaning | What to do |
|---|---|---|
| 400 | The request is missing a field or has a wrong value. | Check the message for the field name. |
| 401 | The key is missing or wrong. | Check the key and that it matches the environment. |
| 404 | The game, room or player was not found. | Check the id. |
| 409 | A result for this player is already recorded. | Do not retry. Each result is recorded once. |
| 429 | Too many requests. | Wait and retry after the time in the Retry-After header. |
Limits
Each key can make up to 60 calls a minute. Contact developer support if your game needs more.
3 November 2026
- Docs: search now filters the docs menu as you type.
- Docs: every page now lists its sections under "On this page".
20 October 2026
- Sandbox: you can now test rooms of 1,000 players.
- Console: rolling back a release no longer needs review.
6 October 2026
- Reports: export any report as a CSV file.
- Reports: compare two date ranges side by side.
15 September 2026
- Docs: new guide to Urdu fonts and right-to-left text.
Before you contact us
Most answers are in these docs. Search the docs menu, and check the Submission checklist if your game was sent back from review.
Support tickets
Open a ticket from the console under Support → New ticket. Choose the game it is about and add screenshots or logs. You can follow every reply in the console.
Response times
| Type of problem | First reply |
|---|---|
| Your live game is down, or payments are not working | Within 4 hours |
| Review, release or report questions | Within 1 working day |
| General questions | Within 2 working days |
Support hours are Monday to Friday, 10:00 to 18:00 Pakistan time. Problems with a live game are watched every day.
Developer forum
Ask questions and share what you have learned with other developers on the network. The PlayForge team answers there too.
Report a security problem
Do not post security problems in the forum. Open a ticket marked Security, and it goes straight to the security team.