RESOURCES

Empowering Smart Payments Decisions

Driving growth and innovation in a rapidly evolving financial landscape.

Follow @GlobalPaymentsConsultants on Instagram

Not every chargeback is worth fighting. The decision is economic, not emotional, and getting it wrong costs you either way.

𝗙𝗶𝗴𝗵𝘁 𝗼𝗿 𝗮𝗰𝗰𝗲𝗽𝘁 𝗶𝘀 𝗺𝗮𝘁𝗵, 𝗻𝗼𝘁 𝗿𝗲𝗳𝗹𝗲𝘅
Fight when you have strong, reason-code-specific evidence and the amount is meaningful. Accept when the dispute is legitimate, your evidence is weak, or you're already close to a monitoring threshold. Fighting every dispute on principle, or refunding every one to avoid friction, both lose money in different ways.

𝗢𝗻𝗹𝘆 𝟮% 𝗲𝘃𝗲𝗿 𝗿𝗲𝗮𝗰𝗵 𝗮𝗿𝗯𝗶𝘁𝗿𝗮𝘁𝗶𝗼𝗻, 𝗮𝗻𝗱 𝘁𝗵𝗮𝘁'𝘀 𝗯𝘆 𝗱𝗲𝘀𝗶𝗴𝗻
Most disputes resolve at representment or pre-arbitration. Arbitration is the exception, the final, binding step reserved for cases both sides are willing to pay real money to settle.

𝗔𝗿𝗯𝗶𝘁𝗿𝗮𝘁𝗶𝗼𝗻 𝗶𝘀𝗻'𝘁 𝗮 𝘀𝗲𝗰𝗼𝗻𝗱 𝗰𝗵𝗮𝗻𝗰𝗲 𝘁𝗼 𝗺𝗮𝗸𝗲 𝘆𝗼𝘂𝗿 𝗰𝗮𝘀𝗲
Visa explicitly bars new evidence at this stage, everything has to have already been submitted during representment. Losing costs $600 with Visa and $575 with Mastercard, on top of the disputed amount itself. This is exactly why evidence prep matters: arbitration punishes anyone who held something back.

𝗬𝗼𝘂𝗿 𝗿𝗮𝘁𝗶𝗼 𝗺𝗮𝘁𝘁𝗲𝗿𝘀 𝗺𝗼𝗿𝗲 𝘁𝗵𝗮𝗻 𝗮𝗻𝘆 𝗼𝗻𝗲 𝗰𝗮𝘀𝗲
Every chargeback, won or lost, counts toward your dispute ratio. Cross Visa's or Mastercard's monitoring thresholds and the fines and reserves that follow dwarf what any single case was worth. Staying under that line is sometimes worth more than winning the fight in front of you.

Do you have an actual fight-or-accept framework, or does every dispute get the same reflexive response?

Manual, scrambled-together evidence wins under 20% of disputes. The same evidence, prepared in advance, wins 70 to 85%. The evidence didn't change. The timing did.

𝗘𝘃𝗶𝗱𝗲𝗻𝗰𝗲 𝗵𝗮𝘀 𝘁𝗼 𝗺𝗮𝘁𝗰𝗵 𝘁𝗵𝗲 𝗿𝗲𝗮𝘀𝗼𝗻 𝗰𝗼𝗱𝗲, 𝗻𝗼𝘁 𝗷𝘂𝘀𝘁 𝗲𝘅𝗶𝘀𝘁
Generic documentation almost always loses, even when you're factually right. "Product not received" needs delivery confirmation front and center. "Not as described" needs the actual listing and policy. Knowing which evidence maps to which reason code, before a dispute lands, is what separates a fast win from a scramble.

𝗧𝗵𝗲 𝗰𝗹𝗼𝗰𝗸 𝘀𝘁𝗮𝗿𝘁𝘀 𝘁𝗵𝗲 𝗺𝗼𝗺𝗲𝗻𝘁 𝘆𝗼𝘂'𝗿𝗲 𝗻𝗼𝘁𝗶𝗳𝗶𝗲𝗱
Response windows run as short as 7 to 30 days, and evidence you don't already have on hand takes real time to track down. Waiting until a dispute lands to start gathering it is the single biggest reason merchants lose winnable cases.

