RESOURCES

Empowering Smart Payments Decisions

Driving growth and innovation in a rapidly evolving financial landscape.

Follow @GlobalPaymentsConsultants on Instagram

Before a processor drops you, they usually tell you. Most merchants just don't recognize the signs.

𝟭. 𝗧𝗵𝗲𝘆 𝘀𝘁𝗮𝗿𝘁 𝗮𝘀𝗸𝗶𝗻𝗴 𝗳𝗼𝗿 𝗱𝗼𝗰𝘂𝗺𝗲𝗻𝘁𝗮𝘁𝗶𝗼𝗻 𝗼𝘂𝘁 𝗼𝗳 𝗻𝗼𝘄𝗵𝗲𝗿𝗲
A sudden request for updated financials, ownership docs, or processing history usually means someone flagged your account for review.

𝟮. 𝗬𝗼𝘂𝗿 𝗿𝗲𝘀𝗲𝗿𝘃𝗲 𝗴𝗲𝘁𝘀 𝗮𝗱𝗱𝗲𝗱 𝗼𝗿 𝗶𝗻𝗰𝗿𝗲𝗮𝘀𝗲𝗱 𝘄𝗶𝘁𝗵𝗼𝘂𝘁 𝘄𝗮𝗿𝗻𝗶𝗻𝗴
This is often the first real signal a processor is protecting itself against something, before they've decided what to do next.

𝟯. 𝗬𝗼𝘂𝗿 𝗮𝗰𝗰𝗼𝘂𝗻𝘁 𝗿𝗲𝗽 𝗴𝗼𝗲𝘀 𝗾𝘂𝗶𝗲𝘁
Fast, helpful responses turn vague, or stop altogether. That shift usually means something changed internally they're not telling you yet.

None of these guarantee you're getting dropped. Together, they're rarely a coincidence.

Have you ever caught one of these signs in time, or only recognized it after the fact?

You can't evaluate a processor from a sales call. You have to actually run volume through it.

𝗕𝘂𝗶𝗹𝗱 𝗮𝗻 𝗲𝘅𝗶𝘁 𝗶𝗻𝘁𝗼 𝗲𝘃𝗲𝗿𝘆 𝗿𝗲𝗹𝗮𝘁𝗶𝗼𝗻𝘀𝗵𝗶𝗽 𝗯𝗲𝗳𝗼𝗿𝗲 𝘆𝗼𝘂 𝗲𝘃𝗲𝗿 𝘁𝗲𝘀𝘁 𝗶𝘁
A termination-for-convenience clause is what turns "signing up" into "evaluating." Without a clean way out, you're not testing a processor, you're committing to one and hoping.

𝗪𝗵𝗮𝘁 𝗮𝗰𝘁𝘂𝗮𝗹 𝘁𝗲𝘀𝘁𝗶𝗻𝗴 𝗹𝗼𝗼𝗸𝘀 𝗹𝗶𝗸𝗲
Real volume, not a demo account. A meaningful window, not a week. And a deliberate look at what happens when something goes wrong, a dispute, a support ticket, a sudden question from underwriting, not just how smooth onboarding felt.

𝗠𝗲𝗮𝘀𝘂𝗿𝗲 𝘁𝗵𝗲 𝘁𝗵𝗶𝗻𝗴𝘀 𝘁𝗵𝗮𝘁 𝗮𝗰𝘁𝘂𝗮𝗹𝗹𝘆 𝗺𝗮𝘁𝘁𝗲𝗿 𝗹𝗮𝘁𝗲𝗿
Approval rates on your actual transaction mix. How fast funds actually settle, not what the contract says should happen. Whether a real person responds when something breaks, and how quickly. Marketing materials answer none of these honestly.

𝗧𝗵𝗲 𝗲𝘃𝗮𝗹𝘂𝗮𝘁𝗶𝗼𝗻 𝗽𝗲𝗿𝗶𝗼𝗱 𝗵𝗮𝘀 𝗮𝗻 𝗲𝗻𝗱 𝗱𝗮𝘁𝗲
At some point, testing has to convert into commitment, or it just becomes another form of avoidance. Once you have real data on which relationships are actually delivering, consolidate to the two or three that earned it, and exit the rest cleanly using the terms built in from day one.

𝗘𝗮𝗿𝗻𝗶𝗻𝗴 𝘆𝗼𝘂𝗿 𝗯𝘂𝘀𝗶𝗻𝗲𝘀𝘀 𝗱𝗼𝗲𝘀𝗻'𝘁 𝘀𝘁𝗼𝗽 𝗼𝗻𝗰𝗲 𝘆𝗼𝘂'𝘃𝗲 𝗰𝗵𝗼𝘀𝗲𝗻
The payments industry keeps moving. Processors get acquired, leadership changes, technology shifts. Even a relationship that earned its place today should keep earning it, not hold that place through a contract that locks you in for three-plus years with steep penalties for leaving. A PSP relationship should always be able to end on merit, not just on a calendar.

For high-risk merchants with real structural complexity, is your evaluation actually testing anything, or did it end the moment onboarding felt smooth?

Established or alternative? If you're a high-risk merchant with real structural complexity, the smartest move is combining, not choosing.

𝗘𝘀𝘁𝗮𝗯𝗹𝗶𝘀𝗵𝗲𝗱 𝗽𝗿𝗼𝗰𝗲𝘀𝘀𝗼𝗿𝘀 𝗴𝗶𝘃𝗲 𝘆𝗼𝘂 𝘀𝗰𝗮𝗹𝗲 𝗮𝗻𝗱 𝘁𝗿𝘂𝘀𝘁, 𝗻𝗼𝘁 𝗳𝗹𝗲𝘅𝗶𝗯𝗶𝗹𝗶𝘁𝘆
Best-priced acquirers and industry specialists bring the pricing leverage and reputation that come from scale. What they don't always bring is the flexibility to accommodate complex ownership structures, or entities that don't fit standard underwriting boxes.

𝗔𝗹𝘁𝗲𝗿𝗻𝗮𝘁𝗶𝘃𝗲 𝗽𝗿𝗼𝗰𝗲𝘀𝘀𝗼𝗿𝘀 𝘀𝗼𝗹𝘃𝗲 𝘀𝗽𝗲𝗰𝗶𝗳𝗶𝗰 𝗽𝗿𝗼𝗯𝗹𝗲𝗺𝘀 𝘄𝗲𝗹𝗹, 𝗻𝗼𝘁 𝗲𝘃𝗲𝗿𝘆𝘁𝗵𝗶𝗻𝗴
A PSP aggregator with stablecoin settlement, a Merchant of Record, a high-risk ISO relationship, each is genuinely excellent at the narrow problem it was built for. None of them are trying to be your entire processing stack, and expecting one to cover everything just recreates the single-point-of-failure problem in a different form.

𝗧𝗵𝗲 𝗰𝗼𝗺𝗯𝗶𝗻𝗮𝘁𝗶𝗼𝗻 𝗰𝗼𝘃𝗲𝗿𝘀 𝘄𝗵𝗮𝘁 𝗲𝗶𝘁𝗵𝗲𝗿 𝗮𝗹𝗼𝗻𝗲 𝗹𝗲𝗮𝘃𝗲𝘀 𝗲𝘅𝗽𝗼𝘀𝗲𝗱
Where an established processor's underwriting can't accommodate a specific entity or ownership structure, an alternative often can. Where an alternative processor's pricing doesn't scale efficiently at real volume, an established one usually does. Pairing them closes gaps that neither would close alone.

𝗧𝗵𝗶𝘀 𝗶𝘀𝗻'𝘁 𝗮𝗯𝗼𝘂𝘁 𝗵𝗲𝗱𝗴𝗶𝗻𝗴 𝗿𝗶𝘀𝗸 𝗮𝗹𝗼𝗻𝗲
It's about coverage. A high-risk merchant with real structural complexity relying only on established processors is exposed the moment their structure or category falls outside standard underwriting. Relying only on alternative processors leaves them exposed the moment they need pricing or scale those processors weren't built to deliver.

If you're a high-risk merchant with real structural complexity, is your current stack leaning entirely on one type, established or alternative, and where does that leave you exposed?

Most foreign merchants don't actually choose a processor. They choose whichever was easiest to set up, think Stripe, PayPal, platforms built for fast developer access.

