Payments

Designing RummyCulture’s payments— making add cash easy for players.

Payments is the screen between deciding to play and sitting at a table. On RummyCulture it has a lot to do in a few seconds: take money from a bank, show where the GST goes, check location and KYC, and keep working when a UPI app or a bank doesn’t. This is the story of the payment page, and of every way a payment can go.

Role
Lead Product Designer
Team
Led 2 designers
Scope
0 → 1
Partner
Rahul Singla, PM
Product
RummyCulture · Gameskraft
Status
Live
The Payments screen: an empty amount field with a ₹50 minimum, and a Continue button. The payment page listing UPI apps, cards, wallets and net banking. Google Pay selected, with an Add ₹1,000 button opened right under it. A saved Axis card as the preferred payment, asking only for the CVV. Add Cash successful, with the GST breakdown and a free tournament ticket.

Before the first game

One small step between players and the table.

On RummyCulture you can practise for free. But to sit at a cash table or join a tournament, you need money in your account, so whatever you opened the app to play, the first real step is the same: Payments.

You type ₹1,000 and hit Continue. Now there’s a page full of ways to pay, a game waiting on the other side, and one question you don’t say out loud.

“What if the money leaves my account and never shows up?”

Every player who reaches this page carries that question. Everything below is an answer to it.

See it in motion

₹1,000 with Google Pay, start to finish

A first-time player on the simplest path through the page. Four taps, from typing an amount to money in the account.

My role

Leading the design, and the room around it

I led a team of two designers on Payments. Beyond the screens, my job was to keep everyone pointed at the same thing: a player adding cash with whichever method they trust, and feeling their money is safe the whole way through.

What I owned

Scope and numbers

Worked through the scope and success numbers with product: which methods and states to cover, and what would tell us it was working.

One plan across teams

Kept the PM, engineers and leadership aligned on how the design would be executed, from the first flows to what shipped.

Safe, every step

Responsible for how adding cash feels end to end, across UPI, cards, wallets and net banking, so the money never feels at risk.

A team of two

Led two designers through the work, alongside Rahul Singla as PM.

01 · The context

The most nervous screen in a fun app

Everything else in RummyCulture is built for play: tables, tournaments, leaderboards, offers. Payments is the one place where real money leaves a player’s bank. For a lot of people, it’s the first time they’ve paid a game anything at all.

It also carries rules most players never think about. Every deposit is taxed at 28% GST, so adding ₹1,000 puts ₹781.25 in Deposit Balance and gives ₹218.75 back as Discount Credits. Some states don’t allow real-money play at all. The app checks location to keep accounts safe, and sometimes asks for KYC. Saved cards follow RBI rules. And payment apps, like any system, have bad hours.

There was no old page to fix. We designed Payments from scratch, as a 0 → 1 product, and it was the main lever for both acquisition and retention.

What the page had to hold

Four ways to pay, at a glance

UPI apps, cards, wallets and net banking, plus a UPI ID for anyone whose app isn’t listed.

GST that adds up

What you paid, what went to tax, and what you can play with, in one place.

Checks before money

Location and KYC, asked for when they’re needed, with one line on why.

Cards, saved the RBI way

A card is saved only when the player agrees, with a line that says why it’s safe.

Methods that fail

When a UPI app or a bank is struggling, players should know before they tap.

The second visit

A returning player shouldn’t have to choose all over again.

02 · Listening first

Before drawing anything, we listened

With no old page to compare against, the “before” in this story is what players were telling us. So we didn’t start with screens. We started with the people who hear the complaints first, and then with players themselves.

How we listened

Customer care first

We sat with our customer care team and wrote down every moment where the experience let players down.

Sorted into buckets

Lobby, tournaments, clubs, rewards, offers, KYC, add cash, withdrawal. From each, we kept the top pain points.

Calls with players

Then we got on calls with players, to hear the same problems in their own words.

What players told us

Finding the way

“Where can I enter the amount? What payment options are there?”

Trust

“I am not sure if my saved method will be safe. I hope RummyCulture doesn’t share my payment information with others.”

Saved cards

“How can I view my saved cards? On what basis is my saved card pre-selected?”

UPI

“How can I identify which UPI ID I have used? What happens if I don’t have PhonePe or GPay?”

Cards

“Where do I enter the CVV? What if I have an Amex or a Diners Club card, how will I pay?”

When it breaks

“How will I know if the payment gateway or bank server is down? What if my only saved method has a high failure rate?”