𝗦𝗽𝗲𝗲𝗱 𝗶𝘁𝘀𝗲𝗹𝗳 𝗶𝘀 𝗽𝗮𝗿𝘁 𝗼𝗳 𝘁𝗵𝗲 𝘀𝘁𝗿𝗮𝘁𝗲𝗴𝘆
Submitting within 24 to 48 hours, rather than waiting until close to the deadline, leaves real room for quality control instead of a rushed, error-prone submission. Prepared merchants aren't just collecting better evidence, they're submitting it faster too.

𝗕𝘂𝗶𝗹𝗱 𝘁𝗵𝗲 𝘁𝗲𝗺𝗽𝗹𝗮𝘁𝗲 𝗯𝗲𝗳𝗼𝗿𝗲 𝘆𝗼𝘂 𝗻𝗲𝗲𝗱 𝗶𝘁
A response written from scratch every time is slower and less consistent than one built from a reason-code-specific template, ready to fill in with the transaction's specific details the moment a dispute actually lands.

Do you have your evidence and response templates ready before a dispute lands, or does the scramble start the moment one does?

Card network rules actually require a customer to contact you first, before disputing. Most customers skip that step entirely.

𝗠𝗼𝘀𝘁 𝗰𝘂𝘀𝘁𝗼𝗺𝗲𝗿𝘀 𝗱𝗼𝗻'𝘁 𝘀𝗲𝗲 𝗮 𝗱𝗶𝗳𝗳𝗲𝗿𝗲𝗻𝗰𝗲 𝗯𝗲𝘁𝘄𝗲𝗲𝗻 𝗮 𝗿𝗲𝗳𝘂𝗻𝗱 𝗮𝗻𝗱 𝗮 𝗰𝗵𝗮𝗿𝗴𝗲𝗯𝗮𝗰𝗸
Roughly 72 percent of cardholders say they see no real difference between the two. If reaching you feels slower or harder than disputing with their bank, the bank wins by default, every time.

𝗖𝗼𝗻𝘃𝗲𝗻𝗶𝗲𝗻𝗰𝗲 𝗶𝘀 𝘁𝗵𝗲 𝗿𝗲𝗮𝗹 𝗰𝗼𝗺𝗽𝗲𝘁𝗶𝘁𝗼𝗿
More than three-quarters of customers admit they've filed a chargeback simply because it was the more convenient option, not because a refund was refused. You're not just competing with bad experiences, you're competing with the path of least resistance.

𝗥𝗲𝘀𝗽𝗼𝗻𝘀𝗲 𝘁𝗶𝗺𝗲 𝗶𝘀𝗻'𝘁 𝗮 𝗻𝗶𝗰𝗲𝘁𝘆, 𝗶𝘁'𝘀 𝗮 𝗽𝗿𝗲𝘃𝗲𝗻𝘁𝗶𝗼𝗻 𝘁𝗼𝗼𝗹
Most customers expect an email response within an hour, and a meaningful share expect it within 15 minutes. Staffing to answer calls within three rings and emails within an hour isn't a customer service benchmark, it's a chargeback prevention benchmark.

𝗔 𝗴𝗼𝗼𝗱 𝗙𝗔𝗤 𝗾𝘂𝗶𝗲𝘁𝗹𝘆 𝗱𝗼𝗲𝘀 𝘁𝗵𝗲 𝘀𝗮𝗺𝗲 𝗷𝗼𝗯
The most effective FAQs aren't generic, they're built directly from your actual chargeback reasons and your most common support questions. We've helped companies processing billions in volume do exactly this, and the difference is significant: fewer disputes, and fewer routine tickets pulling your team away from everything else.

𝗧𝗲𝘀𝘁 𝘆𝗼𝘂𝗿 𝘀𝘂𝗽𝗽𝗼𝗿𝘁 𝘀𝘆𝘀𝘁𝗲𝗺𝘀, 𝗱𝗼𝗻'𝘁 𝗷𝘂𝘀𝘁 𝗮𝘀𝘀𝘂𝗺𝗲 𝘁𝗵𝗲𝘆 𝘄𝗼𝗿𝗸
This matters most for larger operations with multiple support tiers or third-party providers. Actually testing the full path, does a ticket reach the right tier, are SLAs genuinely being met, matters as much as having the policy in place at all. A support system that looks right on paper but breaks down in practice creates the same disputes as having no system.

