Michael Thaler

Ecom | Telehealth | Fast Scale
Fixing Payments 1 account at the time

[Michael Thaler @MickThaler]

If your processor disappeared for 48 hours...

Could customers still check out?
Or does revenue completely stop?

[Michael Thaler @MickThaler]

@ecompayouts @blue_ecom @Shopify @ShopifySupport @ShopifyEng @tobi “Nothing changed except more volume” is exactly what their model is built to flag. Won’t unfreeze fast. While that’s stuck, stand up a second rail and stop sending 100% of new sales through the reviewed account. That’s how you keep December from going quiet.

[Michael Thaler @MickThaler]

@ecompayouts @ecomrickys @sharell_010 Q4 doesn’t just stress ads. It stresses auth, reserves, and whoever is watching the ratio. A dedicated MID helps. It still isn’t the whole stack. If they pause that account you need checkout and rebills standing on something else the same day.

[Michael Thaler @MickThaler]

The fee conversation is incomplete without the ops layer. High-risk rate plus reserve plus a CRM that charges you again on every rebill is how the margin disappears. Compliant lane on a cheap processor only works until the volume story changes. I put telehealth accounts on a setup where routing and billing aren’t the same single point of failure.

[Michael Thaler @MickThaler]

There is another reason I like server-side payment tracking: it gives the merchant another source of truth for what actually happened financially. Browser-based attribution has become harder as privacy controls and ad blockers increase. That doesn't make browser analytics useless but it does mean merchants should be careful about treating one browser event as the definitive record of a transaction. The payment itself is an important event, and businesses need a reliable way to connect it back to the customer journey.

[Michael Thaler @MickThaler]

@GoranMetaFix Same lesson in every language. The hold isn’t random. Volume changes how they see you. Duplicating the shop helps. What actually keeps revenue up is a second processor plus billing that isn’t married to the frozen account. Don’t wait for the email tone to change.

[Michael Thaler @MickThaler]

Nothing is “similar” in the way people mean it. Shopify Payments is easy because you’re a sub-merchant. The tradeoff is you don’t control the decision. If you want that same checkout feel without being stuck, you run your own flow and route the payments underneath. Ease at signup and an exit later are two different products.

[Michael Thaler @MickThaler]

Another processor is only half of it. If checkout, subscriptions and the card file still sit on the dead account, you bought a countdown. You want routing across more than one rail and billing that doesn’t die when the first MID gets reviewed. I set that up for fast scale stores. DM if you want the short version of how we split it.

[Michael Thaler @MickThaler]

@jendor_ecompro Good outcome. Just don’t treat the lift as the fix. Same account will flag again the next time volume jumps. Get a second rail live while payouts are moving and keep the card file somewhere you can take with you. One clean review doesn’t make the setup safe.

[Michael Thaler @MickThaler]

Alerts help after the fact. What actually moves the ratio is the boring stuff: a descriptor they recognize, a refund path that takes 30 seconds, and contact details in every renewal email. If they have to hunt for support they tap dispute. Tools sit on top of that. They don’t replace it.

[Michael Thaler @MickThaler]

I think there's a useful distinction between “payment processing” and “payment operations.” Processing is getting the transaction through. Payment operations is everything the merchant has to manage around it: billing, retries, refunds, disputes, reconciliation, reporting, customer communication and the systems that react when a transaction succeeds or fails. A business can have competent processing and still have a very immature payment operation.

[Michael Thaler @MickThaler]

I find it useful to think about payment infrastructure the same way you think about any other part of a growing business: what was reasonable at one stage can become limiting later. A simple store doesn't need the same operational setup as a business with subscriptions, multiple currencies, multiple markets, several acquisition channels and substantial transaction volume. The goal isn't to make the payment stack complicated. It's to make sure the infrastructure isn't quietly becoming the bottleneck as the business changes.

[Michael Thaler @MickThaler]

@thedanielbudai

[Michael Thaler @MickThaler]

One thing I'd genuinely like to hear from merchants doing $100k+ per month: what payment problem did you only discover after you reached that level? Not the obvious “my processor froze my funds” stories. I'm more interested in the operational problems nobody warned you about: reconciliation, failed rebills, routing, reporting, customer communication, payment events or something completely different.

[Michael Thaler @MickThaler]

@MR_MRR4 Hope the processing side is prepped too. Q4 doesn’t just stress ads. It stresses auth, reserves, and whoever is watching your ratio. Scale the volume only as fast as the rails can absorb it.

[Michael Thaler @MickThaler]

@NoCodeProCode @jonathan_wilke Right direction. Just don’t treat the MID as the whole stack. If they kill that account you still need the checkout, the subscriptions, and the card file standing. Otherwise you bought a merchant account and a countdown.

[Michael Thaler @MickThaler]

@ecompayouts Yeah. The analyst never reads the email thread the way you do. They look for photo, signature, matching descriptor, easy refund path. Win or lose, the ratio still moves. That’s why the real defense is making it stupidly easier to ping you than to tap dispute.

[Michael Thaler @MickThaler]

@MerchantRiskDsk This is the one that wrecks fast-scaling brands. You think you have customers. You have tokens that belong to whoever processed last month. If you can’t take that file with you in a weekend, you don’t have a backup. You have a prayer.

[Michael Thaler @MickThaler]

@buydirectny @stripe @stripesupport This is why a single processor is an operational risk, not a vendor choice. Once they pause payouts you are negotiating from zero leverage. Get a second rail live before you need it, and keep the card data somewhere that isn’t trapped in that Stripe account.

[Michael Thaler @MickThaler]

@thesemicolonist @jonathan_wilke Ask them three things before you switch: how they treat disputes on your vertical, what happens to stored cards if they cut you, and whether payout holds are contractual or “we’ll see.” Most MoR pain shows up after month two, not on the sales call.