𝗘𝗮𝘀𝘆 𝘀𝗲𝘁𝘂𝗽 𝗶𝘀𝗻'𝘁 𝘁𝗵𝗲 𝘀𝗮𝗺𝗲 𝗮𝘀 𝘁𝗵𝗲 𝗿𝗶𝗴𝗵𝘁 𝗳𝗶𝘁
These platforms optimize for fast integration, not for how they'll evaluate your business once you're live. Most merchants never ask how a provider underwrites businesses like theirs, and rarely get real input on the contract. When something goes wrong, there's often no dedicated contact, just a support queue built for someone far less complex than you.

𝗠𝘂𝗹𝘁𝗶𝗽𝗹𝗲 𝗰𝗮𝘁𝗲𝗴𝗼𝗿𝗶𝗲𝘀 𝘄𝗼𝗿𝘁𝗵 𝘂𝗻𝗱𝗲𝗿𝘀𝘁𝗮𝗻𝗱𝗶𝗻𝗴
A best-priced acquirer for straightforward volume. An industry specialist for elevated risk. Global infrastructure for cross-border structuring. A PSP aggregator with stablecoin settlement, useful without a banking relationship. A Merchant of Record with its own PSP network. And high-risk ISO access, which can open doors a direct application can't.

𝗖𝗮𝘁𝗲𝗴𝗼𝗿𝘆 𝗳𝗶𝘁 𝗺𝗮𝘁𝘁𝗲𝗿𝘀 𝗺𝗼𝘀𝘁 𝗶𝗻 𝗵𝗶𝗴𝗵-𝗿𝗶𝘀𝗸 𝘃𝗲𝗿𝘁𝗶𝗰𝗮𝗹𝘀
Underwriters score risk by MCC first. A processor that approved you without real category expertise is often the one that restricts or terminates you later. The early "yes" isn't the same as genuine fit.

𝗢𝘄𝗻𝗲𝗿𝘀𝗵𝗶𝗽 𝘀𝘁𝗿𝘂𝗰𝘁𝘂𝗿𝗲 𝗰𝗮𝗻 𝗮𝗱𝗱 𝗮𝗻𝗼𝘁𝗵𝗲𝗿 𝗹𝗮𝘆𝗲𝗿
Not every entity in a multi-entity structure has ownership that fits standard citizenship or residency requirements. The right combination often depends on finding relationships built to accommodate that.

𝗡𝗼𝘁 𝗲𝘃𝗲𝗿𝘆 𝗺𝗲𝗿𝗰𝗵𝗮𝗻𝘁 𝗻𝗲𝗲𝗱𝘀 𝘁𝗵𝗶𝘀
A low-risk business rarely needs to evaluate multiple relationships. A high-risk, complex one does, testing several before narrowing to the two or three that earn a permanent place. Complementary strengths, not the count, make the stack resilient.

This is exactly the kind of evaluation we help merchants work through.

Have you mapped your setup against what actually makes sense for your business, or did you default to the easiest, most developer-friendly route?

DCC can pay you a commission on every international sale. It's also one of the fastest ways to lose customer trust.

𝗗𝗖𝗖 𝗹𝗼𝗼𝗸𝘀 𝗹𝗶𝗸𝗲 𝗮 𝗰𝘂𝘀𝘁𝗼𝗺𝗲𝗿 𝗰𝗼𝗻𝘃𝗲𝗻𝗶𝗲𝗻𝗰𝗲. 𝗜𝘁'𝘀 𝗮𝗹𝘀𝗼 𝗮 𝗺𝗮𝗿𝗸𝘂𝗽.
Letting a customer pay in their home currency at checkout sounds like a win, no surprises on their statement. But the exchange rate used typically carries a 3-7% markup over the real interbank rate, sometimes more, and most customers have no easy way to know that.

𝗠𝗲𝗿𝗰𝗵𝗮𝗻𝘁𝘀 𝗰𝗮𝗻 𝗲𝗮𝗿𝗻 𝗮 𝗰𝘂𝘁 𝗼𝗳 𝘁𝗵𝗮𝘁 𝗺𝗮𝗿𝗸𝘂𝗽
DCC providers typically share a portion of that markup with the merchant who offers it. That's a real incentive to turn it on, and a real reason to think carefully about whether it's worth the trust it can cost.

𝗧𝗵𝗲 𝗰𝘂𝘀𝘁𝗼𝗺𝗲𝗿 𝗵𝗮𝘀 𝘁𝗼 𝗮𝗰𝘁𝗶𝘃𝗲𝗹𝘆 𝗰𝗵𝗼𝗼𝘀𝗲 𝗶𝘁, 𝗻𝗼𝘁 𝗴𝗲𝘁 𝗱𝗲𝗳𝗮𝘂𝗹𝘁𝗲𝗱 𝗶𝗻𝘁𝗼 𝗶𝘁
Visa and Mastercard rules require DCC to be presented neutrally, with the customer making an active choice. If a customer wasn't given a real choice, their bank can pursue a chargeback against the merchant.

𝗥𝗲𝗴𝘂𝗹𝗮𝘁𝗼𝗿𝘀 𝗮𝗿𝗲 𝗽𝘂𝘀𝗵𝗶𝗻𝗴 𝗳𝗼𝗿 𝗺𝗼𝗿𝗲 𝘁𝗿𝗮𝗻𝘀𝗽𝗮𝗿𝗲𝗻𝗰𝘆, 𝗻𝗼𝘁 𝗹𝗲𝘀𝘀
EU rules already require showing the markup against the official reference rate before a customer confirms. That transparency bar is likely to keep rising, not loosen.

How much do you think your customers actually value DCC's convenience, versus what it's quietly costing them?

A $38 billion settlement just gave merchants a right they've never had: the ability to say no to specific premium cards.

𝗧𝗵𝗲 𝗿𝗮𝘁𝗲 𝗰𝘂𝘁 𝗶𝘀𝗻'𝘁 𝘁𝗵𝗲 𝘀𝘁𝗼𝗿𝘆
Interchange drops 0.1 percentage point for five years, and standard consumer cards get capped at 1.25% for eight. Against a 2024 average of 2.35%, that's a rounding error the networks can absorb without blinking.

𝗧𝗵𝗲 𝗿𝗲𝗮𝗹 𝗰𝗵𝗮𝗻𝗴𝗲: "𝗵𝗼𝗻𝗼𝗿 𝗮𝗹𝗹 𝗰𝗮𝗿𝗱𝘀" 𝗶𝘀 𝗲𝗻𝗱𝗶𝗻𝗴
For the first time since the rule existed, merchants will be able to decline entire categories of premium or rewards cards, and surcharge or discount by card tier specifically, not just by network. That's a fundamentally different lever than blanket surcharging.

𝗧𝗵𝗲 𝘁𝗮𝗿𝗴𝗲𝘁𝗶𝗻𝗴 𝗺𝗮𝘁𝘁𝗲𝗿𝘀 𝗺𝗼𝗿𝗲 𝘁𝗵𝗮𝗻 𝘆𝗲𝘀𝘁𝗲𝗿𝗱𝗮𝘆'𝘀 𝗱𝗮𝘁𝗮 𝘀𝘂𝗴𝗴𝗲𝘀𝘁𝗲𝗱
Only 22% of premium cardholders say they'd switch payment methods if surcharged, versus 33% of no-fee cardholders. Premium cardholders also spend nearly 3x more per month. Surcharging by tier, once this settlement is final, is a much lower-risk lever than surcharging everyone equally.

𝗜𝘁'𝘀 𝗻𝗼𝘁 𝗳𝗶𝗻𝗮𝗹 𝘆𝗲𝘁
The settlement has preliminary approval, not final approval, and the National Retail Federation has already called it insufficient. Worth watching closely rather than planning around it yet.

If you could decline specific premium card tiers tomorrow, would you?

40% of merchants worldwide are actively considering leaving their bank. It's not about trust, it's about speed.

𝗢𝗻𝗯𝗼𝗮𝗿𝗱𝗶𝗻𝗴 𝗶𝘀 𝘁𝗵𝗲 𝗳𝗶𝗿𝘀𝘁 𝗯𝗿𝗲𝗮𝗸𝗶𝗻𝗴 𝗽𝗼𝗶𝗻𝘁
Bank onboarding can take up to seven days and cost as much as $496. PayTechs get merchants live in under 60 minutes for as little as $214. That gap alone is enough to push merchants toward alternatives before they've processed a single transaction.

