Announcer: Welcome to Cents Chat, the podcast where payments meet personality. From tech trends to legal twists, compliance quirks to marketplace moves, Kitty is here to keep ISVs, PayFacs, and marketplaces ahead of the curve. Get ready for insights, a few laughs, and the occasional compliance scare. Let's dive in and make payments make sense.

Kitty: When did payments become the department everyone ignores until something catches fire? Because for a long time, payments got treated like plumbing. Necessary, hidden, boring, and only worth talking about when something backed up. But that's not where we are anymore.

Now payments touches product strategy, customer experience, revenue, compliance, fraud, onboarding, data, contracts, pricing, support, and every delightful little edge case that somehow becomes a seven-person Slack thread with financial exposure.

Welcome to Cents Chat. We're back with a new format, a sharper focus, and frankly, less patience for pretending payments are simple.

I'm Kitty. I'm a world traveler who somehow landed in payments, which means I've seen complicated systems in a lot of countries and still somehow decided this industry had the most chaos per square inch.

On the show, we're going to talk about the payment problems ISVs, PayFacs, marketplaces, software platforms, fintech teams, and operators are actually dealing with. Not the glossy version. The real version.

The version where onboarding breaks, where contracts are vague, where APIs technically work but operationally betray you, where compliance shows up late and brings a flamethrower.

And because I shouldn't be trusted alone with a microphone and this much sarcasm, I'm joined today by three people who bring a very specific kind of payments damage.

First up, Jason. Jason runs a consulting practice called Payments Therapist, which is honestly the most accurate name possible because most payment problems do eventually sound like a therapy session. He's worked with some of the biggest payment processors, banks, and fintech companies. And his world is payment strategy, API integration, infrastructure, marketplaces, and the systems underneath the systems.

Jason, what should people expect from your seat at the table?

Jason: Well, Kitty, they should expect us to talk about how payments actually work underneath the sales decks. A lot of platforms think they're buying payment features. They're not. They're connecting themselves to money movement, risk controls, reporting obligations, settlement timing, customer support, revenue share mechanics, and partner dependencies.

From my perspective, the interesting part is usually not whether an API can technically move money. It's whether the platform has designed the right operating model around that integration. Because an API integration is not a strategy. It's where the strategy starts getting tested.

Kitty: Exactly. The demo works, everyone claps, then six months later, someone discovers refunds, chargebacks, reserves, onboarding exceptions, and the phrase processor limitation, which is legally recognized as a cry for help.

Next up, Steve. Steve lives in the world where payments dreams go to be operationally approved or rejected. Merchant onboarding, PayFac operations, ACH, risk, fraud, sponsor oversight, compliance execution, basically all the things that people call back office right before they become front-page problems.

Steve, what are you bringing into this?

Steve: I am bringing the operational reality check. Everyone wants faster onboarding. Everyone wants less friction. Everyone wants to approve good merchants quickly and keep the business moving. But if you make onboarding faster without understanding risk, you may just be helping bad merchants get through the front door more efficiently.

Merchant onboarding is not just a form. It is the first control point in the relationship. You need to know who the merchant is, what they sell, how they operate, where the money is going, what the risk signals look like, and how you are going to monitor them after approval. If you cannot monitor the merchant after approval, you did not finish onboarding.

Kitty: A beautiful sentence that should be printed on a coffee mug and thrown at anyone who says, "Can we just auto-approve everyone?"

And finally, Chris. Chris focuses on the legal, contractual, and compliance architecture sides of payments. Partner obligations, deal structure, regulatory ambiguity, risk allocation, and all the fun little details people ignore until a contract suddenly becomes a crime scene.

Chris, what's your role in the circus?

Chris: My role is to make sure we talk about responsibility before the problem shows up. Payments is full of shared relationships. ISVs, processors, sponsor banks, PayFacs, platforms, gateways, vendors, merchants. Everybody touches a piece of the workflow. But when something breaks, shared can quickly turn into unclear.

That is where contracts, compliance design, and operating responsibility matter. Who owns onboarding? Who owns monitoring? Who owns customer communication? Who absorbs pricing changes? Who responds when a regulator, bank, card network, or customer asks a hard question?

If nobody defines that up front, the answer usually gets discovered at the worst possible time.

Kitty: So the theme today is payments are not just a feature and the fine print has teeth.

So let's talk about why we're relaunching Cents Chat now. Because every time someone says payments has always been complicated, the industry finds a way to make the sentence age poorly.

Card brand rules keep changing. ACH rules are evolving. AI is walking into commerce like it owns the place. Agentic commerce is not just a buzzword anymore. We're moving toward a world where software agents may initiate, compare, recommend, and potentially transact on behalf of users.

Regulators are paying attention. States are getting more involved in payment economics. And ISVs are increasingly expected to own more of the customer experience, even when the risk is spread across five partners in a PDF agreement from 2021.

