Most booking platforms evaluate payment partners the same way: compare rates, check API documentation, confirm PCI compliance, sign the contract. Three months later, the integration is live but merchants are churning, support tickets are piling up, and the "partnership" feels more like vendor management.
The problem isn't the checklist—it's what's missing from it.
Every payment partner you're evaluating can process cards. They all have APIs. They'll all promise seamless integration. This is the baseline, not the differentiator.
When software platforms focus their evaluation entirely on technical specifications, they end up surprised by operational friction that shows up months after launch. The gateway works fine. The webhook documentation was accurate. But somehow, merchants are still frustrated, and your support team is fielding questions they shouldn't have to answer.
Technical due diligence matters, but it's the easiest part of the evaluation to get right. The harder questions—the ones that actually predict partnership success—rarely make it onto the spreadsheet.
This is where most evaluations fall apart. Platforms ask about support hours and response times, get satisfactory answers, and move on. But "24/7 support" and "average response time under 2 hours" tells you nothing about what actually happens when a kayak rental operator in June has a funding hold during their busiest weekend of the year.
The questions that matter:
Who does the merchant call? Is it a general support line that handles thousands of unrelated businesses, or someone who understands experience-based operations? Does that person have authority to actually resolve issues, or are they triaging tickets into a queue?
What's the escalation path? When a merchant's deposits don't arrive before a holiday weekend, who can fix it? How many layers exist between the problem and someone with decision-making power?
How does your platform get visibility? When a merchant contacts payment support, do you know about it? Can you see the ticket history? Or do you find out three weeks later when the merchant cancels their subscription with you?
Most platforms don't discover the answers to these questions until something goes wrong. By then, the merchant has already decided your platform is the problem—even if the issue is entirely on the payment side.
Payment partners love talking about their fast onboarding. "Merchants can be live in 24 hours." That speed is appealing, especially when you're trying to reduce friction in your own signup flow.
But fast onboarding often means minimal underwriting, which means more holds, more reserve requirements, and more merchants who get approved and then can't actually process when it counts.
For experience businesses—especially those selling high-ticket adventures or operating seasonally—underwriting shortcuts create downstream chaos. A zipline operator gets approved instantly, processes $40,000 in deposits for summer bookings, then gets flagged for review because the volume pattern looks unusual. Funds get held. The operator blames your platform. You lose a customer over something you never controlled.
The evaluation question isn't "how fast can merchants get approved?" It's "what does the onboarding process look like for the specific merchant types we serve, and what percentage of approved merchants hit funding issues in their first 90 days?"
If your prospective payment partner can't answer that second question with real data, they either don't track it or don't want to share it. Neither is a good sign.
Revenue sharing sounds straightforward: you refer merchants, you earn a percentage of processing volume. Everyone wins.
But the structure of that revenue share shapes behavior in ways that aren't obvious during contract negotiations.
Front-loaded vs. lifetime value models. Some partnerships pay higher residuals upfront that decrease over time. Others pay consistent rates for the life of the merchant relationship. The first model incentivizes volume acquisition. The second incentivizes merchant retention. Which one aligns with how your platform actually grows?
Who owns the merchant relationship? If a merchant leaves your platform but keeps using the payment provider, do you still earn on that volume? This isn't just about revenue—it's about whether your payment partner has an incentive to help you retain merchants or an incentive to build their own direct relationship.
What happens when merchants have problems? If merchant churn affects your residuals immediately but the payment partner's retention team only kicks in after 60 days of inactivity, you're absorbing risk that should be shared.
The evaluation checklist should include: "Walk me through a scenario where a merchant is unhappy. Who reaches out first? Who owns the save attempt? How does that affect the economics?"
When a merchant processes a payment through your platform, what do they see? What does the guest see on their credit card statement? What branding appears on receipts, refund notifications, and dispute communications?
These details feel minor during partner evaluation. They're not.
If dispute emails come from your payment partner's brand and reference a company name your merchant doesn't recognize, confusion becomes your support problem. If the statement descriptor doesn't match your platform or the operator's business name, chargebacks increase because guests don't remember the charge.
The bigger question: does the payment experience reinforce your platform's value, or does it introduce another brand into the relationship?
Some platforms prefer invisible payments—the processing happens, funds appear, and the merchant never thinks about who's behind it. Others want payment features to be a visible benefit of their platform. Either approach works, but you need a payment partner whose model matches your positioning.
Before signing a payment partnership, every booking platform should be able to answer:
If your evaluation process doesn't surface clear answers to these questions, you're not evaluating a partnership. You're comparing vendors—and you'll end up with a vendor relationship even if the contract calls it something else.
Payments Made Simple. Experiences Made Unforgettable.
ActivityPay is a vertically focused payments and commerce partner built for the activity and experiences economy.
Reno, Nevada
View full profile