𝗦𝗮𝘁𝗶𝘀𝗳𝗮𝗰𝘁𝗶𝗼𝗻 𝗶𝘀 𝘄𝗼𝗿𝘀𝗲 𝘁𝗵𝗲 𝘀𝗺𝗮𝗹𝗹𝗲𝗿 𝘆𝗼𝘂 𝗮𝗿𝗲
Only 15% of small merchants and 22% of mid-sized merchants report being satisfied with their bank's merchant services, according to Capgemini's World Payments Report 2026. Banks have largely deprioritized this segment in favor of larger accounts.

𝗨𝗻𝗿𝗲𝗹𝗶𝗮𝗯𝗶𝗹𝗶𝘁𝘆 𝗵𝗮𝘀 𝗮 𝗾𝘂𝗮𝗻𝘁𝗶𝗳𝗶𝗮𝗯𝗹𝗲 𝗰𝗼𝘀𝘁
Merchants report up to nine hours of payment system downtime annually. Every one of those hours is revenue that simply doesn't get captured.

𝗕𝘂𝘁 𝗺𝗼𝘀𝘁 𝗺𝗲𝗿𝗰𝗵𝗮𝗻𝘁𝘀 𝘄𝗼𝘂𝗹𝗱𝗻'𝘁 𝗹𝗲𝗮𝘃𝗲 𝗶𝗳 𝗴𝗶𝘃𝗲𝗻 𝗮 𝗿𝗲𝗮𝘀𝗼𝗻 𝘁𝗼 𝘀𝘁𝗮𝘆
66% of merchants still prefer a traditional provider, and 8 in 10 say they'd switch back to a bank if it matched PayTech-level service at the same cost. This isn't really about trust in banks eroding, it's about a service gap nobody's closing.

Is your current provider actually earning your business, or just holding onto it by default?

Two businesses can sell the exact same product and carry completely different legal, tax, and chargeback exposure, depending on which model they chose.

𝗪𝗵𝗼 𝗶𝘀 𝗹𝗲𝗴𝗮𝗹𝗹𝘆 𝘁𝗵𝗲 𝘀𝗲𝗹𝗹𝗲𝗿 𝗶𝘀 𝘁𝗵𝗲 𝗿𝗲𝗮𝗹 𝗾𝘂𝗲𝘀𝘁𝗶𝗼𝗻
Under a standard merchant account, your business is the seller of record: you own tax collection, chargeback liability, and compliance. Under a Merchant of Record model, a third party legally becomes the seller and takes that liability on directly, for a fee.

𝗠𝗼𝗥 𝗯𝘂𝘆𝘀 𝘀𝗽𝗲𝗲𝗱 𝗮𝗻𝗱 𝘀𝗶𝗺𝗽𝗹𝗶𝗰𝗶𝘁𝘆, 𝗻𝗼𝘁 𝗮 𝗯𝗲𝘁𝘁𝗲𝗿 𝗿𝗮𝘁𝗲
MoR fees typically run higher than a standard processing rate, because that fee bundles payment processing, tax remittance across jurisdictions, chargeback handling, and compliance into one number. You're not paying more for the same thing, you're paying for someone else to own the liability.

𝗧𝗵𝗲 𝘁𝗿𝗮𝗱𝗲𝗼𝗳𝗳 𝗶𝘀 𝗰𝗼𝗻𝘁𝗿𝗼𝗹
An MoR usually owns the customer payment relationship, the refund policy, and often the checkout experience itself. A standard merchant account keeps that control with you, but puts the compliance burden squarely on your shoulders too.

𝗧𝗵𝗲 𝗺𝗮𝘁𝗵 𝗳𝗹𝗶𝗽𝘀 𝗮𝘁 𝘀𝗰𝗮𝗹𝗲
For an early-stage digital goods or subscription business selling internationally, an MoR's bundled fee is often cheaper than building tax and compliance infrastructure from scratch. At meaningful volume, that same percentage fee can cost more than negotiating a direct merchant account and handling compliance separately.

Are you actually the legal seller of record for your own transactions, or does your provider quietly own that?

Adding a surcharge can recover real margin. It can also cost you the sale entirely. Here's what the data actually shows:

𝗢𝗻𝗲 𝗶𝗻 𝘁𝗵𝗿𝗲𝗲 𝗰𝘂𝘀𝘁𝗼𝗺𝗲𝗿𝘀 𝘄𝗮𝗹𝗸𝘀 𝘄𝗵𝗲𝗻 𝘁𝗵𝗲 𝗳𝗲𝗲 𝗮𝗽𝗽𝗲𝗮𝗿𝘀
Of small businesses that surcharge credit card transactions, 32% report customers cancel the purchase at least some of the time when the fee shows up at checkout, according to a 2026 J.D. Power survey.

𝗧𝗵𝗲 𝗹𝗼𝘆𝗮𝗹𝘁𝘆 𝗵𝗶𝘁 𝗶𝘀 𝗯𝗶𝗴𝗴𝗲𝗿 𝘁𝗵𝗮𝗻 𝘁𝗵𝗲 𝗮𝗯𝗮𝗻𝗱𝗼𝗻𝗺𝗲𝗻𝘁 𝗻𝘂𝗺𝗯𝗲𝗿
56% of consumers say they're very or extremely likely to switch merchants entirely because of a surcharge. This isn't just a lost sale in the moment, it's a lost customer going forward.

𝗬𝗼𝘂 𝗰𝗮𝗻 𝗻𝗲𝘃𝗲𝗿 𝘀𝘂𝗿𝗰𝗵𝗮𝗿𝗴𝗲 𝗮 𝗱𝗲𝗯𝗶𝘁 𝗰𝗮𝗿𝗱
Surcharging a debit card, even one run as credit at the terminal, is a Durbin Amendment violation. Getting this wrong isn't a customer experience problem, it's a compliance one.

𝗧𝗿𝗮𝗻𝘀𝗽𝗮𝗿𝗲𝗻𝗰𝘆 𝗶𝘀 𝘁𝗵𝗲 𝗱𝗶𝗳𝗳𝗲𝗿𝗲𝗻𝗰𝗲 𝗯𝗲𝘁𝘄𝗲𝗲𝗻 𝗹𝗼𝘀𝗶𝗻𝗴 𝗮 𝘀𝗮𝗹𝗲 𝗮𝗻𝗱 𝗸𝗲𝗲𝗽𝗶𝗻𝗴 𝗼𝗻𝗲
Clearly displaying dual pricing, or offering a no-fee cash or bank-transfer alternative, keeps the large majority of shoppers loyal even when they're paying more to use a card. Surprise fees at the final step are what actually drive people away, not the fee itself.

Have you tested surcharging, or have you avoided it because of the customer reaction?

(5/5) Most subscription businesses inherited their billing setup instead of choosing it.

𝗔 𝘀𝘁𝗮𝗻𝗱𝗮𝗿𝗱 𝗣𝗦𝗣 𝘄𝗮𝘀𝗻'𝘁 𝗯𝘂𝗶𝗹𝘁 𝗳𝗼𝗿 𝗿𝗲𝗰𝘂𝗿𝗿𝗶𝗻𝗴 𝗯𝗶𝗹𝗹𝗶𝗻𝗴 𝗹𝗼𝗴𝗶𝗰
Dedicated subscription billing platforms handle proration, plan changes, usage-based billing, and dunning natively. A standard processor can take a card, but the recurring logic on top of it is usually something you have to build or bolt on yourself.

𝗠𝗲𝗿𝗰𝗵𝗮𝗻𝘁 𝗼𝗳 𝗥𝗲𝗰𝗼𝗿𝗱 𝘀𝗼𝗹𝘃𝗲𝘀 𝗮 𝗽𝗿𝗼𝗯𝗹𝗲𝗺 𝗺𝗼𝘀𝘁 𝘀𝘂𝗯𝘀𝗰𝗿𝗶𝗽𝘁𝗶𝗼𝗻 𝗯𝘂𝘀𝗶𝗻𝗲𝘀𝘀𝗲𝘀 𝗱𝗼𝗻'𝘁 𝘀𝗲𝗲 𝗰𝗼𝗺𝗶𝗻𝗴
Selling subscriptions internationally means dealing with VAT, GST, and sales tax obligations across dozens of jurisdictions. An MoR takes on that liability directly; a standard PSP setup leaves it entirely on you.

𝗖𝗼𝗻𝘀𝗼𝗹𝗶𝗱𝗮𝘁𝗲𝗱 𝘃𝘀. 𝗰𝗼𝗯𝗯𝗹𝗲𝗱-𝘁𝗼𝗴𝗲𝘁𝗵𝗲𝗿 𝗶𝘀 𝗮 𝗿𝗲𝗮𝗹 𝘁𝗿𝗮𝗱𝗲𝗼𝗳𝗳
An integrated platform is faster to launch and reduces reconciliation headaches. Piecing together separate billing, dunning, and tax tools gives more control and can be cheaper at scale, but only if someone owns making them work together well.