So the new format of Cents Chat is simple. We're going to open with something current: a trend, a rule, a regulatory fight, a weird market shift, something that tells us where payments are moving. But the heart of the show is going to be pain points. Real ISV pain points. Real platform problems. Real operational messes.

We're going to bring on guests, talk through what they ran into, what broke, what they learned, and how they fixed it, or how they're still fixing it, because this is where the useful stuff is.

Jason: Yeah, Kitty, that's the part I'm most excited about. Payments content often gets stuck on the surface. It talks about revenue share, embedded payments, conversions, frictionless experience, all the usual buzzwords, but the actual work happens underneath that.

How do you structure onboarding? How do you integrate APIs without creating a brittle mess? How do you handle exceptions? How do you design funds flow? How do you reconcile what your platform thinks happened versus what actually settled? This is where platforms either build leverage or inherit chaos.

Steve: And when we bring ISVs into the show, the point is not to embarrass anyone for having pain points. Everyone has pain points. The point is to make those problems visible so other platforms can learn from them before they trip over the same thing.

A lot of operational failures do not start as giant failures. They start as small compromises. We will review that manually for now. We will add monitoring later. We will let support handle those exceptions. We will clean up the onboarding flow after lunch.

Then the volume grows, risk grows, expectations grow, and suddenly the thing that was supposed to be temporary becomes the operating model.

Chris: And from a legal and compliance perspective, that matters because temporary processes have a way of becoming permanent evidence. The question is not just, did we solve the problem? It is also, did we understand who was responsible for the problem in the first place?

Payments is changing quickly, but platforms still need clear ownership. If you are taking on more of the payments experience, your contracts, procedures, disclosures, reporting, and partner obligations need to match what you are actually doing. Otherwise, you can end up with a business model that says one thing, a contract that says another, and an operation doing a third thing entirely.

Kitty: Which is my favorite genre of disaster: three versions of reality with no adult supervision.

And that's where listeners come in. If you're an ISV, a PayFac, a marketplace, a software platform, or honestly anyone on the payment supply chain who's stared at a problem and thought, there has to be a better way than this, we want to hear from you.

Go to centschat.com/survey. Tell us what you're dealing with. Tell us what's confusing. Tell us what's broken. Tell us what you wish someone had explained before your platform learned it the expensive way.

And if you want to be featured on a feature episode, hit the get featured button on the Cents Chat website. That's going to be a major part of the show. We want real stories from real operators solving real payments problems.

For our first current topic hit, I want to pull in the latest Cents Chat blog post from Chris: "Interchange Is Becoming a State-Level Knife Fight." First of all, excellent title. Very relaxing. Very nothing bad can happen here.

Chris, give us the high-level version. Why should platforms care about a state-level fight over interchange?

Chris: The simple version is that interchange used to feel like background payment economics. A merchant accepted a card, fees were assessed, statements arrived, everyone complained later. But state-level activity, especially around whether interchange can be charged on tax and gratuity portions of a transaction, changes the conversation.

Now platforms may need to understand transaction components much more clearly. What part of the transaction is the sale? What part is tax? What part is tip? What part is a platform fee? What happens on refunds, partial refunds, chargebacks, and settlement reporting?

This is not just a legal issue. It becomes a product issue, a pricing issue, a data issue, a reconciliation issue, and a customer support issue.

Jason: Couldn't agree more, Chris. And this is the part that platforms should start paying attention to. A lot of systems were not built to treat every component of a transaction as operationally meaningful. They may have a total amount, some metadata, maybe some reporting that works well enough until somebody asks a more specific question.

But when the payment economics become more fragmented, your data model matters. If you can't separate the sale amount, tax, tip, fees, discounts, refunds, chargebacks, and settlement outcomes very clearly, you may not be able to answer the questions your merchants are going to ask. And worse, you might not be able to implement what your partners or regulators eventually require.

Steve: From an operations standpoint, the support team is where this lands first. The merchant does not usually call and ask for a beautiful legal analysis of interchange policy. They ask, why did my fees change?

And if support cannot explain that clearly, now you have confusion, escalations, angry customers, and maybe inaccurate explanations going out into the world. That is why these changes are not just finance issues. They have to connect back to the actual operating workflow.

Kitty: So what I'm hearing is that interchange went from weird line item on a statement to possible multi-state operational knife fight, which feels very on brand for payments.

Chris: Unfortunately, yes. And the larger point is that platforms should not wait until the rules perfectly settle before asking whether their systems are ready. Legal uncertainty does not mean operational irrelevance. It usually means you should start mapping exposure, responsibilities, and flexibility now.

Kitty: That's a nice way of saying panic is not a strategy, but ignoring it is also not a strategy.