Have you actually tested your support systems end-to-end, or are you just assuming they work as intended?

Most merchants think about chargebacks after they happen. The real leverage is in what you do before.

𝟯𝗗𝗦𝟮 𝗮𝘂𝘁𝗵𝗲𝗻𝘁𝗶𝗰𝗮𝘁𝗶𝗼𝗻 𝘀𝗵𝗶𝗳𝘁𝘀 𝗹𝗶𝗮𝗯𝗶𝗹𝗶𝘁𝘆 𝗮𝘄𝗮𝘆 𝗳𝗿𝗼𝗺 𝘆𝗼𝘂
When properly completed, 3DS2 moves fraud liability for card-not-present transactions off the merchant. We covered the full mechanics and setup checklist in an earlier series, linked in the comments, but if you haven't implemented it, this is the single highest-leverage prevention tool available.

𝗔𝗩𝗦 𝗮𝗻𝗱 𝗖𝗩𝗩 𝗺𝗮𝘁𝗰𝗵𝗶𝗻𝗴 𝗰𝗮𝘁𝗰𝗵𝗲𝘀 𝗽𝗿𝗼𝗯𝗹𝗲𝗺𝘀 𝗯𝗲𝗳𝗼𝗿𝗲 𝘁𝗵𝗲𝘆'𝗿𝗲 𝗽𝗿𝗼𝗯𝗹𝗲𝗺𝘀
Address and card verification checks are basic, but skipping or ignoring partial matches is one of the most common preventable causes of fraud-related disputes.

𝗢𝗿𝗱𝗲𝗿 𝗰𝗼𝗻𝗳𝗶𝗿𝗺𝗮𝘁𝗶𝗼𝗻, 𝗲𝘃𝗲𝗿𝘆 𝘁𝗶𝗺𝗲
A clear receipt applies to every sale, digital or physical. If you ship a physical good, tracking and signed delivery confirmation add a second layer of evidence on top of that receipt.

𝗔 𝗰𝗹𝗲𝗮𝗿 𝗿𝗲𝗳𝘂𝗻𝗱 𝗽𝗼𝗹𝗶𝗰𝘆 𝗿𝗲𝗺𝗼𝘃𝗲𝘀 𝗮 𝗿𝗲𝗮𝘀𝗼𝗻 𝘁𝗼 𝗱𝗶𝘀𝗽𝘂𝘁𝗲
If a customer doesn't know how to get a refund, or assumes it's not possible, disputing with their bank becomes the path of least resistance. Stating the policy clearly, and making it easy to find, removes that default option.

This is the first post in a seven-part series on chargebacks: prevention, descriptors, customer care, preparation, managing an active dispute, friendly fraud, and the tools worth knowing about.

Which of these prevention levers have you actually implemented, and which have you been putting off?

A chargeback doesn't start with a call to you. It starts with a call to their bank, and by the time you find out, the money's already gone.

𝗧𝗵𝗲 𝗺𝗼𝗻𝗲𝘆 𝗺𝗼𝘃𝗲𝘀 𝗯𝗲𝗳𝗼𝗿𝗲 𝘆𝗼𝘂'𝗿𝗲 𝗲𝘃𝗲𝗻 𝘁𝗼𝗹𝗱
The moment a cardholder disputes a charge, their issuing bank reverses the funds and credits them immediately. You find out after the fact, usually through a Chargeback Debit Advice Letter from your acquirer, not before.

𝗬𝗼𝘂 𝗴𝗲𝘁 𝗮𝘀 𝗹𝗶𝘁𝘁𝗹𝗲 𝗮𝘀 𝗮 𝘄𝗲𝗲𝗸 𝘁𝗼 𝗿𝗲𝘀𝗽𝗼𝗻𝗱
If you want to fight it, "representment," submitting evidence to prove the charge was legitimate, the window is typically 7 to 30 days depending on the network and reason code. Miss it, and you automatically lose, regardless of how strong your case actually was.