𝗪𝗵𝗮𝘁 𝘁𝗵𝗶𝘀 𝘄𝗲𝗲𝗸 𝗮𝗱𝗱𝗲𝗱 𝘂𝗽 𝘁𝗼
Involuntary churn is 20-40% of total churn, and most of it is recoverable. Account updaters and smart retry timing catch it before a customer ever notices. Dunning done well recovers the rest without pushing people to actually leave. And cancellation compliance isn't optional just because a rule got vacated. The infrastructure choice is what determines whether all of that runs smoothly, or takes constant manual effort to hold together.

If you rebuilt your subscription billing stack from scratch today, would you choose what you're running now?

(3/5) The right message at the right moment recovers a subscriber. The wrong one pushes them to actually cancel.

𝗦𝗠𝗦 𝗼𝘂𝘁𝗽𝗲𝗿𝗳𝗼𝗿𝗺𝘀 𝗲𝗺𝗮𝗶𝗹 𝗯𝘆 𝗮 𝘄𝗶𝗱𝗲 𝗺𝗮𝗿𝗴𝗶𝗻, 𝗯𝘂𝘁 𝘁𝗶𝗺𝗶𝗻𝗴 𝗺𝗮𝘁𝘁𝗲𝗿𝘀
SMS gets roughly 98% open rates versus 20-40% for email, and most people check a text within five minutes. But leading with SMS on day one reads as aggressive. It works best layered in after the second or third email, not as the opening move.

𝗚𝗲𝗻𝗲𝗿𝗶𝗰 "𝗽𝗮𝘆𝗺𝗲𝗻𝘁 𝗳𝗮𝗶𝗹𝗲𝗱" 𝗲𝗺𝗮𝗶𝗹𝘀 𝗹𝗲𝗮𝘃𝗲 𝗿𝗲𝘃𝗲𝗻𝘂𝗲 𝗼𝗻 𝘁𝗵𝗲 𝘁𝗮𝗯𝗹𝗲
Matching the message to the actual decline reason, an expired card versus insufficient funds versus a bank-side issue, recovers meaningfully more than sending the same template to everyone. Dunning should only fire when a customer actually needs to act, not on soft declines your retry logic is already handling quietly.

𝗢𝗻𝗲 𝗲𝗺𝗮𝗶𝗹 𝗶𝘀𝗻'𝘁 𝗮 𝘀𝘁𝗿𝗮𝘁𝗲𝗴𝘆
Recovery comes from persistence across a sequence, not a single attempt. Spacing communications out over one to three weeks, rather than giving up after one message, is what separates strong recovery from weak recovery.

𝗣𝗮𝘂𝘀𝗲, 𝗱𝗼𝗻'𝘁 𝗰𝗮𝗻𝗰𝗲𝗹, 𝗮𝘁 𝘁𝗵𝗲 𝗲𝗻𝗱 𝗼𝗳 𝘁𝗵𝗲 𝘀𝗲𝗾𝘂𝗲𝗻𝗰𝗲
Hard-cancelling a customer at day 30 forecloses recoveries that would have happened at day 45 or 60. Offering a pause instead preserves the relationship and the customer's data, and makes reactivation far easier than re-acquiring them later.

What's the most aggressive dunning message you've ever received as a customer, and did it actually work on you?

(2/5) The single highest-ROI fix for subscription churn isn't a discount. It's a background service most merchants have never turned on.

𝗔𝗰𝗰𝗼𝘂𝗻𝘁 𝘂𝗽𝗱𝗮𝘁𝗲𝗿 𝘀𝗲𝗿𝘃𝗶𝗰𝗲𝘀 𝗰𝗮𝘁𝗰𝗵 𝘁𝗵𝗲 𝗽𝗿𝗼𝗯𝗹𝗲𝗺 𝗯𝗲𝗳𝗼𝗿𝗲 𝗶𝘁 𝗲𝘃𝗲𝗿 𝗵𝗮𝗽𝗽𝗲𝗻𝘀
Visa and Mastercard both run services that automatically refresh expired or reissued card details in the background, before the next billing attempt ever runs. Card network data puts the impact at reducing expiry-related involuntary churn by 40-60%, the single highest-ROI fix available.

𝗦𝗺𝗮𝗿𝘁 𝗿𝗲𝘁𝗿𝘆 𝘁𝗶𝗺𝗶𝗻𝗴 𝗺𝗮𝘁𝘁𝗲𝗿𝘀 𝗺𝗼𝗿𝗲 𝗳𝗼𝗿 𝗿𝗲𝗰𝘂𝗿𝗿𝗶𝗻𝗴 𝗯𝗶𝗹𝗹𝗶𝗻𝗴
A fixed retry schedule ignores something one-time purchases don't have to think about: predictable pay cycles. Timing retries around when funds are actually likely to be available recovers meaningfully more than a flat interval.

𝗔𝗻𝗻𝘂𝗮𝗹 𝗯𝗶𝗹𝗹𝗶𝗻𝗴 𝗻𝗲𝗲𝗱𝘀 𝗮 𝗱𝗶𝗳𝗳𝗲𝗿𝗲𝗻𝘁 𝗮𝗽𝗽𝗿𝗼𝗮𝗰𝗵 𝘁𝗵𝗮𝗻 𝗺𝗼𝗻𝘁𝗵𝗹𝘆
A failed monthly charge gets another shot in 30 days regardless. A failed annual charge doesn't, which makes getting the retry window right on the first attempt far more consequential.

𝗧𝗵𝗲 𝗰𝗼𝗺𝗯𝗶𝗻𝗮𝘁𝗶𝗼𝗻 𝗯𝗲𝗮𝘁𝘀 𝗮𝗻𝘆 𝘀𝗶𝗻𝗴𝗹𝗲 𝘁𝗮𝗰𝘁𝗶𝗰
Smart retries alone recover a meaningful share of failed payments. Layering an account updater and a dunning sequence on top compounds the recovery rate well beyond what any single tactic achieves alone.

When's the last time you actually saw the numbers on what your account updater is recovering?

(1/5) If you run a subscription business, some of your "cancellations" were never cancellations at all.

𝗜𝗻𝘃𝗼𝗹𝘂𝗻𝘁𝗮𝗿𝘆 𝗰𝗵𝘂𝗿𝗻 𝗹𝗼𝗼𝗸𝘀 𝗲𝘅𝗮𝗰𝘁𝗹𝘆 𝗹𝗶𝗸𝗲 𝘃𝗼𝗹𝘂𝗻𝘁𝗮𝗿𝘆 𝗰𝗵𝘂𝗿𝗻 𝗼𝗻 𝗮 𝗱𝗮𝘀𝗵𝗯𝗼𝗮𝗿𝗱
A customer who never chose to leave and a card that just failed to charge produce the exact same result: a lost subscriber. Most subscription businesses don't separate the two, which means they don't actually know how much of their "churn" was preventable.

𝗧𝗵𝗲 𝗻𝘂𝗺𝗯𝗲𝗿 𝗶𝘀 𝗯𝗶𝗴𝗴𝗲𝗿 𝘁𝗵𝗮𝗻 𝗺𝗼𝘀𝘁 𝗳𝗼𝘂𝗻𝗱𝗲𝗿𝘀 𝗮𝘀𝘀𝘂𝗺𝗲
20-40% of all subscription churn is involuntary, driven by failed payments rather than a customer decision. Industry-wide, that added up to an estimated $129 billion in lost subscription revenue in 2025 alone.

𝗠𝗼𝘀𝘁 𝗼𝗳 𝗶𝘁 𝘄𝗮𝘀 𝗻𝗲𝘃𝗲𝗿 𝗮 𝗹𝗼𝘀𝘁 𝗰𝘂𝘀𝘁𝗼𝗺𝗲𝗿
Unlike voluntary churn, involuntary churn is largely recoverable. The customer wanted to keep paying. Something in the billing chain just failed silently, an expired card, a network timeout, a false decline, with no cancellation button ever touched.

𝗧𝗵𝗶𝘀 𝘄𝗲𝗲𝗸
We're covering what to actually do about it: the technical fixes, the communication layer that recovers customers without annoying them, a live regulatory risk every subscription business should know about, and how to choose infrastructure that supports all of it.