This is exactly the kind of issue we want to keep unpacking on Cents Chat. But starting with the next episode, we're going to shift into the real core of the new format: ISV pain points.

Our first guest episode is going to focus on onboarding flows. We're not naming the company today because suspense is healthy and also because I was told not to, but the problem is familiar. How do you take on an onboarding process that is too manual, too slow, too confusing, or too fragile and streamline it without accidentally creating a risk bonfire with a nice user interface?

Steve: Spot on, Kitty. I like where your head's at. That's a great first guest topic because onboarding is where a lot of payments problems begin.

When onboarding is messy, everything downstream gets harder. Risk reviews get harder, support gets harder, compliance gets harder, merchant expectations get harder to manage. But when onboarding is designed well, it can reduce friction and improve control at the same time.

That is the balance people miss. Better onboarding does not just mean faster onboarding. It means clearer data, better decisioning, cleaner workflows, and fewer surprises later.

Jason: Yes, Steve. We all know how much everyone loves a good surprise. From the integration side, onboarding is usually where the platform's product experience and the payment partner's requirements collide.

The ISV wants a clean customer journey. The processor or sponsor bank needs enough information to manage risk. The API has specific fields, states, errors, decision paths, and the user just wants to get live.

This is not just a simple form redesign problem. It's a systems design problem.

Chris: That's right, Jason. And don't forget, it's also a responsibility design problem. If a platform is collecting information, presenting terms, triggering underwriting, communicating status, or managing merchant expectations, then a platform needs to understand what role it is playing.

The onboarding flow should match the legal and compliance structure behind it. If the experience says, "We've got this," but the contract says, "Actually, someone else does," that gap can matter.

Kitty: So translation: don't let your onboarding screen write checks your compliance model can't cash.

And again, if that sounds familiar, if you have an onboarding mess, a payments integration problem, a compliance question, a risk workflow that grew horns, or a customer support issue that keeps coming back wearing different hats, go to centschat.com/survey. You can also go to the Cents Chat website and click get featured.

We're looking for ISVs and payment operators who want to talk through the real stuff. What broke, what changed, what worked, what still hurts. Other platforms can learn from it.

We're going to keep publishing written content every Thursday. So the podcast comes out every other Wednesday, and the blog keeps the conversation moving on Thursdays. The idea isn't to create random content confetti. The idea is to build a practical library for people operating inside payments.

Some topics need a conversation. Some need a written breakdown. Some need both, because apparently payments like to be complicated in multiple formats.

Jason: Yeah, Kitty, this is helpful because some issues need diagrams, details, examples, API integrations, fund flow, settlement timing, data models. All those can be really hard to unpack in short conversations. So that's where the blogs are really going to augment the podcast.

Steve: That's right, Jason. And operational topics benefit from repetition. Fraud monitoring, onboarding controls, ACH risk, merchant review. These are not one-time lessons. They are operating disciplines.

Chris: And you can never leave out compliance and contracts. The blog gives us room to explain why a rule change or legal fight matters, while the podcast lets us talk through how these issues show up in real businesses.

Kitty: Exactly. It's the same mission across formats: make payments make sense without sanding off all the weird edges.

Before we wrap, I want one sentence from each of you on what listeners should expect from this new version of Cents Chat.

Jason?

Jason: Kitty, they should expect practical conversations about how payment systems, APIs, partners, and platform strategy actually work once real money starts moving.

Kitty: Steve?

Steve: Yeah, I'd expect us to talk about operational details that decide whether a payments program scales cleanly or becomes a risk problem with revenue attached.

Kitty: Chris?

Chris: Expect us to connect payment strategy to responsibility because if ownership is unclear, the problem will eventually assign itself.

Kitty: And for me, expect direct questions, uncomfortable truths, and a strong bias toward solving the problem instead of admiring the mess.

This is Cents Chat. We're here for ISVs, PayFacs, marketplaces, fintech operators, payment teams, compliance teams, founders, and anyone else trying to build inside an industry that changes rules, pricing, technology, and expectations while everyone is still reconciling last month.

Subscribe wherever you listen, read the blog every Thursday, go to centschat.com/survey, and tell us what payments problems you want us to tackle.

And if your company has solved something painful, messy, expensive, weird, or even useful, hit the get featured button on the website. We want to hear from you because payments are not just a feature. They are where strategy meets reality, and reality has questions.

Announcer: Thanks for tuning in to Cents Chat. Got questions? Got ideas? Got payment problems keeping you up at night? We've got you covered. Head over to our website to take our quick survey. You might just land a guest spot on the pod.

Don't forget to subscribe, share this episode with your favorite ISV, and follow us on all social for the latest trends, tips, and debates. We promise no boring slideshows. At Cents Chat, we're here to make payments make sense and make it fun while we're at it. See you next time.