Underneath, almost every question was one of three: where do I start, is my money safe, and what happens if it fails? The rest of this page is an attempt to answer them.

Who we were designing for

  • 48%LVPs, low value players, paying ₹0–₹199 a day in commission
  • 30%MVPs, medium value players, paying ₹200–₹499 a day
  • 22%HVPs, high value players, paying ₹500 or more a day

Our 22% HVPs drove almost 80% of the commission. But growth sat in the other 78%: a new player becomes an LVP, and over time LVPs grow into MVPs and HVPs. Many of them play on lower-resolution phones, so the page had to hold up on smaller screens too, not just on high-end ones.

03 · What we promised

Four promises to the person holding the phone

  1. 01

    Don’t make them hunt.

    The method they’re most likely to use sits at the top. Picking it opens the button right there, without a second screen.

  2. 02

    Say the amount, every time.

    Buttons read Add ₹1,000, Proceed to Add ₹1,000, Add Remaining ₹20. Money never moves behind a word like Pay or Submit.

  3. 03

    After a failure, talk about their money first.

    Before asking anyone to retry, tell them what happens to anything that was deducted.

  4. 04

    Warn, then steer.

    If a method is failing, say so before they tap it, and put one that’s working above it.

A payment page is judged on its worst minute.So a lot of this one is about that minute.

04 · The page

One list, read top to bottom

Every flow starts from the same list. We grouped the methods by where the money lives and gave each group one clear action: tap an app, add a card, link a wallet, or choose a bank. Nothing on the page asks the player to read more than a line.

✏️ The bones of it

Without colour or logos, the page comes down to a few boxes in a fixed order: the amount, the methods grouped by where the money lives, and one button under the chosen method.

Wireframe sketch: an amount field showing ₹1,000, a Continue button and a number pad.
How much? One field, one button.
Wireframe sketch of the payment list: UPI apps, Cards, Wallet with Link, and Net banking.
Grouped by where the money lives.
Wireframe sketch: the first UPI app ticked, with an Add ₹1,000 button opened under it.
Pick one, and its button opens.
Wireframe sketch: a bottom sheet over the dimmed list asking to allow location access, with one button.
One line on why, one button.

Amount on top

Add ₹1,000 stays pinned at the top. View details opens the GST split.

UPI first

One tap, one PIN. The three apps people use most are right on the page.

One clear action per method

Each payment type has a single next step: tap a UPI app, add a card, link a wallet, or choose a bank.

The payment page: Add ₹1,000 with View details at the top, then UPI apps, Debit/Credit Cards, Wallets with Link, and Net Banking.

Trust, up front

Safe & secure payments sits where the eye lands first.

Link once, not every time

Wallets link on their own screen with an OTP, then stay linked.

The long tail, one tap away

View All and All Banks hold every other app and bank.

💰 It starts with an amount

Payments opens with one question: how much? The field takes anything from ₹50, and Continue stays dimmed until there’s an amount in it. Type ₹1,000 and it lights up at the bottom, under the player’s thumb, one tap from the payment page. And if they want to check the maths first, View details at the top opens the full split: ₹218.75 to GST, the same back as Discount Credits, and a Buy-In Value of 1,000.

The Payments screen with an empty amount field and Continue dimmed.
Choose an amount
₹1,000 entered in the amount field and Continue switched on.
₹1,000 entered, Continue on
The payment page listing UPI apps, cards, wallets and net banking.
Then, how to pay
The View details sheet: ₹1,000, GST at 28% of ₹218.75, Discount Credits of ₹218.75 and a Buy-In Value of 1,000.
View details: where the money goes

05 · Every way a payment can go

Ten journeys, one page

Here’s each path through the page, from the first permission to the receipt. These are the real flows, including the screens a player only sees on a bad day.

📍 Before any money moves

A new player’s first step isn’t a payment, it’s a permission. The sheet says exactly why the app wants their location: “to detect any suspicious activity and keep your account safe.” Then Android asks in its own words. If they say no, the next sheet doesn’t plead. It says what’s needed and opens Settings.

Where real-money play isn’t allowed, the page says so plainly and offers practice games instead of a dead end. KYC follows the same pattern: one sentence on why, one button.