Do you track involuntary churn separately from voluntary churn, or does it all just show up as "churn"?

Comparing processors headline-to-headline on rate alone is how merchants end up locked into a bad fit. Here's a fuller scorecard worth running before you sign anywhere:

𝗥𝗮𝘁𝗲𝘀 𝗮𝗻𝗱 𝗳𝗲𝗲 𝘁𝗿𝗮𝗻𝘀𝗽𝗮𝗿𝗲𝗻𝗰𝘆
Ask whether you're being quoted interchange-plus (wholesale cost and markup shown separately) or a flat, bundled rate (simpler and more predictable, but the underlying cost breakdown isn't visible). Neither is inherently better, it depends on whether you value simplicity or granular visibility, but you should know which one you're actually getting.

𝗖𝗼𝗻𝘁𝗿𝗮𝗰𝘁 𝗳𝗹𝗲𝘅𝗶𝗯𝗶𝗹𝗶𝘁𝘆
Auto-renewal terms, early termination fees, and whether a termination-for-convenience clause is even on the table. A processor that won't discuss any of these is telling you something.

𝗥𝗲𝘀𝗲𝗿𝘃𝗲 𝗮𝗻𝗱 𝘀𝗲𝘁𝘁𝗹𝗲𝗺𝗲𝗻𝘁 𝘁𝗲𝗿𝗺𝘀
Whether reserves are capped, whether there's a defined review and release schedule, and how fast you actually get paid once a transaction clears.

𝗥𝗶𝘀𝗸 𝗮𝗽𝗽𝗲𝘁𝗶𝘁𝗲 𝗳𝗼𝗿 𝘆𝗼𝘂𝗿 𝗶𝗻𝗱𝘂𝘀𝘁𝗿𝘆
Some processors are genuinely comfortable with your MCC and business model, and some just say they are until underwriting sees your actual application. Ask about approval rates for businesses like yours specifically.

𝗥𝗲𝗮𝗹 𝗵𝘂𝗺𝗮𝗻 𝘀𝘂𝗽𝗽𝗼𝗿𝘁
Do you get a dedicated contact, or a ticket queue? This matters most exactly when something goes wrong, not during the sales process when everyone is responsive.

Which of these has actually burned you before?

(2/2) Yesterday I covered why most declines are recoverable. Today: what you can actually do about it.

None of this requires switching processors. It starts with asking better questions:

𝗔𝘀𝗸 𝘄𝗵𝗲𝘁𝗵𝗲𝗿 𝘆𝗼𝘂'𝗿𝗲 𝗼𝗻 𝘀𝗺𝗮𝗿𝘁 𝗿𝗲𝘁𝗿𝗶𝗲𝘀 𝗼𝗿 𝗮 𝘀𝘁𝗮𝘁𝗶𝗰 𝘀𝗰𝗵𝗲𝗱𝘂𝗹𝗲
A static schedule retries every failure the same way regardless of decline code, issuer, or card type. Smart retry logic reads the decline reason and times each attempt around when funds are actually likely to be available. Ask your processor directly which one you're running.

𝗔𝘀𝗸 𝗮𝗯𝗼𝘂𝘁 𝗮𝗰𝗰𝗼𝘂𝗻𝘁 𝘂𝗽𝗱𝗮𝘁𝗲𝗿 𝘀𝗲𝗿𝘃𝗶𝗰𝗲𝘀
These automatically refresh expired or reissued card details before a decline even happens, especially valuable for recurring billing. Not every processor enables this by default.

𝗔𝘀𝗸 𝗵𝗼𝘄 𝘀𝗼𝗳𝘁 𝗮𝗻𝗱 𝗵𝗮𝗿𝗱 𝗱𝗲𝗰𝗹𝗶𝗻𝗲𝘀 𝗮𝗿𝗲 𝗯𝗲𝗶𝗻𝗴 𝗿𝗼𝘂𝘁𝗲𝗱
Decline codes are messy, and some issuers return the same generic code for most of their declines. Ask whether your system is actually distinguishing between the two, or retrying everything and hoping.

𝗧𝗿𝗲𝗮𝘁 𝘆𝗼𝘂𝗿 𝗿𝗲𝗰𝗼𝘃𝗲𝗿𝘆 𝗿𝗮𝘁𝗲 𝗹𝗶𝗸𝗲 𝗮 𝗞𝗣𝗜
Ask your processor to show you the actual number, not just your overall approval rate. If you don't know it, that's usually a sign no one's optimizing it.

Have you ever actually asked your processor how your retries are configured?

(1/2) Most declined payments aren't actually declined, they're just mistimed. Here's what the data on retries actually shows:

𝗠𝗼𝘀𝘁 𝗱𝗲𝗰𝗹𝗶𝗻𝗲𝘀 𝗮𝗿𝗲𝗻'𝘁 𝘄𝗵𝗮𝘁 𝘁𝗵𝗲𝘆 𝗹𝗼𝗼𝗸 𝗹𝗶𝗸𝗲
Soft declines, temporary issues like a network timeout or a momentary insufficient-funds check, make up 70-90% of all card-not-present payment failures. The card is fine. The timing wasn't.

𝗥𝗲𝘁𝗿𝘆𝗶𝗻𝗴 𝘁𝗼𝗼 𝘀𝗼𝗼𝗻 𝗹𝗲𝗮𝘃𝗲𝘀 𝗺𝗼𝗻𝗲𝘆 𝗼𝗻 𝘁𝗵𝗲 𝘁𝗮𝗯𝗹𝗲
One dataset found waiting 24 hours before a retry, instead of the standard 2, improved recovery by 6.5%. Adding a few extra, well-timed retry attempts lifted recovery by over 20%.

𝗡𝗼𝘁 𝗲𝘃𝗲𝗿𝘆 𝗱𝗲𝗰𝗹𝗶𝗻𝗲 𝘀𝗵𝗼𝘂𝗹𝗱 𝗯𝗲 𝗿𝗲𝘁𝗿𝗶𝗲𝗱
Retrying a genuinely hard decline, a stolen or closed card, wastes processing fees and can trigger card network penalties. Knowing which is which matters more than retrying everything and hoping.

Do you actually know your payment recovery rate, or are you just assuming retries are being handled?

Tomorrow: what you can actually do about it.

Visa, Mastercard, Amex, and Stripe just backed a new way for AI to pay for things, no card, no login, no checkout page. Here's what actually launched:

𝗪𝗵𝗮𝘁 𝗮𝗰𝘁𝘂𝗮𝗹𝗹𝘆 𝗹𝗮𝘂𝗻𝗰𝗵𝗲𝗱
The x402 Foundation went fully operational on July 14, 2026 under the Linux Foundation, with 40 member organizations including Visa, Mastercard, American Express, Stripe, Google, and Shopify.

𝗜𝘁 𝗿𝗲𝘃𝗶𝘃𝗲𝘀 𝗮 𝟯𝟱-𝘆𝗲𝗮𝗿-𝗼𝗹𝗱 𝗱𝗲𝗮𝗱 𝘀𝘁𝗮𝘁𝘂𝘀 𝗰𝗼𝗱𝗲
"402 Payment Required" was reserved by the original web architects in 1991 and never used. x402 turns it into a working rail: a server responds "payment required," an AI agent pays programmatically, and the request retries automatically, in seconds.

𝗥𝗶𝗴𝗵𝘁 𝗻𝗼𝘄, 𝘁𝗵𝗶𝘀 𝗶𝘀 𝗺𝗮𝗰𝗵𝗶𝗻𝗲-𝘁𝗼-𝗺𝗮𝗰𝗵𝗶𝗻𝗲, 𝗻𝗼𝘁 𝘆𝗼𝘂𝗿 𝗮𝘃𝗲𝗿𝗮𝗴𝗲 𝗰𝗵𝗲𝗰𝗸𝗼𝘂𝘁
Think an AI agent paying a few cents to call a paid API hundreds of times a day, not an agent doing your customers' shopping for them on your storefront. That broader shift is coming too, just not through this specific protocol yet.

𝗧𝗵𝗲 𝗿𝗮𝗶𝗹 𝘂𝗻𝗱𝗲𝗿𝗻𝗲𝗮𝘁𝗵 𝗶𝘀𝗻'𝘁 𝗻𝗲𝘂𝘁𝗿𝗮𝗹 𝘆𝗲𝘁
The spec is payment-method agnostic, but real-world settlement today runs almost entirely on a stablecoin, on one company's blockchain. The card networks backing this are, in effect, backing a rail that could eventually reduce their own role in the transaction.

