The buyer depends on how much of the money flow the platform owns. At an early marketplace, the founder or CTO picks the first provider. Once payments earn revenue, a head of payments owns the choice, the CFO signs, and risk or legal approves the liability. Most deals need all four.
Why do platforms treat payments as a revenue line?
Payments volume can grow faster than the platform itself. In the quarter to 30 June 2026, 68% of Shopify's gross merchandise volume ran through Shopify Payments, or $78.1 billion. A year earlier: 64% and $56.6 billion (Shopify 10-Q, August 2026, company reports).
Volume through Shopify Payments grew 38%, while total volume grew about 32% ($115.6 billion against $87.8 billion). Shopify Payments revenue rose $624 million year on year in that quarter.
These figures decide who comes to your meeting. When payments are a cost, the CTO judges you on integration effort. When payments are a product, its owner judges you on take rate, conversion and payout speed, and the CFO checks the forecast. Ask early which case your prospect is.
Who owns the decision at each stage?
Titles vary by company, so confirm each owner before you write. The usual pattern has four stages:
- First integration, payments as a cost. The founder or CTO picks the vendor, and a lead engineer checks the integration. They measure time to go live and fees.
- Payments as a product line. A head of payments or VP product picks, and the CFO approves. They measure take rate, authorisation rate and payout speed.
- Several providers or countries. The head of payments picks with a payments operations lead. The CFO, head of risk and legal approve. They measure cost per transaction by country, provider redundancy and loss rates.
- The platform holds or moves client funds. The head of payments or embedded finance picks. The CFO, compliance officer and legal approve. They measure the liability split, licence scope and reconciliation.
Stages 2 and 3 hold most of the budget. At those stages, someone's bonus depends on payments revenue, and that person will take a meeting about it.
Who carries the liability, and why does that add a buyer?
Liability decides whether risk and legal join the deal. On Stripe Connect, the account type sets the platform's liability for fraud, abuse, negative balances and identity checks (Stripe, October 2026). In the fully white-labelled setup, the platform handles onboarding, identity data and support for every connected seller.
Each item has an owner inside the platform:
- Fraud and dispute losses: the head of risk or trust and safety.
- Negative seller balances: finance, usually the controller.
- Identity checks on sellers: compliance and the onboarding product team.
- Seller support for payment issues: customer operations.
A vendor that moves any of these onto or off the platform changes the platform's cost base. Lead with the item that matters to the person in the room. If your product moves liability, bring the risk lead in early, so their questions shape the proposal before it reaches the CFO.
How do you find the right person?
Search for the role that owns payments revenue. Useful titles are head of payments, director of payments product, head of fintech, VP monetisation, head of embedded finance and payments operations lead.
Contact databases mislabel these people. In our records, a co-founder title for one company sat on a contact record for a different company (our data, October 2026). We now drop any record whose title names another firm.
At a marketplace, the same mistake sends a pitch to a seller on the platform. Match the email domain to the company domain before you send. This matching step is one part of GTM engineering.
What does each person need to hear?
Write one message per role. Send them a few days apart, each with a different reason to reply:
- CFO: a payments revenue estimate in their own numbers. Multiply the volume on the platform by the share it processes, then by the net margin per transaction.
- Head of payments: authorisation rate and payout speed, with one comparable platform that improved both.
- Payments engineering lead: the migration effort. Say what moves, what stays, and whether stored card tokens can move.
- Head of risk: the liability split before and after your product, line by line.
For a listed platform, use public filings for the estimate. For a private one, use its own published volume. If you cannot source a figure, leave it out.
How long does a platform deal take?
Most of the time goes on migration planning and the liability review. These start only when the head of payments agrees to sponsor the project. Expect engineering and risk at the second meeting.
For the cost of booking those meetings, see how much you should pay per qualified meeting.
Who gets your first message?
- No payments leader: write to the founder or CTO about integration time and fees.
- A head of payments: write about take rate and authorisation, and use the CFO's numbers in your estimate.
- Your product moves liability: add the head of risk to the first meeting.
- The platform holds client funds: add compliance before you send a proposal.
- Every record: check the title against the company domain before the send.
To see the payments owners at platforms that fit now, start with five named buyers, free, each with a dated reason.