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 or embedded finance leader owns the choice, the CFO signs, and risk or legal approves the liability that comes with the setup. Most deals need all four.
Why do platforms treat payments as a revenue line?
Because payments volume can grow faster than the platform itself. Shopify reports that 68% of its gross merchandise volume ran through Shopify Payments in the quarter to 30 June 2026, or $78.1 billion, up from 64% and $56.6 billion a year earlier (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), and Shopify Payments revenue rose $624 million year on year in that quarter.
Those figures explain who shows up to your meeting. When payments are a cost, the CTO evaluates you on integration effort. When payments are a product, the person who owns that product line evaluates you on take rate, conversion and payout speed, and the CFO checks the forecast. Ask early which of the two your prospect is.
Who owns the decision at each stage?
The table below maps the usual owners. Titles vary by company, so confirm each one before you write.
| Platform stage | Picks the vendor | Evaluates the integration | Approves | What they measure |
|---|---|---|---|---|
| First integration, payments as a cost | Founder or CTO | Lead engineer | Founder | Time to go live, fees |
| Payments as a product line | Head of payments or VP product | Payments engineering lead | CFO | Take rate, authorisation rate, payout speed |
| Several providers or countries | Head of payments with a payments operations lead | Platform architecture team | CFO, head of risk, legal | Cost per transaction by country, provider redundancy, loss rates |
| Platform holds or moves client funds | Head of payments or embedded finance | Engineering and compliance | CFO, compliance officer, legal | Liability split, licence scope, reconciliation |
The middle rows hold most of the budget. A platform at that stage has someone whose 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. Stripe's Connect documentation states that the platform's choice of account type determines its liability for fraud, abuse, negative balances and identity verification (Stripe, October 2026). In its fully white-labelled setup, the platform handles onboarding, identity data and support for every connected seller.
Each item on that list 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, plus the onboarding product team.
- Seller support for payment issues. Customer operations.
A vendor that shifts any of these onto the platform, or takes them off, changes the platform's cost base. Lead with the item that matters to the person in the room. Bring the risk lead in early when your product moves liability, 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, then check that the record belongs to the company. Useful titles include 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 we found a co-founder title for one company sitting 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 instead of the platform itself, so match the email domain to the company domain before you send.
This matching step is one part of the system described in what GTM engineering is.
What does each person need to hear?
Write one message per role and send them a few days apart, each with a different reason to reply:
- CFO. A payments revenue estimate in their own numbers: volume on platform, times the share processed through the platform, times the net margin per transaction.
- Head of payments. Authorisation rate and payout speed, with one comparable platform that improved both.
- Payments engineering lead. Migration effort: what moves, what stays, and whether stored card tokens can move with it.
- Head of risk. The liability split before and after your product, line by line.
Use public filings for the estimate when the platform is listed, and the platform's own published volume when it is private. Leave a figure out when you cannot source it.
How long does a platform deal take?
Most of the time goes on migration planning and the liability review, and those start only once the head of payments has agreed to sponsor the project. Expect the first meeting to be with the sponsor and the second to include engineering and risk.
For the cost of booking those meetings, see how much you should pay per qualified meeting.
A decision rule for your first outreach
- If the platform has no payments leader, write to the founder or CTO about integration time and fees.
- If it has a head of payments, write to them about take rate and authorisation, and copy the CFO's numbers in your estimate.
- If your product moves liability, add the head of risk to the first meeting.
- If the platform holds client funds, add compliance before you send a proposal.
- Check every record's title against the company domain before the send.
To map the payments owners at your target platforms by stage and liability, start with The Diagnostic at $2,500.