Is your business anywhere near ready for a customer's AI agent to be the one making the purchase?

Your account just froze. What you do in the first few hours determines whether this is a temporary setback or a real crisis. Here's the playbook:

𝗗𝗼 𝘁𝗵𝗲𝘀𝗲 𝗮𝘁 𝘁𝗵𝗲 𝘀𝗮𝗺𝗲 𝘁𝗶𝗺𝗲, 𝗻𝗼𝘁 𝗶𝗻 𝘀𝗲𝗾𝘂𝗲𝗻𝗰𝗲

𝗗𝗼𝗰𝘂𝗺𝗲𝗻𝘁 𝗲𝘃𝗲𝗿𝘆𝘁𝗵𝗶𝗻𝗴
Screenshot the freeze notice, save your recent transaction history, and log every communication with a timestamp. This becomes your evidence if you need to dispute the hold or escalate later.

𝗔𝗰𝘁𝗶𝘃𝗮𝘁𝗲 𝗯𝗮𝗰𝗸𝘂𝗽 𝗽𝗿𝗼𝗰𝗲𝘀𝘀𝗶𝗻𝗴
If you have redundancy, flip to it immediately. Don't wait to see how the freeze plays out, route new transactions through your secondary processor right away.

𝗖𝗮𝗹𝗹 𝘆𝗼𝘂𝗿 𝗰𝗵𝗮𝗺𝗽𝗶𝗼𝗻
Reach out to your sales rep, client success manager, or payments advisor, whoever actually knows your account. We make a point of setting every client up with a solid contact at their processor from day one, because having a real advocate matters most exactly when something goes wrong.

𝗜𝗳 𝘆𝗼𝘂𝗿 𝗰𝗵𝗮𝗺𝗽𝗶𝗼𝗻 𝗰𝗮𝗻'𝘁 𝗿𝗲𝘀𝗼𝗹𝘃𝗲 𝗶𝘁 𝗾𝘂𝗶𝗰𝗸𝗹𝘆

𝗘𝘀𝗰𝗮𝗹𝗮𝘁𝗲 𝘁𝗼 𝗿𝗶𝘀𝗸 𝗱𝗶𝗿𝗲𝗰𝘁𝗹𝘆
Skip standard support channels. General support can't release a risk hold no matter how many times you call.

𝗢𝗻𝗰𝗲 𝘆𝗼𝘂 𝗵𝗮𝘃𝗲 𝗮 𝗰𝗹𝗲𝗮𝗿 𝗽𝗶𝗰𝘁𝘂𝗿𝗲

𝗧𝗲𝗹𝗹 𝗰𝘂𝘀𝘁𝗼𝗺𝗲𝗿𝘀 𝗮𝗻𝗱 𝘃𝗲𝗻𝗱𝗼𝗿𝘀
Proactive communication about a delay preserves trust. Silence, followed by a customer discovering it themselves, does more damage than the freeze itself.

𝗗𝗼𝗻'𝘁 𝗿𝘂𝘀𝗵 𝗮 𝗻𝗲𝘄 𝗮𝗰𝗰𝗼𝘂𝗻𝘁 𝗼𝘂𝘁 𝗼𝗳 𝗽𝗮𝗻𝗶𝗰
Opening a new account under time pressure, without understanding how it interacts with industry blacklists like MATCH, can turn one problem into two. Move fast, but not blind.

Has this happened to you? If so, how did you find resolution?

Most merchants sign their Merchant Services Agreement without fully reviewing, or fully understanding, the reserve terms buried inside it. Here's a framework for how to actually approach those terms before you sign:

𝗔𝘀𝗸 𝗳𝗼𝗿 𝗮 𝗰𝗮𝗽, 𝗻𝗼𝘁 𝗷𝘂𝘀𝘁 𝗮 𝗽𝗲𝗿𝗰𝗲𝗻𝘁𝗮𝗴𝗲
Most reserve clauses are written as an open-ended percentage of volume. Negotiating a maximum dollar cap means the reserve stops growing once it covers a reasonable worst case, instead of scaling forever alongside your sales.

𝗪𝗮𝘁𝗰𝗵 𝗳𝗼𝗿 𝗱𝗲𝗹𝗮𝘆𝗲𝗱 𝘀𝗲𝘁𝘁𝗹𝗲𝗺𝗲𝗻𝘁 𝗮𝘀 𝗮 𝘀𝘂𝗯𝘀𝘁𝗶𝘁𝘂𝘁𝗲
Some processors use delayed settlement instead of a straight reserve, holding funds longer before payout rather than withholding a percentage outright. It serves the same risk-management purpose, so the length of that delay is worth negotiating just as hard as a reserve percentage.

𝗡𝗲𝗴𝗼𝘁𝗶𝗮𝘁𝗲 𝗮 𝗿𝗲𝗹𝗲𝗮𝘀𝗲 𝘀𝗰𝗵𝗲𝗱𝘂𝗹𝗲 𝘂𝗽𝗳𝗿𝗼𝗻𝘁
Ask specifically when funds get released, and whether the reserve rolls indefinitely or converts to a capped, declining balance after a defined stretch of clean processing history.

𝗕𝘂𝗶𝗹𝗱 𝗶𝗻 𝗮 𝗿𝗲𝘃𝗶𝗲𝘄 𝗽𝗼𝗶𝗻𝘁
Request a contractual review at defined intervals tied to actual performance, chargeback ratio, processing history, so the reserve is a temporary bridge while trust gets established, not a permanent fixture.

𝗗𝗲𝗳𝗶𝗻𝗲 𝗲𝘃𝗲𝗿𝘆 𝘁𝗿𝗶𝗴𝗴𝗲𝗿 𝘄𝗶𝘁𝗵 𝘇𝗲𝗿𝗼 𝗮𝗺𝗯𝗶𝗴𝘂𝗶𝘁𝘆
Every condition for when the reserve applies, changes, or ends should be spelled out specifically, not left to the processor's discretion. This is a baseline we push for in every client contract we review.

𝗢𝗳𝗳𝗲𝗿 𝗲𝘃𝗶𝗱𝗲𝗻𝗰𝗲 𝗶𝗻𝘀𝘁𝗲𝗮𝗱 𝗼𝗳 𝗷𝘂𝘀𝘁 𝗮𝘀𝗸𝗶𝗻𝗴
Documented processing history, bank statements, or a related entity's track record does more to move a reserve decision than negotiation alone. This is literally how we got a reserve removed entirely for a client, not by arguing, but by showing the numbers.

What reserve or settlement delay issues have you run into with a processor?

Not every company needs a full-time Head of Payments. Most just need one when it actually matters.

Here's what that looks like in practice:

𝗪𝗵𝗮𝘁 𝗮 𝗳𝗿𝗮𝗰𝘁𝗶𝗼𝗻𝗮𝗹 𝗽𝗮𝘆𝗺𝗲𝗻𝘁𝘀 𝗹𝗲𝗮𝗱𝗲𝗿 𝗮𝗰𝘁𝘂𝗮𝗹𝗹𝘆 𝗱𝗼𝗲𝘀
Strategy, vendor selection, contract negotiation, ongoing risk oversight, the same decisions a full-time Head of Payments would own, just scoped to the time your business actually needs.

𝗪𝗵𝗲𝗻 𝗶𝘁 𝗮𝗰𝘁𝘂𝗮𝗹𝗹𝘆 𝗺𝗮𝗸𝗲𝘀 𝘀𝗲𝗻𝘀𝗲
Scaling into new markets, evaluating or renegotiating processors, building out payments infrastructure for the first time, situations that need real expertise at the table, but not necessarily a full-time seat at it.

𝗪𝗵𝘆 𝗻𝗼𝘁 𝗷𝘂𝘀𝘁 𝗵𝗶𝗿𝗲 𝗳𝘂𝗹𝗹-𝘁𝗶𝗺𝗲
A six-figure salary and benefits for a role that needs part-time strategic attention rarely pencils out, especially for companies not yet at the scale where payments decisions happen every single week.

𝗧𝗵𝗶𝘀 𝗶𝘀 𝗹𝗶𝘁𝗲𝗿𝗮𝗹𝗹𝘆 𝘄𝗵𝗮𝘁 𝘄𝗲'𝘃𝗲 𝗯𝗲𝗲𝗻 𝘁𝗮𝗹𝗸𝗶𝗻𝗴 𝗮𝗯𝗼𝘂𝘁
Every topic covered here over the past few weeks, underwriting, contracts, FX, chargeback thresholds, PCI compliance, is exactly the terrain a fractional payments leader is actually navigating day to day.