A bottom sheet asking for location permission, with the reason and a Proceed to Allow button.
Why we ask
Android's own prompt: Allow RummyCulture to access this device's location, with Allow only while using the app, Only this time and Deny.
Android asks
Location permission denied, with a Go to Settings button.
If they say no
Add cash is unavailable at your location, with a Play Practice Games button.
Not allowed here
A bottom sheet asking the player to complete KYC by uploading documents.
KYC, when it’s needed

📱 First time, paying with UPI

Pick an app and the button opens right under it: Add ₹1,000. There’s no review screen in between, because the amount is already on the button. If their app isn’t one of the three on the page, View All has the rest.

The payment page for a first-time player.
The list
All UPI Apps: Google Pay, PhonePe UPI, Amazon Pay, Paytm UPI, BHIM and iMobile Pay.
All UPI apps
Google Pay selected, with an Add ₹1,000 button under it.
Tap, and the button opens
Google Pay still selected, with a loader spinning inside the orange button while the UPI app opens.
Over to the UPI app
A full green Success screen.
Done

🆔 Paying with a UPI ID

Some players use an app we can’t open, or would rather type. They can enter a UPI ID, choose to save it for next time, and pay. The button still carries the amount.

The payment page with an Add UPI ID option under UPI.
+ Add UPI ID
Add a new UPI ID, empty, with the keyboard open.
Keyboard up
A UPI ID typed in, with Securely save UPI ID checked.
Typed and saved
The UPI ID entered and ready to pay.
Ready to pay

💳 Adding a card

The keyboard opens on its own, and the card network shows up as soon as the number gives it away. Saving the card is the player’s choice, with one line on why it’s safe: “Secure this card as per RBI guidelines.”

Cards we can’t take, like Amex and Diners, are named in the error, so nobody keeps retyping a number that was never going to work. Next time, the card waits at the top, and only the CVV is asked again.

Add a new card, empty, with the numeric keypad open.
Empty, keyboard up
A card number, expiry and CVV filled in, with the Mastercard logo detected.
Network detected
An error under the card number: Amex and Diners club cards are not supported.
A card we can’t take
The Proceed button showing a loading spinner.
Processing
The saved Axis card as preferred payment, asking only for the CVV.
Next time, just the CVV

👛 Linking a wallet

Wallets link once, with an OTP. Before the code goes out, the sheet shows which number it will go to, so nobody waits on a phone they don’t have. Resend unlocks after 15 seconds, and too many tries get a clear message instead of a silent failure.

Once linked, the balance sits next to the wallet. If it’s short, the page says so, “Low balance. Add ₹20 in your wallet”, and the button does the maths: Add Remaining ₹20.

A sheet confirming which phone number the Paytm wallet will be linked to.
Which number
Enter the OTP sent to the phone number, with Verify and Link Wallet.
Enter the OTP
An error under the OTP field: maximum limit exhausted.
Too many tries
The PhonePe Wallet as preferred payment, with the payment from its ₹1,140 balance in progress.
Paying from the wallet
The PhonePe Wallet with ₹980 and a low balance note, with an Add Remaining ₹20 button.
Short by ₹20

🏦 Net banking

Net banking is the longest route, and for some players the one they trust most. The big banks sit right on the page. Everyone else is in All Banks, with a search box on top, so a smaller bank is a couple of letters away.

The payment page scrolled to show SBI, ICICI and Kotak under Net Banking.
Big banks on the page
All Banks: a searchable list of banks.
All Banks
Searching the bank list with the keyboard open.
Search
A full green Success screen.
Done

🔁 Coming back

The second visit should be faster than the first. Whatever they paid with last moves up to Preferred payment, open and ready, showing a wallet balance or the last four digits of a card. Everything else is still below, for the days they want something different.

A returning player's page with Paytm Wallet as preferred payment.
The second visit
PhonePe Wallet preferred, with an Add ₹1,000 button, above the Paytm Wallet and a saved card.
Wallet, ready to go
Google Pay as preferred payment, with Add ₹1,000 ready.
Google Pay, last used
Two saved cards under Preferred payment, Axis and HDFC.
Two cards saved

🚦 When a method is having a bad day

Payment apps and banks have bad hours, and a player shouldn’t find out by waiting on one. When a method’s success rate drops, it says so under its name, in plain words: “Experiencing low success rate” or “Observing high failure rate.”

If the whole of UPI is struggling, the section moves to the bottom and dims, with one line on top: “UPI is facing issues. We recommend you to use another payment mode.” Cards get a nudge at the same moment, Flat ₹25 FreeCash on add cash using cards, so the way forward is also the better deal.

