Insights Contact

Product and Program Management

Where Should a Payments Product Manager Start? A Live Product or a Brand-New One

By SP Sankar

Every new payments product manager asks the same question in week one: where do I start? I asked it too. The answer depends on one thing. Is the product already live, or brand new?

If the product is live, fix what hurts, tidy the backlog, plan, then check it worked. If it is new, know why, know who it is for, build the right team, and launch small and safe.

Part 1: The product is already live

Week one: purpose and people

  • Learn why the product exists and how its success is measured.
  • Meet the team, and the people in operations, support, compliance and finance. They know where it hurts.
  • Find out who decides what.
Existing product: fix, tidy, plan, learnFirst learn the purpose and meet the team1Live problems firstFix what hurts money, rules and customers.Find the problems that keep coming back.2Make the backlog honestGather input from sales, support, compliance.Close duplicates; label must do, fix, feature.3Set prioritiesDeadlines, then risk and customer harm,then value against effort, plus clean-up.4Listen and measureCustomer feedback and performance numbers.Turn the biggest gaps into backlog items.Every sprintDecisions come from customers and data, not guesses.P‌M

1. Fix live problems first

Failed, stuck or double payments, broken checks, and numbers that don’t match come first: fix them now. Problems with a workaround get a plan. Small annoyances go on the to-do list. Look for problems that keep coming back, because fixing those pays off most.

2. Make the backlog honest

The backlog (the team’s to-do list) is often full of old ideas and duplicates. Collect requests from sales, support and compliance in one place, delete what is no longer needed, and label the rest: must do, fix or new feature.

3. Set priorities

  1. Deadlines first: rules from regulators and card networks, expiring certificates, security fixes.
  2. Then risk and customer harm: the biggest problems from step 1.
  3. Then value against effort: new features that move one important number. Check what competitors offer too.
  4. A little clean-up every sprint, so old code doesn’t pile up.

A simple way to split each sprint (a two-week work cycle):

Type of workShare of the sprint
Work with a deadlineWhatever the date needs (plan it first)
Live problemsAbout 20%
Clean-up and securityAbout 10 to 15%
New featuresThe rest

4. Listen and measure

After each release, check whether it helped. Two things tell you:

  • Customers: support tickets, complaints, short interviews, and where people give up in the app.
  • Numbers: pick three to five, such as payment success rate, time for the money to arrive, returned payments, fraud losses and cost per payment.

Look at them every week. Turn the biggest gap into new backlog items, and tell customers when their problem is fixed. Then the loop starts again.

Part 2: The product is brand new

There are no live problems and no data yet. So the question becomes: what must be true before the first dollar moves?

AreaLive productNew product
Start withProblems hurting customers todayThe purpose and the customer
Decide withData from productionCustomer interviews and a small pilot
The teamA team you get to knowA team you build
Biggest riskBreaking what worksBuilding the wrong thing
New product: what must be true firstBefore the first dollar movesWHY AND WHO1Find the purposeWhy this, why now, and what success means.2Start with the problem and the marketCustomers, competitors, one number for success.3Build the right teamPayments skills, clear owners, one sponsor.BEFORE BUILDING4Draw the money flow with complianceWho holds the money, which rail, which rules.5Choose partners earlySponsor bank, processor, certification.DESIGN AND BUILD6Plan the unhappy pathsReturns, duplicates, timeouts, disputes.7Build the first backlogGates, controls, core flow, operations tools.GO LIVE8Get go-to-market readySales, marketing, support ready; claims approved.9Launch small and safeOne customer type, one rail, low limits.10Live: listen, measure, improveCustomer feedback, numbers, existing playbook.P‌M

1. Find the purpose

Why should the company build this, and why now? Write it in one sentence, for example: “Help small clinics get paid the same day.” Agree what success looks like, and find a senior sponsor who makes the final call.

2. Start with the problem and the market

Talk to 10 to 15 target customers. Learn how they pay today, who else offers this, why they would switch, and what they would pay. Then write one sentence on why a customer would choose you. If you can’t, keep researching.

3. Build the right team

Start with five to eight people: a product manager, an engineering lead, someone with deep payments experience, quality engineering and a designer, plus partners from compliance, operations and finance. Agree early who decides what.

4. Draw the money flow with compliance

Who holds the money, which rail (ACH, wire, card or instant), and which rules apply? Bring compliance and risk in now, not the week before launch.

5. Choose partners early

Most new payment products need a sponsor bank (a licensed bank that gives you access to the payment networks) and a processor. Their onboarding and tests often take longer than building the product, so start them first.

6. Plan the unhappy paths

Decide what happens when a payment is returned, sent twice, times out or is disputed, and how your records will match the bank’s. In payments, this is half the product.

7. Build the first backlog

In this order: approvals and contracts, then checks (identity, sanctions and fraud), then one complete payment from start to finish, then tools for the support team. Everything else waits.

8. Get go-to-market ready

Sales, marketing and support must know who the product is for and what it does. In payments, compliance approves every promise: words like “instant”, “free” or “FDIC-insured” must be exactly true.

9. Launch small and safe

One customer type, one rail, low limits and a few friendly pilot customers. Keep a switch that stops new payments fast if something goes wrong. Talk to pilot customers every week, and grow only when the numbers look healthy.

10. Listen, measure, improve

Once real payments flow, the new product is a live product. From here, follow Part 1.

The short version

Live product: fix, tidy, plan, then listen and measure. Repeat every sprint.

New product: why, who it is for and which team; then money flow, partners and what can go wrong; then a small, safe launch.

Where did you start, on a live payments product or a brand-new one?

Working on a payments project?

I help banks and fintechs deliver real-time payments, ISO 20022, and AI-driven AML and compliance change, from strategy to go-live.

Connect on LinkedInSee how I can help