CentsChat (@centschat) header
CentsChat (@centschat) profile picture

Welcome to Cents Chat, the podcast that's changing the game for ISVs, Payment Facilitators, and Marketplaces!

St Petersburg, FL
Joined March 2020
Photo by CentsChat (@centschat)Photo by CentsChat (@centschat)Photo by CentsChat (@centschat)Photo by CentsChat (@centschat)Photo by CentsChat (@centschat)Photo by CentsChat (@centschat)
Your SaaS onboarding is beautiful. Then the merchant clicks "Accept Payments" and gets sent back to 2005. A separate portal. Another login. The same business information again. An unexplained document request. A confirmation email that says almost nothing. From the merchant's point of view, none of this is a "payments partner handoff." It's your product, and your product just got harder to use. To be clear, underwriting and verification aren't optional chores we can design away. Payments providers need information to evaluate businesses and manage risk. Some steps have to happen outside your platform, and some details may need to be confirmed directly. But necessary diligence doesn't excuse a confusing experience. The best place to start isn't a redesign. It's an inventory. What information does the merchant already provide to your software? What does the payments partner actually need? Which fields can be passed or prefilled securely, where permitted? Which documents are required for everyone, and which are requested only when a review calls for them? Then examine the part most product demos skip: what happens after "Submit." Can the merchant see whether the application is in progress, needs more information, or is approved? Can they tell when they're actually ready to accept payments? Does your support team have enough visibility to explain a delay without forwarding the same email through three departments? A redirect isn't automatically a bad experience. An embedded screen isn't automatically a good one. The real test is whether the merchant knows what's happening and what to do next. And when something goes wrong, ownership matters. Someone has to handle the exception, explain the next step, and keep the merchant from becoming the project manager of their own payments application. ISVs don't need to become underwriters to do this better. They need to treat payments onboarding as a product workflow, not a vendor link. The merchant doesn't care how many companies are involved behind the scenes. They just want to get paid without taking a field trip through the internet. #MerchantOnboarding #EmbeddedPayments #ISV #PaymentProcessing #CustomerExperience centschat.com/blog/stop-maki…
1
1
15
A Pay Now button inside your software doesn't automatically make payments embedded. If customers get sent to another portal, merchants can't see accurate payment status, and support has to refer every issue elsewhere, you've integrated a checkout. You haven't necessarily integrated the experience. There's nothing wrong with hosted payments. There is something wrong with calling a handoff seamless while the customer does all the work. Jason looks at the real test for embedded payments: what happens when the happy path breaks? #EmbeddedPayments #VerticalSaaS #ISV #PaymentProcessing #FinTech centschat.com/blog/stop-call…
1
The payment processor handles the card data. So PCI is taken care of, right? Not necessarily. ISVs can affect payment security without ever seeing a card number. And passing an assessment doesn’t mean the underlying controls will keep working all year. Kitty Wisneski and Chris join Wes Shattler of Payments Therapist to unpack scoping, shared responsibilities, missed access reviews, and the JavaScript running on payment pages. If your PCI evidence only comes together when the assessor asks for it, this one’s worth a listen. #PCIDSS #ISV #PaymentSecurity #EmbeddedPayments #Compliance youtu.be/8qquwNfcTzQ
8
If you work in payments, you've probably had this conversation at least once. "So, what exactly do you do?" And suddenly, you're trying to explain an entire industry while watching your family's eyes glaze over. In this CentsChat clip, Fredo of FT3 Global insists payments are fun, Steve Woodland admits his wife still doesn't really know what he does, and Kitty Wisneski isn't entirely sure she can explain her own job either. It's a little industry humor that anyone who's ever tried to explain payment processing at a family dinner can appreciate. So, how do YOU explain what you do in payments to people outside the industry? #Fintech #PaymentProcessing #PaymentsIndustry #EmbeddedPayments #CentsChat
2
A restaurant orders a technology platform to make running the business easier. Then an extra fee shows up on the bill. Then another. And when the owner asks how to leave, the answer is a process nobody can explain in one call. That's the uncomfortable story behind the FTC and state lawsuit filed against Toast on October 29. The complaint alleges hidden and unauthorized charges, unwanted add-ons, difficult cancellations, and other practices. Toast disputes the allegations, and the case is pending. The most interesting question isn't whether every challenged fee will ultimately be found unlawful. It's whether any software company should want to build its retention strategy around customers being confused, surprised, or afraid of the cost of leaving. The complaint alleges that restaurants were charged for subscription add-ons they didn't authorize. It also challenges a 99-cent fee imposed on certain online orders, with proceeds going to Toast rather than the restaurant. Imagine being the restaurant owner explaining a charge you didn't choose to the diner who thinks you added it. That's not just a billing issue. That's the platform spending the merchant's trust. A provider can absolutely charge for value. Hardware financing, payroll services, payment acceptance, and multi-year commitments can all make commercial sense. But a merchant should be able to answer what they agreed to, how the fees are calculated, and what happens when they want to leave. Otherwise, recurring revenue starts looking a lot like recurring resentment. For ISVs, the practical questions are simple: Can you prove an add-on was authorized? Can a merchant understand its invoice without calling support? Does the merchant know who collects a fee charged to its customers? Are termination obligations clear before signing? High retention is impressive when customers stay because the product earns its place in their business. It's much less impressive when they stay because they can't untangle the exit. You can charge avocado toast prices. Just make sure the customer ordered avocado toast, knows the price, and doesn't get burnt toast instead.
2
1
35
You saved 10 basis points on processing. Did you check what it cost you? A lower processor rate is one of those wins that's easy to celebrate. The proposal is clean, the savings calculation fits on a slide, and everybody feels good about negotiating a better deal. But a processing fee is not the same thing as a payment outcome. What if the new setup approves fewer legitimate transactions? What if failed subscriptions are harder to recover? What if finance now spends an extra day every month matching deposits to orders? The fee went down. The business may still be worse off. Here's a hypothetical example. Two processors handle a business attempting $10 million in monthly card payments. One approves 94% of attempted value at a 2.40% effective fee. The other approves 96% at 2.50%. Assuming that approval gap represents genuinely incremental successful sales, the more expensive processor produces substantially more approved payment value after fees. That isn't the same as extra profit. You still need to account for fulfillment costs, refunds, fraud and contribution margin. And the approval difference needs to be measured fairly, not cherry-picked from different customer mixes or retry definitions. But it shows why the cheapest quote isn't automatically the best deal. For merchants, the evaluation should include conversion, legitimate declines, failed-payment recovery, fraud losses and customer friction. For ISVs, add the cost of the integration, reporting quality, reconciliation, merchant support, and what happens when something breaks across hundreds of accounts. For private equity, look beyond a quick expense reduction. A rate improvement that harms conversion or retention can undermine the very value-creation plan it was supposed to support. Sometimes the cheapest processor really is the best one. If performance and service are comparable, take the savings. Just don't make the decision with a basis-point calculator alone. The better question isn't "Which processor charges less?" It's "Which processor leaves the business with the strongest risk-adjusted economics after everything else is counted?" That's a much harder question. It's also the one worth answering.
1
17
Your software can be ready for Canada long before your payments operation is. A US ISV may already have a perfectly good payments partner, but entering a new market can change the questions: local acceptance, settlement, familiar payment methods, banking and who owns the operational work. Kitty Wisneski and Steve Woodland talk with Frederik “Fredo” Pen of FT3 Global about the decisions software companies should make before promising an international launch. Watch the episode on YouTube: youtu.be/1kPJ6eoV-ns?si=kIZ7… #InternationalPayments #ISV #CrossBorderPayments #EmbeddedPayments #PaymentInfrastructure
6
Your residual report says you're making money. But are the numbers actually right? For ISVs, it's easy to look at the monthly residual payment, see revenue coming in, and assume everything is working as expected. But when was the last time you checked the math? A simple comparison between your residual report and a handful of merchant statements could reveal discrepancies in card volume, buy rates, or what you're actually being charged. In this CentsChat clip, Kitty Wisneski asks Brian Abernethy of Straata where an ISV should start when evaluating the health of its payments program. His advice? Start small. Grab a few merchant statements, compare the numbers, and see if things actually add up. Because a growing residual check doesn't necessarily mean you're getting paid correctly. #EmbeddedPayments #PaymentProcessing #VerticalSaaS #ISV #PaymentsStrategy
2
Your customer wants to cancel a subscription. Your website wants a password reset, three menus and a conversation with retention. Their banking app is already open. When cancellation is harder than disputing a charge, some customers will take the route you didn't want them to take. And that turns a preventable service issue into a payments problem. Our latest @centschat article looks at the connection between subscription UX, confusing descriptors, customer support and chargeback prevention. Sometimes the best dispute strategy starts with a better cancel button. #Chargebacks #RecurringPayments #SubscriptionBusiness #CustomerExperience #Payments centschat.com/blog/your-cust…
5
When was the last time you actually looked at your processor agreement? Not just the revenue share. The whole agreement. For ISVs, a payments deal that made sense three years ago might look very different today. Especially if your responsibilities have changed. Are you handling underwriting? KYC? Customer support? Sales? Or is your payments partner doing the heavy lifting? Because who's doing the work should have a lot to do with who's getting paid. Kitty Wisneski and Jason Kafer sit down with Brian Abernethy of Straata to discuss what makes a processor agreement healthy, and why ISVs need to understand the responsibilities behind their payments economics. The question isn't just whether you negotiated a good deal. It's whether you still have one. #EmbeddedPayments #VerticalSaaS #PaymentProcessing #ISV #PaymentsStrategy
1
23
The weirdest part of many B2B payment workflows is that the software knows almost everything about the payment right up until the moment money actually moves. The ERP knows the invoice. The procurement system knows the supplier. The AP workflow knows who approved it. The platform knows the amount, the budget, the cost center, and the reconciliation data. Then someone opens another banking portal to actually pay. That gap is starting to close. Mastercard and BMO recently launched an embedded commercial payments capability that lets eligible corporate card clients initiate and manage virtual card payments directly inside participating ERP, procurement, accounts-payable, and travel platforms. The interesting part isn't the virtual card by itself. It's where the payment is happening. Once payment execution moves inside the software workflow, the platform can potentially connect the business decision and the money movement much more tightly. Approval can sit next to payment. Spend controls can reflect the actual transaction context. Reconciliation data can be created as part of the workflow instead of reconstructed later. That's a much better experience than treating payments like the last manual step after the software has already done everything else. But embedding the payment also embeds more responsibility. Who can initiate it? Who can approve it? What happens when the payment fails? What if the supplier information changes after approval? How are exceptions handled? Does the software understand the payment status well enough to keep accounting and operations in sync? The future of embedded commercial payments isn't just about eliminating a banking portal. It's about making payment execution part of the operating system of the business. For ISVs, that can create a more valuable product and a stickier customer relationship. It also means the payment workflow has to be designed with the same discipline as the rest of the software. If your platform already runs the business, the next question may be whether it should also run more of the payment.
7
Residuals are up. Merchants are processing. So the payments program must be healthy, right? Not necessarily. Contract terms can quietly limit your options, residual math can hide discrepancies, and higher pricing can cover up merchant churn. Kitty and Jason sit down with Brian Abernethy of Straata to walk through five areas ISVs should actually measure, from processor contracts to product fit. The useful question isn't just what payments earned this month. It's what is driving that number, and whether it'll hold up. #EmbeddedPayments #ISV #PaymentProcessing #Interchange #Payments centschat.com/episodes/is-yo…
5
The most interesting Apple Pay fee isn’t the 0.15%. It’s the question of why Apple could charge it in the first place. That question is now sitting at the center of an antitrust case that could have implications well beyond Apple Pay. A federal judge recently certified a class of U.S. card issuers in a case challenging Apple Pay transaction fees and Apple’s historical restrictions on competing tap-to-pay wallets. That ruling is not a finding that Apple broke the law. It doesn’t mean the fees were unlawful. It means qualifying issuers can pursue their common claims together. But the structure behind the case should get the attention of anyone building payments inside a software platform. Payments pricing doesn’t happen in a vacuum If you control a critical interface, you may also control who can compete through it, what technical requirements they have to meet, and what commercial terms attach to access. At some point, the product architecture and the commercial model become the same conversation. That’s essentially the tension in the Apple Pay case. The plaintiffs allege Apple historically restricted competing tap-to-pay wallets from accessing the iPhone’s NFC capabilities while charging issuers transaction fees when their cards were used through Apple Pay. Apple has since opened a path for eligible third-party contactless payment apps through its NFC and Secure Element Platform. So the future looks different from the period being challenged. But that doesn’t make the underlying question any less interesting. Control creates leverage The lesson for ISVs, PayFacs, banks, and fintech platforms isn’t that charging for access is automatically a problem. It’s that control creates leverage, and leverage creates questions. Who owns the customer interface? Who controls access to the payment functionality? Can another provider realistically compete? What fees exist because someone is providing value, and what fees exist because there isn’t a practical alternative? Those questions matter when you’re negotiating with a processor. They matter when you’re choosing a wallet strategy. They matter when you’re building an embedded payments model around someone else’s platform. And they matter when today’s technical dependency becomes tomorrow’s commercial dependency. A simple tap can hide a complicated business model That’s what makes this case worth watching beyond the eventual outcome for Apple. Payments businesses tend to spend a lot of time thinking about rates, fees, contracts, and economics. But sometimes the more important question comes one layer earlier: Who controls the infrastructure that makes those economics possible? Because once one company controls a critical part of the experience, the technical architecture can start determining the negotiating leverage. The payment may still look like a simple tap. The contract and competition questions underneath it are anything but simple.
47
Apple Pay made tapping an iPhone at checkout feel simple. The economics behind that tap are now part of a much bigger antitrust fight. A federal judge has certified a class of U.S. card issuers challenging Apple Pay transaction fees and Apple's historical restrictions on competing tap-to-pay wallets. That doesn't mean Apple has been found liable. It means thousands of issuers can now pursue common claims together. Our latest CentsChat article looks past the headline and into the payments question underneath it: when a technology platform controls access to the customer interface, how much leverage should that control create over the economics of the transaction? #ApplePay #Antitrust #DigitalWallets #Payments #PaymentsInfrastructure centschat.com/blog/apple-pay…
16
The U.S. doesn’t have an instant payments problem. It might have an instant payments choice problem. FedNow is growing, and the Federal Reserve is now offering discounts designed to get more financial institutions to turn on sending. But there’s an obvious question worth asking: What problem are we still trying to solve? If a business needs to push money quickly, Visa Direct and Mastercard Move already support a wide range of payout and money-movement use cases. The Clearing House has RTP. FedNow adds another 24/7 bank-to-bank instant payment rail. That’s not necessarily a bad thing. But “instant” by itself isn’t much of a differentiator anymore. The more interesting question is what happens after an ISV has access to all of these options. A marketplace might want to push funds to a seller’s debit card. A business might want a bank-to-bank payment with immediate settlement. Another use case might depend on transaction limits, reach, cost, messaging, reconciliation, or how easily the recipient can actually receive the money. Suddenly the product decision isn’t: “Should we offer instant payments?” It’s: “Which rail should we use for this transaction?” That’s a much more interesting payments problem. Because every additional rail brings another set of rules, economics, integrations, fraud considerations, exceptions, reconciliation requirements, and support scenarios. And sending is where those differences really start to matter. Receiving money quickly is relatively easy to get excited about. Giving a customer the ability to send money irrevocably in real time means authentication, fraud controls, transaction limits, exception handling, and customer support all have to work just as quickly. Maybe FedNow isn’t solving a problem that didn’t have a solution. Maybe its bigger role is giving banks, ISVs, and platforms another way to solve it. And if that’s where instant payments are headed, the real competitive advantage may not be supporting the most rails. It may be knowing which one to use. #InstantPayments #FedNow #Payments #FinTech #EmbeddedPayments
16
CentsChat is officially going on camera.        For our first full video episode Kitty, Jason, and Chris look back at the payments stories that keep proving the same point: the sentence "this should be simple" is usually where the interesting part starts.        We get into merchant monitoring, recent FTC processor actions, agentic commerce, what we've learned from ISVs building payments into their products, and why the best CentsChat guests don't show up with a product pitch. They show up with something real to teach.        And yes, Jason is still lobbying for a daily payments podcast. Kitty is still saying no.
11
Instant payments don’t have a speed problem anymore. They have a routing, adoption, and use-case problem. The Federal Reserve is offering new FedNow discounts in 2027 to encourage more banks to enable sending. At the same time, Visa Direct and Mastercard Move already give platforms fast ways to push money to cards, accounts, and wallets, while The Clearing House RTP network is moving significant bank-to-bank volume. So is FedNow solving a problem that doesn’t exist? Our latest CentsChat article looks at the question that matters more: which instant-payment rail actually fits the job you’re trying to do? #FedNow #InstantPayments #VisaDirect #MastercardMove #PaymentsInfrastructure centschat.com/blog/instant-p…
8
The next payments stack might have an AI agent at the front, stablecoins at the back and the same old operational mess in the middle. That’s the part of the future-of-payments conversation I think we’re overlooking. We’re watching two major changes happen at roughly the same time. On the front end, AI agents are moving beyond helping people search and compare. The industry is building toward agents that can actually initiate purchases on someone’s behalf. On the back end, stablecoins are creating new ways to move and settle value, potentially faster and more programmably than traditional rails. Put those together and the transaction starts looking very different. An AI agent could decide what to buy and initiate the transaction. Existing payment infrastructure could still handle acceptance. Stablecoins could eventually play a role in settlement. Sounds incredibly modern. But here’s what didn’t disappear: Who gave the agent permission to spend? What was it allowed to buy? How does the merchant know the transaction was actually authorized? Who monitors the fraud? How does the ISV reconcile what the customer bought with how the merchant was funded? What happens when there’s a refund? A dispute? A customer who has absolutely no idea why something appeared on their statement? That’s why I think the most interesting payments opportunity isn’t necessarily at either end of this transformation. It’s in the middle. ISVs and platforms are going to have to connect increasingly intelligent commerce experiences to increasingly programmable financial infrastructure while somehow making the whole thing feel boring and reliable to the businesses using it. And “boring and reliable” is a much harder engineering and operational problem than it sounds. New rails don’t eliminate payments operations. AI doesn’t eliminate authorization. Automation doesn’t eliminate accountability. If anything, changing both ends of the transaction at the same time makes the middle more important. The future of payments may look radically different underneath. The customer is still going to expect the transaction to just work. #Payments #FinTech #EmbeddedPayments #AgenticCommerce #Stablecoins
2
1
30
The payments stack is starting to change from both ends at once. AI agents are moving closer to initiating purchases on the front end, while stablecoins are creating new possibilities for how value moves and settles on the back end. But the middle doesn't disappear. ISVs and platforms still have to manage permissions, authorization, fraud, settlement, reconciliation, refunds, disputes and support. Our latest CentsChat article looks at what happens when intelligent commerce meets programmable money - and why the software layer connecting them may become even more important. #Payments #FinTech #EmbeddedPayments #AgenticCommerce #Stablecoins centschat.com/blog/the-futur…
8
Are paper checks past their prime? Public transportation is down 90% in some cities, but how can we make it safer, and more efficient? Imposter Issues continue to skyrocket for FI's amidst the global pandemic, but what model hasn’t been greatly affected? centschat.com/