𝗔 𝘄𝗶𝗻 𝗶𝘀𝗻'𝘁 𝗴𝘂𝗮𝗿𝗮𝗻𝘁𝗲𝗲𝗱, 𝗮𝗻𝗱 𝗶𝘁 𝗰𝗮𝗻 𝘀𝘁𝗶𝗹𝗹 𝗲𝘀𝗰𝗮𝗹𝗮𝘁𝗲
The issuing bank reviews your evidence and can take 30 to 75 days to rule. If neither side backs down, it escalates to arbitration, where the card network makes a final, binding decision.

𝗧𝗵𝗲 𝗱𝗶𝘀𝗽𝘂𝘁𝗲 𝘄𝗶𝗻𝗱𝗼𝘄 𝗶𝘀 𝗹𝗼𝗻𝗴𝗲𝗿 𝘁𝗵𝗮𝗻 𝗺𝗼𝘀𝘁 𝗺𝗲𝗿𝗰𝗵𝗮𝗻𝘁𝘀 𝗲𝘅𝗽𝗲𝗰𝘁
A cardholder can typically dispute a transaction up to 120 days after the original purchase, and in some cases up to 540 days. A sale from months ago can still resurface as a dispute today.

Have you ever had a chargeback catch you completely off guard, or were you ready for it?

PayPal doesn't use fixed dollar thresholds like Stripe or Square. It uses something different, and just as important to understand.

𝗧𝗵𝗲 𝗿𝗲𝘀𝗲𝗿𝘃𝗲 𝗶𝘀 𝗽𝗲𝗿𝗰𝗲𝗻𝘁𝗮𝗴𝗲-𝗯𝗮𝘀𝗲𝗱, 𝗻𝗼𝘁 𝗮 𝗼𝗻𝗲-𝘁𝗶𝗺𝗲 𝘁𝗿𝗶𝗴𝗴𝗲𝗿
PayPal's minimum reserve holds a percentage of your daily transaction volume until it reaches a set cap, or takes a one-time lump sum instead. A jumpstart reserve pulls funds from your balance immediately if PayPal decides your account needs one.

𝗛𝗼𝗹𝗱𝘀 𝗰𝗮𝗻 𝗹𝗮𝘀𝘁 𝘂𝗽 𝘁𝗼 𝟮𝟭 𝗱𝗮𝘆𝘀, 𝘁𝗿𝗶𝗴𝗴𝗲𝗿𝗲𝗱 𝗯𝘆 𝘀𝗶𝗴𝗻𝗮𝗹𝘀, 𝗻𝗼𝘁 𝗼𝗻𝗲 𝗻𝘂𝗺𝗯𝗲𝗿
New seller status, a history of disputes, or an unusually large payment spike can all trigger a hold. There's no single dollar figure that sets it off, it's a pattern-based decision.

𝗬𝗼𝘂𝗿 𝗿𝗲𝘀𝗲𝗿𝘃𝗲 𝗴𝗲𝘁𝘀 𝗿𝗲𝘃𝗶𝗲𝘄𝗲𝗱 𝗲𝘃𝗲𝗿𝘆 𝟭𝟴𝟬 𝗱𝗮𝘆𝘀
Unlike a threshold you cross once, PayPal reassesses reserves roughly every six months based on performance, disputes, and industry. It can actually improve, not just escalate.

𝗛𝗶𝗴𝗵-𝗿𝗶𝘀𝗸 𝗰𝗹𝗮𝘀𝘀𝗶𝗳𝗶𝗰𝗮𝘁𝗶𝗼𝗻 𝗰𝗵𝗮𝗻𝗴𝗲𝘀 𝘁𝗵𝗲 𝘄𝗵𝗼𝗹𝗲 𝗿𝗲𝗹𝗮𝘁𝗶𝗼𝗻𝘀𝗵𝗶𝗽
Once flagged, PayPal can cap your transaction volume, delay payouts 7 to 21 days per transaction, and in severe cases freeze or terminate the account entirely.

Did you know PayPal's reserve system worked this way, or did you assume it was just a random hold?

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.

.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

The Rate Isn't The Only Score

Comparing processors headline-to-headline on rate alone is how merchants end up locked into a bad fit. A fuller scorecard covers fee transparency, contract flexibility, reserve terms, risk appetite, and real human support.