This is one of the ways we work with clients at Global Payments Consultants: stepping in as a fractional Head of Payments, scoped to what the business actually needs.

If you had someone dedicated to payments strategy part-time, what's the first thing you'd want them to fix?

(2/2) Yesterday I covered what changed with 3DS2. Today: how to actually get it configured right, and how to raise it with your processor.

Most merchants have 3DS2 turned on. Fewer have it turned on well:

𝗦𝗲𝗻𝗱 𝗲𝘃𝗲𝗿𝘆 𝗱𝗮𝘁𝗮 𝗲𝗹𝗲𝗺𝗲𝗻𝘁 𝘆𝗼𝘂 𝗰𝗮𝗻
Your frictionless rate lives and dies on data completeness: device fingerprint, billing and shipping match, account history, prior order history. Skipping fields to simplify integration is the most common way merchants quietly sabotage their own approval rate.

𝗔𝘀𝗸 𝘄𝗵𝗲𝘁𝗵𝗲𝗿 𝘆𝗼𝘂'𝗿𝗲 𝗱𝗲𝗳𝗮𝘂𝗹𝘁𝗲𝗱 𝗶𝗻𝘁𝗼 𝗲𝘃𝗲𝗿𝘆 𝗰𝗵𝗮𝗹𝗹𝗲𝗻𝗴𝗲
Some integrations are configured to challenge every transaction "to be safe." Ask your processor directly whether your setup is running true risk-based authentication, or defaulting to a challenge screen for everyone regardless of risk.

𝗔𝘀𝗸 𝘄𝗵𝗼 𝗼𝘄𝗻𝘀 𝘁𝗵𝗲 𝗲𝘅𝗲𝗺𝗽𝘁𝗶𝗼𝗻 𝘀𝘁𝗿𝗮𝘁𝗲𝗴𝘆
Depending on your processor and gateway, exemptions for low-value or trusted recurring transactions can route certain payments around a challenge entirely. Ask specifically whether your integration is requesting these exemptions, or leaving that option on the table.

𝗥𝗲𝘃𝗶𝗲𝘄 𝘆𝗼𝘂𝗿 𝗳𝗿𝗶𝗰𝘁𝗶𝗼𝗻𝗹𝗲𝘀𝘀 𝗿𝗮𝘁𝗲 𝗹𝗶𝗸𝗲 𝗮 𝗞𝗣𝗜
Ask your processor to show you the actual frictionless-versus-challenge breakdown on your account. 80%+ frictionless is the practical benchmark for a well-configured setup. If you're meaningfully below that, something in your data or configuration needs attention.

Where do you suspect your own checkout is quietly losing approval rate right now?

(1/2) That password screen you remember hating during checkout? It's mostly gone. Here's what replaced it, and why it matters for your approval rate.

𝟯𝗗𝗦𝟭 𝘄𝗮𝘀 𝗮 𝗰𝗼𝗻𝘃𝗲𝗿𝘀𝗶𝗼𝗻 𝗸𝗶𝗹𝗹𝗲𝗿
Static passwords, browser-only redirects, no real mobile support. Approval rates typically landed at 60-70%, with cart abandonment jumping 15-25% at the authentication step alone. Most merchants outside Europe simply turned it off.

𝟯𝗗𝗦𝟮 𝗿𝗲𝗽𝗹𝗮𝗰𝗲𝘀 𝗮 𝗽𝗼𝗽𝘂𝗽 𝘄𝗶𝘁𝗵 𝗿𝗶𝘀𝗸 𝗱𝗮𝘁𝗮
Over 100 data points get passed to the issuer instead of a handful, and most transactions now authenticate silently in the background in under two seconds. Only the genuinely risky ones get a challenge screen at all.

𝗧𝗵𝗲 𝗹𝗶𝗮𝗯𝗶𝗹𝗶𝘁𝘆 𝘀𝗵𝗶𝗳𝘁 𝗶𝘀 𝘁𝗵𝗲 𝗿𝗲𝗮𝗹 𝗽𝗿𝗶𝘇𝗲
When an issuer authenticates a transaction through 3DS2, fraud chargeback liability shifts to them, not you. With Visa and Mastercard's dispute thresholds tightening this year, that protection is worth more than it used to be.

𝗜𝗺𝗽𝗹𝗲𝗺𝗲𝗻𝘁𝗮𝘁𝗶𝗼𝗻 𝗾𝘂𝗮𝗹𝗶𝘁𝘆 𝗶𝘀 𝘁𝗵𝗲 𝗲𝗻𝘁𝗶𝗿𝗲 𝗴𝗮𝗺𝗲
The gap between a well-implemented and poorly-implemented 3DS2 setup can run 5-15 percentage points of approval rate on affected volume. Sparse data or forcing unnecessary challenges quietly erases the gains the protocol is supposed to deliver.

Is your checkout actually sending 3DS2 the data it needs, or is it running a stripped-down version that's leaving approval rate on the table?

Tomorrow: how to actually get your 3DS2 setup right, and how to raise it with your processor.

If your PCI compliance still feels like an annual checkbox, that grace period is over.

Here's what actually changed, and why it matters more for online merchants specifically:

𝗧𝗵𝗲 𝗴𝗿𝗮𝗰𝗲 𝗽𝗲𝗿𝗶𝗼𝗱 𝗲𝗻𝗱𝗲𝗱 𝗠𝗮𝗿𝗰𝗵 𝟮𝟬𝟮𝟱
Every "future-dated" requirement in PCI DSS 4.0 became mandatory as of March 31, 2025. Merchants completing their first full assessment cycle under the new standard this year no longer have transition allowances to lean on.

𝗬𝗼𝘂𝗿 𝗰𝗵𝗲𝗰𝗸𝗼𝘂𝘁 𝗽𝗮𝗴𝗲 𝗶𝘀 𝗻𝗼𝘄 𝗲𝘅𝗽𝗹𝗶𝗰𝗶𝘁𝗹𝘆 𝗶𝗻 𝘀𝗰𝗼𝗽𝗲
New requirements call for inventorying every script running on your payment page and monitoring for unauthorized changes. Even merchants on the simplest self-assessment (SAQ A) aren't automatically exempt anymore, eligibility now depends on how the page is actually built.

𝗠𝗙𝗔 𝗶𝘀𝗻'𝘁 𝗷𝘂𝘀𝘁 𝗳𝗼𝗿 𝗮𝗱𝗺𝗶𝗻𝘀 𝗮𝗻𝘆𝗺𝗼𝗿𝗲
Multi-factor authentication is now required for anyone accessing the cardholder data environment, not just remote access or administrators, internal staff and third-party vendors included.

𝗖𝗼𝗺𝗽𝗹𝗶𝗮𝗻𝗰𝗲 𝗶𝘀𝗻'𝘁 𝗮𝗻 𝗮𝗻𝗻𝘂𝗮𝗹 𝘀𝗻𝗮𝗽𝘀𝗵𝗼𝘁 𝗮𝗻𝘆𝗺𝗼𝗿𝗲
Merchants are now expected to document and confirm their compliance scope at least every 12 months, not just check a box once a year and move on.

Do you know whether your checkout page actually meets the new script-monitoring requirement?

Payment processors are quietly piloting stablecoins for real merchant settlement now, not as a crypto experiment, but as an actual payment rail. Here's what's real, and what isn't yet:

𝗪𝗵𝗮𝘁 𝗮𝗰𝘁𝘂𝗮𝗹𝗹𝘆 𝗰𝗵𝗮𝗻𝗴𝗲𝗱
The GENIUS Act gave U.S. stablecoins a real legal framework for the first time in 2025, reserve requirements, redemption standards, issuer oversight. That's what turned stablecoins from a crypto-trading tool into something payment processors are now piloting for actual settlement.

𝗧𝗵𝗲 𝗿𝗲𝗮𝗹 𝗮𝗽𝗽𝗲𝗮𝗹: 𝗺𝗶𝗻𝘂𝘁𝗲𝘀, 𝗻𝗼𝘁 𝗱𝗮𝘆𝘀
Settlement on stablecoin rails typically completes in minutes, versus one to three business days on SWIFT-led correspondent chains, and it runs 24/7 instead of banking hours only.

