Verity Payments
veritypayments.comBottom line. Verity has outgrown a customer portal it built in 2021 and has said so in public. Priya owns the rebuild and has no front-end team to give it to. Lead with the takeover you ran for Kestrel, and find out who signs before the call ends. The opening is a standing front end for two quarters rather than a redesign, and the difference is worth naming in the first ten minutes.
The company
Verity Payments moves money for marketplaces. Its customers are the operations teams who have to pay sellers, drivers and freelancers on a schedule, and the product is judged on whether those payouts land when they were promised. It sells to the marketplace rather than to the person being paid, which is why the portal those operations leads log into every day is the product and not a wrapper around it.
Ninety-one people, eleven of them in engineering, split between the ledger and the public API. There is no front-end team and no front-end lead. The company raised $28M in March 2026 and told its investors the money funds a self-serve tier, so the portal now sits on a funded roadmap with a date attached to it.
Facts
- Series B, $28M, March 2026. Ardent Partners led the round. Verity named self-serve onboarding as the first thing it funds, so there is budget for customer-facing product this year and a date it will be measured against.1
- Ninety-one people, eleven engineers. Engineering is split across the ledger and the public API. There is no front-end team and no front-end lead, so work on the portal has nowhere internal to sit.2
- Payouts for marketplaces. They are not a general payments company. Their buyers are marketplace operations leads, and the portal is the thing those leads work in all day rather than a wrapper around an API.3
- The portal dates from 2021. It went up beside the first version of the ledger and has been patched since. Verity has said in public that it has outgrown it, which is a rare thing for a company to write down.6
Why now
- March 2026Raised $28M and named self-serve onboarding as the first thing it funds, so the rebuild sits on a funded roadmap rather than a wish list.1
- July 2026Posted for a senior front-end engineer, then closed the ad after five weeks with no hire announced, so the internal route looks stalled.4
- Last weekShipped a status page after a four-hour outage and apologised for how hard it was to tell what was happening, so trust in the current interface is live.5
Who you're meeting
- Promoted from within two years ago. She ran the ledger product before this, so she will judge a partner on delivery discipline before visual craft. Show her a sequence and a date before you show her a screen.6
- Owns onboarding end to end. The self-serve tier is her number, so anything that shortens time to first payout is her problem rather than a nice extra.6
- Not the only signature. The CFO signed the last two vendor contracts, so plan for a second conversation and ask who else has to see the scope.7
Likely priorities
- Get the self-serve tier live on the date she gave the board.
- Keep her own engineers on the ledger while it happens.
- Come out of it with a front end that somebody owns.
Where you connect
- You have taken over a merchant dashboard mid-flight before, at Kestrel.
- She ships the plain version rather than miss a quarter, and so do you.
- Owns the ledger and the API. Tomas is not the buyer, but nothing ships without him. He will want to hear that his endpoints stay where they are and that his team is not pulled onto the portal.2
How they communicate
Our read, from their own words
Priya Raman, VP Product
- Plain about tradeoffs, impatient with polish. She describes decisions by what was given up, so a proposal that names its own compromises will read as honest.
“We shipped the ugly version because the alternative was shipping in April.”8
- Measures in customer time, not sprints. Her writing counts hours saved for users, so frame the timeline around when their customers feel it.
“Nobody outside the building cares which sprint it landed in.”6
Tech and hiring
- One front-end role, opened and closed. The senior front-end advert ran for five weeks in July and came down with no hire announced. Nothing has been reposted, so the internal route to a rebuild is stalled rather than under way.4
- The open roles are backend. Both roles on the careers page today sit on the ledger and on reconciliation, which says where the engineering budget goes while the portal waits.9
- The portal is its own front end. Their engineering writing describes it as a client that talks to the public API, so a partner can work behind endpoints that already exist rather than negotiating for new ones.10
Competitive set
- Harbour Payouts The name that comes up most often against them in marketplace deals. Harbour rebuilt its own seller portal last year, which is part of why Verity's looks its age to a buyer comparing the two.7
- Sableline Cheaper and thinner, aimed at smaller marketplaces. Verity wins on reconciliation and loses on time to first payout, which is the exact gap the self-serve tier is meant to close.3
- Building it in-house The largest marketplaces run their own payout rails. It is why Verity sells on operations rather than on price, and why onboarding time is the number they watch.3
Where you fit
strongOur read, not sourced
Likely pains
- No front-end capacity, and the one hire they went out for did not land.
- A 2021 portal is the first thing a marketplace ops lead sees while evaluating them.
- Self-serve revenue is committed to investors on a timeline the team cannot staff.
Verity does not need an agency to redesign a portal. It needs one to take the whole front end for two quarters while its own engineers stay on the ledger. That is the shape Halyard sells, and it is a harder thing to buy from a design studio.
The risk is that Priya has already framed this internally as a redesign and is shopping for a Figma file. Reframe it early. Ask what happens to the front end after launch and the conversation moves from a project to a standing team.
The money is already approved, which changes the sale. You are not arguing for a budget. You are arguing about who spends one that exists, against a hire they have already tried once.
Talking points
- Kestrel, same shape. You took over Kestrel's merchant dashboard while their team stayed on billing, and shipped in nine weeks. Same handover, same constraint, and a reference she can call.
- Discovery that ends in a plan. Your two-week discovery produces a build sequence and a fixed first phase, which answers a CFO before he asks.
- Their engineers keep the API. You work behind their existing endpoints, so nothing you do blocks the ledger roadmap.
Risks
- A design-only scope. Bought as a redesign, the build goes to whoever is cheapest afterwards and the standing team never happens. Fix the frame in the first call or you are bidding on a Figma file.
- The CFO you have not met. The last two vendor contracts went through finance. A scope agreed only with Priya can sit unsigned for a month with nobody ever saying no to you.
- The hire coming back. If they reopen the front-end role in the autumn the case for a partner weakens. A phased first quarter is easier to defend than a two-quarter commitment.
Ask these
- What breaks first if self-serve doubles? Tells you whether the portal is the constraint or a symptom of one.
- Who else has to agree before we start? Surfaces the CFO in week one instead of week three.
- What happened with the front-end hire? Tells you whether they are still trying to solve this internally.
- What must the portal do by Q1? Turns a redesign into a dated commitment you can scope against.
Watch out for
Objections
- “We should just hire for this.” They tried and stopped, so agree with the instinct, then price a team they can switch off rather than one they carry.
- “Agencies don’t know payments.” Raise the Kestrel ledger work before they do, and name the compliance constraints you already built inside.
Deal risks
- A decision maker you have not met. The CFO signed the last two contracts, so a scope agreed only with Priya can die quietly in finance.
- Scope framed as a redesign. A design-only brief caps this at a small project and hands the build to somebody else.
Sensitivities
- The July outage. They have apologised for it once in public. Treat the status page as evidence they take it seriously, not as a problem you are here to fix.
Sources
- ardentpartners.com/news/verity-payments-series-b
- veritypayments.com/about/team
- veritypayments.com/product/payouts
- veritypayments.com/careers/senior-frontend-engineer
- status.veritypayments.com/incidents/2026-07-14
- veritypayments.com/blog/shipping-self-serve
- techledger.example.com/2026/05/verity-payments-vendor-spend
- buildandbill.example.com/episodes/priya-raman
- veritypayments.com/careers
- veritypayments.com/blog/behind-the-api
This brief was researched and written by AI. Every claim is source-checked, but AI can make mistakes, please verify anything you act on.