Most embedded payments provider evaluations start with pricing and end with regret. The pricing looked competitive, the demo was polished, and six months into the integration you discover that the migration path doesn't exist, the API documentation is incomplete, and your merchants are calling you about deposit delays that you can't resolve because the processor's support team takes 48 hours to respond.

The problem isn't that platforms choose bad providers. The problem is that most evaluations focus on the wrong things. Rate sheets and feature lists are table stakes. The questions that actually determine whether a payments partnership works are harder to ask and harder to compare — but they're the ones that matter 18 months in.

Here are the eight questions we use when evaluating embedded payments providers for our advisory clients.

1. What Is the Full Cost Stack — Not Just the Headline Rate?

Every provider will quote you a rate. Interchange-plus pricing, flat rate, or a blended rate — the headline number is designed to be comparable. It's also designed to be incomplete.

The full cost stack includes interchange (non-negotiable, set by card networks), the processor markup above interchange, per-transaction fees, monthly platform fees, PCI compliance fees, chargeback fees, batch settlement fees, and sometimes gateway fees on top of processing fees. Some providers bundle these. Others itemize them. The ones who bundle are usually hiding the most margin.

Ask for a complete cost breakdown on a sample month of transactions — not a rate card. Provide your actual merchant mix (average ticket size, card-present vs. card-not-present, debit vs. credit split) and ask them to model the effective cost. If they won't do this, they know the answer isn't favorable.

2. Who Owns the Merchant Relationship?

This is the single most consequential question in any payments partnership, and most platforms don't ask it directly enough.

In some arrangements, the processor owns the merchant relationship. They can contact your merchants directly, market to them, and — in some cases — migrate them to another platform's integration. In others, you own the merchant relationship and the processor is an infrastructure provider behind the scenes.

The answer determines your competitive exposure. If the processor can see your merchant data, understand your vertical, and reach your merchants directly, you've handed them a map to compete with you or to sell that intelligence to someone who will. Ask specifically: can the processor market directly to merchants boarded through your integration? What data do they retain? What happens to the merchant relationship if you terminate the agreement?

3. What Does the Migration Path Look Like?

Your payments strategy will evolve. You might start in ISV Referral and move to PayFac Lite. You might outgrow a managed PayFac provider and want to register directly. You might simply want to switch processors because the economics no longer work.

Before you sign, understand what migration looks like. Some providers make it straightforward — they'll export your merchant portfolio, provide a transition timeline, and cooperate with the receiving processor. Others make it deliberately painful. Merchant data is locked, re-boarding is required from scratch, and the contractual exit terms include volume commitments or early termination fees that make switching economically irrational.

Ask for the specific migration process in writing. If the answer is vague or the contract includes a long exclusivity period with steep exit penalties, factor that into your evaluation — because you're not just choosing a provider, you're choosing how hard it will be to leave.

4. What Is the Merchant Onboarding Experience?

The boarding experience is the first thing your merchants see of your payments program. If it's clunky, slow, or requires information they don't understand, you'll lose merchants before they process a single transaction.

Evaluate the provider's boarding flow from the merchant's perspective. How many fields? How long does approval take? Is there a sandbox you can test? Does it support progressive boarding — where merchants can start processing before full KYC is complete? Can you customize the flow, or are you locked into their standard form?

The providers with the best boarding experiences have invested in pre-fill, real-time verification, and instant approval for low-risk merchants. The ones with the worst experiences are the ones that built compliance-first and never came back to fix the UX.

5. What Happens When Something Goes Wrong?

Payments problems are urgent. When a merchant's deposit doesn't arrive, or a transaction is declined incorrectly, or a chargeback is filed, the clock is ticking. Your merchant isn't going to wait 48 hours for an email response from a support queue.

Ask about support SLAs — not the marketing version, the contractual version. What is the guaranteed response time for critical issues? Is there a dedicated support contact for your integration, or are you in the general queue? Can your team access the provider's internal tools to troubleshoot, or do you have to relay everything through their support team?

The best providers give you direct access to a dashboard where your team can investigate deposit timing, transaction status, and chargeback details without opening a ticket. The worst ones make you a middleman between your merchants and their support team.

6. How Mature Is the API and Developer Documentation?

If your engineering team is going to build against this API for the next 3-5 years, the quality of the developer experience matters more than any feature on the marketing site.

Look at the documentation before the sales process, not after. Is it public? Is it complete? Are there working code examples in your stack? Is there a sandbox environment you can test against without signing a contract? How frequently does the API change, and how much notice do they give before breaking changes?

Talk to other platforms who have integrated with this provider — not the references the sales team gives you, but platforms you find independently. Ask them about the integration timeline versus what was quoted, the quality of technical support during the build, and the stability of the API post-launch.

7. What Are the Contract Terms That Will Hurt You Later?

Five contract clauses that platforms consistently overlook:

None of these are deal-breakers on their own. All of them are negotiable. But you have to know they're there to negotiate them.

8. Does This Provider's Roadmap Align with Yours?

The payments landscape is evolving. Real-time payments, A2A (account-to-account) transfers, embedded lending, and card issuing are all becoming part of the embedded finance stack. Your provider today might not have the capabilities you need in two years.

Ask about their product roadmap. Not the slide deck version — the real version. Are they investing in the capabilities that matter for your vertical? Do they have a track record of shipping what they promise? Are they building for platforms like yours, or are you a secondary use case for a provider that primarily serves enterprise merchants?

A provider that is perfectly adequate today but has no roadmap alignment with your needs will become the provider you're migrating away from in 24 months — and by then, the migration cost is real.

The Evaluation That Matters

Rate comparisons are necessary but insufficient. The providers who quote the best rate are often the ones who make it up in hidden fees, restrictive contracts, or poor support. The providers with slightly higher rates but better APIs, clearer migration paths, and genuine support infrastructure are almost always the better long-term partners.

The best payments partnerships are the ones where the economics improve as you grow. The worst ones are the ones where the contract prevents you from capturing that improvement.

If you're evaluating providers and want an independent assessment of proposals you've received, that's one of the most common use cases for a Margin Labs Quick Start Call. We review processor proposals, identify the contract terms that matter, and help you compare options without vendor bias.