𝗜𝘁'𝘀 𝗻𝗼𝘁 𝗲𝗾𝘂𝗮𝗹𝗹𝘆 𝘂𝘀𝗲𝗳𝘂𝗹 𝗲𝘃𝗲𝗿𝘆𝘄𝗵𝗲𝗿𝗲
The value is corridor-specific. A payment on already-efficient banking rails may not justify switching. A payment into a market with slow, expensive correspondent banking often does.

𝗢𝗻/𝗼𝗳𝗳-𝗿𝗮𝗺𝗽 𝗳𝗿𝗶𝗰𝘁𝗶𝗼𝗻 𝗶𝘀 𝘀𝘁𝗶𝗹𝗹 𝘁𝗵𝗲 𝗿𝗲𝗮𝗹 𝗯𝗼𝘁𝘁𝗹𝗲𝗻𝗲𝗰𝗸
Moving value on-chain is fast. Converting it back to usable local currency at the other end still depends on custody relationships and compliance infrastructure that varies enormously by country.

Is this something you're actively evaluating, or does it still feel too early to matter for your business?

Mastercard's new dispute monitoring program goes live in 10 days. Most merchants have never heard of it.

Here's what's actually changing, and why chargeback management just got less forgiving:

𝗠𝗮𝘀𝘁𝗲𝗿𝗰𝗮𝗿𝗱'𝘀 𝗻𝗲𝘄 𝗽𝗿𝗼𝗴𝗿𝗮𝗺 𝘀𝘁𝗮𝗿𝘁𝘀 𝗝𝘂𝗹𝘆 𝟮𝟰
The Seller Merchant Monitoring Program (SMMP) can flag any card-not-present merchant once combined refunds and chargebacks cross 5% of transactions over a rolling 30 days, with no separate warning tier before enforcement.

𝗩𝗶𝘀𝗮'𝘀 𝘁𝗵𝗿𝗲𝘀𝗵𝗼𝗹𝗱 𝗷𝘂𝘀𝘁 𝗴𝗼𝘁 𝘁𝗶𝗴𝗵𝘁𝗲𝗿, 𝘁𝗼𝗼
Visa's VAMP "excessive" threshold dropped from 2.2% to 1.5% this April. Fines run $8 per violation, with no warning tier before penalties start.

𝗪𝗶𝗻𝗻𝗶𝗻𝗴 𝗮 𝗱𝗶𝘀𝗽𝘂𝘁𝗲 𝗱𝗼𝗲𝘀𝗻'𝘁 𝗲𝗿𝗮𝘀𝗲 𝗶𝘁 𝗳𝗿𝗼𝗺 𝘆𝗼𝘂𝗿 𝗿𝗮𝘁𝗶𝗼
Even a successful representment doesn't reduce your ratio under either program, the dispute already counted the moment it was filed. Prevention is the only lever that actually moves the number.

𝗥𝗲𝗮𝘀𝗼𝗻 𝗰𝗼𝗱𝗲𝘀 𝗱𝗲𝘁𝗲𝗿𝗺𝗶𝗻𝗲 𝘄𝗵𝗮𝘁 𝗲𝘃𝗶𝗱𝗲𝗻𝗰𝗲 𝗮𝗰𝘁𝘂𝗮𝗹𝗹𝘆 𝗺𝗮𝘁𝘁𝗲𝗿𝘀
"Item not received" needs tracking and delivery confirmation. "Fraud" needs AVS/CVV match and device data. Submitting generic evidence for the wrong reason code is one of the most common ways merchants lose winnable disputes anyway.

If your chargeback ratio crossed one of these thresholds tomorrow, would you know what to do about it?

.pro-gallery-wix-wrapper {display: block !important;} .pro-gallery-wix-wrapper .gallery-item-container {opacity: 1 !important; display: block !important;}

Subscribe to Our Blog

Join our community for monthly updates, expert insights, and practical tips delivered straight to your inbox.

Email*

All Posts
Tips
Industry News
Company News
Case Studies
Whitepapers
Articles

What Happens As Your Stripe Volume Grows

Certain volume levels quietly change how Stripe treats your account, from owner verification requirements to when negotiated pricing finally becomes available. None of these thresholds are advertised upfront.

Tips

Nick Swihart

14 hours ago1 min read

What They Say. What It Actually Means.

Payment processor language can sound routine when it isn't. Here's what three common phrases, additional documentation, a security hold, and updated risk policies, actually mean when they show up in your inbox.

Tips

Nick Swihart

2 days ago1 min read

Myth: Your Processor Is On Your Team

Merchants often assume their payment processor is a partner looking out for their interests. In reality, a processor is managing its own risk exposure, and understanding that distinction changes how you should actually plan around the relationship.

Tips

Nick Swihart

3 days ago1 min read

Before They Drop You, They Tell You

A processor rarely drops a merchant without warning first. Here are the three signs, sudden documentation requests, a growing reserve, and a suddenly quiet account rep, that most merchants miss until it's already too late.

Tips

Nick Swihart

4 days ago1 min read

It Wasn't If. It Was When.

"Why did my account get flagged? I didn't do anything wrong." Here's what's usually actually going on, especially for foreign, high-risk merchants. "Why did my account get flagged? I didn't do anything wrong." More often than not, this comes from a merchant who signed up with Stripe, PayPal, or a platform like them. There was barely any underwriting at signup, so nothing about the relationship ever forced a real risk conversation upfront. Why This Hits Foreign, High-Risk

Tips

Nick Swihart

5 days ago1 min read

Do You Even Have Your Own MID?

The Merchant Identification Number behind every processor relationship, who actually controls it, and why a business might need more than one Every processor relationship runs on a number most merchants never think about: the MID. But not everyone actually has their own. What A MID Actually Is A Merchant Identification Number is the unique number an acquiring bank assigns to identify a specific processing relationship. It's not just an account number; it's what card network

Tips

Nick Swihart

6 days ago2 min read

You Can't Evaluate A Processor From A Sales Call

A five-step framework for actually testing payment processors before committing to any of them You can't evaluate a processor from a sales call. You have to actually run volume through it. This is the final post in a three-part series on evaluating payment processing options for high-risk merchants with real structural complexity. Build In An Exit Before You Ever Test A termination-for-convenience clause is what turns signing up into actually evaluating. Without a clean way

Tips

Nick Swihart

7 days ago2 min read

Stop Choosing. Start Combining.

Why established and alternative processor types work best together, not as a single choice. Established or alternative? If you're a high-risk merchant with real structural complexity, the smartest move is combining, not choosing. This is the second post in a three-part series on evaluating payment processing options for foreign merchants in high-risk spaces with real structural complexity. Established Processors Give You Scale And Trust, Not Flexibility Best-priced acquirer

Tips

Nick Swihart

Aug 72 min read

Multiple Processor Types. One Right Combination.

A framework for high-risk merchants with multi-entity, multi-location complexity evaluating payment processing options Most foreign merchants don't actually choose a processor. They choose whichever one was easiest to set up, think Stripe, PayPal, the platforms built for fast developer access, rather than the one actually suited to their business. This is the first post in a three-part series on how to evaluate the real options, specifically for a merchant that's both classif

Tips

Nick Swihart

Aug 73 min read

2 3 4 5

Navigate the complexity of payments with confidence

Get started today.

SCHEDULE DISCOVERY CALL

RESOURCES

Empowering Smart Payments Decisions

Follow @GlobalPaymentsConsultants on Instagram

Subscribe to Our Blog

What Happens As Your Stripe Volume Grows

What They Say. What It Actually Means.

Myth: Your Processor Is On Your Team

Before They Drop You, They Tell You

It Wasn't If. It Was When.

Do You Even Have Your Own MID?

You Can't Evaluate A Processor From A Sales Call

Stop Choosing. Start Combining.

Multiple Processor Types. One Right Combination.

Navigate the complexity of payments with confidence

EXPERTISE

Cross-border Payments

Emerging Markets

Payouts/Money Transfer

Fast Payments

B2B Payments

Payment Orchestration

EXPERTISE

Merchant of Record

ISO

Embedded Payments

Payment Facilitation

Marketplace

RESOURCES

Empowering Smart Payments Decisions

Follow @GlobalPaymentsConsultants on Instagram

​

Subscribe to Our Blog

What Happens As Your Stripe Volume Grows

What They Say. What It Actually Means.

Myth: Your Processor Is On Your Team

Before They Drop You, They Tell You

It Wasn't If. It Was When.

Do You Even Have Your Own MID?

You Can't Evaluate A Processor From A Sales Call

Stop Choosing. Start Combining.

Multiple Processor Types. One Right Combination.

Navigate the complexity of payments with confidence