PhonePe UPI dimmed with Experiencing low success rate under it, and a Flat ₹25 FreeCash nudge on cards.
One app struggling
PhonePe UPI flagged with Observing high failure rate even inside Preferred payment.
Flagged, even when preferred
A banner under UPI: UPI is facing issues. We recommend you to use another payment mode.
All of UPI struggling
The UPI section moved to the bottom of the page and dimmed.
UPI moved down and dimmed

Three ways to handle a failing method

❌ Hide it

Someone who always pays with PhonePe finds it gone. It feels like a bug.

❌ Let them find out

They tap, wait for the app and then fail, with the clock still running.

✅ Say it, dim it, move it

They see the problem before they tap, with a working option right above.

😟 When it doesn’t go through

Some payments fail anyway. The sheet that follows starts with what matters most to the player, their money: anything that was deducted comes back within 5–7 bank working days. Then a transaction ID they can quote to support, and two ways forward: retry with the same app, or try another method.

An Add Cash failed sheet with the transaction ID, amount, a note on refunds in 5–7 bank working days, and Retry Add Cash.
Their money, first
A failure sheet offering Retry with Google Pay or Try Another Method.
Retry, or switch
A Something went wrong state.
Something went wrong

🎁 An offer, at the right moment

The offer isn’t for everyone. It’s for the moments when a player might walk away. New players get it on each of their first three deposits: add ₹1,000, get 1,200 in the wallet. Returning players get it once a month, after an add cash fails, so a bad moment ends with a reason to try again. Players who left the payment page without paying see a smaller one when they’re back on Add Cash: add ₹100, get 110. Everyone else sees the page as it is. One offer, three jobs: an easier way in, fewer players lost to a failure, and a nudge back for anyone who hesitated.

New player

First three deposits

The payment page with a banner at the top: Add ₹1,000 to get 1,200 in your wallet.
The offer, right at the top

Returning player

After a failed add cash, once a month

The Add Cash failed sheet with the transaction ID, amount and Retry Add Cash.
It didn’t go through
Back on the payment page, with the Add ₹1,000 to get 1,200 banner at the top.
Back on the page, with the offer

Dropped off

Left the payment page without paying

The Add Cash screen with a banner under the amount field: Add ₹100 to get 110 in your wallet.
Back on Add Cash, with an offer
₹100 typed into the amount field, with the Add ₹100 to get 110 banner and Continue enabled.
₹100 in, 110 to play with

Everyone else

No offer

The payment page for a returning player, Google Pay preferred, with no offer banner.
The page, as it is

🎉 When it does

Success gets a full green screen for a second, because a payment that worked deserves a moment. Then the receipt answers the GST question in one table: ₹1,000 added, ₹218.75 paid to the government, ₹781.25 into Deposit Balance and ₹218.75 back as Discount Credits. The Buy-In Value is 1,000, the same number the player paid.

A full green Success screen.
A moment
Add Cash successful with the GST breakdown, the GST policy video and a referral offer.
The receipt
Full transaction details with date, payment mode, transaction ID and Download invoice.
Full details

06 · What happened next

The numbers

The numbers that mattered here were the quiet ones: did the money go through, did players make it to the table, and when a payment failed, did they trust it enough to try again? With the improvements that followed, this is where it landed.

  • 92%+payment success rate, across every method
  • 60%+of players on the payment page went on to add cash
  • 70%+converted when an offer was on
  • 50%+tried again after a failed payment
  • 1×add cash per daily active player. With 28% GST on every deposit, players top up once to save on it, and we encouraged that.

07 · Reflection

What this project taught me

  • The quiet screens carry the most weight.

    Most of this work is screens a player hopes never to see: an OTP limit, a struggling bank, money stuck in between. Those screens decide whether someone trusts the app with their money again.

  • One number, all the way through.

    The amount a player types should follow them everywhere: into the button, the sheet and the receipt. When ₹1,000 means ₹1,000 at every step, there’s nothing left to double-check.

  • Their money first, then the ask.

    When something fails, say what’s happening to the money before asking them to try again. Reassurance is what earns the retry.

  • Be honest before it breaks.

    Telling a player that UPI is struggling, and showing another way to pay, is kinder than letting them find out halfway through a payment.

  • Save the offer for the moments that matter.

    An offer shown to everyone is just noise. Kept for a first deposit or a bad moment, it gives a hesitant player a reason to stay.