Tips

Nick Swihart

Jul 272 min read

Recovering Revenue Starts With Better Questions

Recovering revenue from mistimed declines does not require switching processors. Four direct questions, about retry logic, account updater status, decline routing, and recovery rate reporting, surface exactly where a business stands.

Tips

Nick Swihart

Jul 252 min read

A landscape banner reading "Most Declines Aren't Declines. They're Timing," comparing a 47.6% median payment recovery rate against an 89% top-performer recovery rate.

Most Declined Payments Aren't Declines. They're Timing.

Soft declines make up 70 to 90 percent of card-not-present payment failures, and most will succeed on a well-timed retry. The gap between median recovery (47.6%) and top-performer recovery (89%) represents real, addressable revenue.

Tips

Nick Swihart

Jul 242 min read

The First Few Hours After Your Account Freezes

Your account just froze. What you do in the first few hours determines whether this is a temporary setback or a real crisis. Document, activate backup processing, and call your champion, all at the same time, not in sequence.

Tips

Nick Swihart

Jul 232 min read

The Reserve Clause Is Almost Always Negotiable

Most merchants sign their Merchant Services Agreement without fully understanding the reserve terms buried inside it. Here is a practical framework, capping the reserve, negotiating release schedules, and offering evidence instead of just asking.

Tips

Nick Swihart

Jul 212 min read

Not Every Business Needs A Full-Time Head Of Payments

Not every company needs a full-time Head of Payments. Most just need one when it actually matters, for strategy, vendor selection, contract negotiation, and risk oversight, scoped to the time a business actually needs.

Company News

Nick Swihart

Jul 202 min read

A landscape banner reading "Most Merchants Have It On. Few Have It Right," highlighting a 5 to 15 percentage point approval rate gap between well and poorly configured 3DS2 setups.

Most Merchants Have 3DS2 Turned On. Few Have It Configured Right.

Having 3DS2 turned on and having it configured well are two very different things. The gap between a well-implemented setup and a poorly-implemented one can run 5 to 15 percentage points of approval rate on the same volume.

Tips

Nick Swihart

Jul 182 min read

A landscape banner reading "That Password Screen Is Mostly Gone," comparing 3DS1's 60-70% approval rate against 3DS2's 85-95% approval rate.

That Password Screen Is Mostly Gone. Here's What Replaced It.

The password screen you remember hating during checkout is mostly gone. 3DS2 passes over 100 data points to the issuer, reaching 85-95 percent approval rates versus 60-70 percent under the old protocol, plus a real fraud liability shift.

Tips

Nick Swihart

Jul 172 min read

The PCI Compliance Grace Period Is Over. Here's What Changed.

Why PCI DSS 4.0.1 means online merchants can't treat compliance as an annual checkbox anymore If your PCI compliance still feels like something you check off once a year and forget about, that grace period has ended. As of 2026, PCI DSS 4.0.1 is the operating standard, and every requirement that was once "future-dated" is now fully enforceable. Here's what actually changed, and why it matters more for online merchants specifically. The Grace Period Ended March 2025 Every futu

Tips

Nick Swihart

Jul 162 min read

2 35 6

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

The Rate Isn't The Only Score

Recovering Revenue Starts With Better Questions

Most Declined Payments Aren't Declines. They're Timing.

The First Few Hours After Your Account Freezes

The Reserve Clause Is Almost Always Negotiable

Not Every Business Needs A Full-Time Head Of Payments

Most Merchants Have 3DS2 Turned On. Few Have It Configured Right.

That Password Screen Is Mostly Gone. Here's What Replaced It.

The PCI Compliance Grace Period Is Over. Here's What Changed.

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

The Rate Isn't The Only Score

Recovering Revenue Starts With Better Questions

Most Declined Payments Aren't Declines. They're Timing.

The First Few Hours After Your Account Freezes

The Reserve Clause Is Almost Always Negotiable

Not Every Business Needs A Full-Time Head Of Payments

Most Merchants Have 3DS2 Turned On. Few Have It Configured Right.

That Password Screen Is Mostly Gone. Here's What Replaced It.

The PCI Compliance Grace Period Is Over. Here's What Changed.

Navigate the complexity of payments with confidence