By David Baxter, CEO of Solutions by Text
- What was the strategic rationale behind acquiring Triple Play Pay (TPP), and how does it accelerate Solutions by Text’s (SBT) vision for finance-ready messaging as core infrastructure for lenders?
Lenders needed a single, compliant messaging layer that doesn’t just initiate a payment, but runs the payment across cards, ACH, and wallets inside the same trusted thread. The TPP acquisition allows us to function as a PayFac. It gives us our own payment orchestration engine (with a set of modern API’s)—including gateway, and fraud control functions—so “finance‑ready messaging” stops being a front‑end veneer and becomes real infrastructure that can own the entire journey from reminder to reconciliation.
We were already seeing rapid growth in text‑initiated payments, and substantial flows through Apple Pay and Google Pay once those wallets were enabled in FinText. The next logical step was to bring modern payment orchestration inside the same compliant messaging layer lenders already trust.
Strategically, doing this now lets SBT meet three converging pressures at once: consumer demand to “do it all in a message,” lender demand to collapse tools and vendors, and regulatory pressure to prove control over consent, communications, and payments in one place. With TPP embedded into FinText, lenders don’t have to bolt messaging onto portals and legacy processors; they can design complete, in‑thread experiences where outreach, identity, authorization, and settlement are orchestrated together, shortening time to revenue and strengthening SBT’s role as a core system in the lending stack rather than just a high‑performing engagement add‑on.
- Can you walk through how the combined SBT–TPP platform turns a simple text conversation into a frictionless, one-tap payment experience across cards, ACH, and mobile wallets like Apple Pay and Google Pay?
It can start with something as ordinary as a text reminder: a borrower gets a message in a trusted thread—often branded or verified—that clearly states what’s due and when, and presents simple options rather than a link to a portal.
From there, the combined SBT-TPP platform lets them take an immediate, no hassles payment, and then routes that payment through TPP’s orchestration layer so the actual transaction can run over cards, ACH, or a mobile wallet without leaving the conversation.
Because TPP sits behind FinText, the lender doesn’t have to set up separate experiences for each rail or wallet; the platform can surface a one‑tap Apple Pay or Google Pay button when those wallets are available, or fall back to a card or bank account flow when they’re not, with tokenization, fraud checks, and reconciliation handled behind the scenes. That’s how a simple “you have a payment due” message turns into a frictionless, one‑tap experience: the conversation stays in thread, the options are clear, and the complexity lives in the orchestration layer, not on the borrower’s shoulders.
- Lenders are struggling to reach borrowers through phone, email, and apps. At the same time, delinquency, BNPL exposure, and fraud are rising. How does unifying messaging and payments change lender economics around revenue creation, revenue protection, cost reduction, and speed of repayment?
Lenders are dealing with a very specific structural problem: most of their “successful” outreach still doesn’t translate into money moving. A borrower might get the email or see the app notification. But then there’s usually a long trail of steps—find the portal, remember the password, navigate to payments—before anything is resolved, which drags down right‑party contact, keeps call‑center volume high, slows recovery on past‑due accounts, and creates openings for fraud and confusion.
When you unify messaging and payments, you start to change those economics instead of just absorbing them. Revenue creation improves because more of your outbound volume turns into completed payments: the borrower taps a link or button in a trusted thread, chooses card, bank account, or wallet, and finishes in one motion instead of over days and channels. Revenue protection improves because the entire flow—identity checks, consent, and authorization—remains in a verified, auditable conversation, making it harder for bad actors to insert themselves and easier to prove what happened. Costs come down as you resolve more accounts without live calls, paper, or portal support tickets. And speed of repayment increases because you’re catching borrowers in the moment, on the device they already have in their hand, with a clear path from reminder to resolution instead of asking them to come back later and remember how to log in.
- From a technology standpoint, what are the key capabilities TPP brings—PCI compliant gateway, PayFac onboarding, fraud monitoring, omnichannel APIs—and how do they plug into SBT’s existing compliance and messaging layer?
TPP brings the part of the stack lenders usually have to assemble on their own: a PCI-compliant payment gateway, merchant onboarding, multi‑rail orchestration across cards and ACH, and embedded fraud and analytics that can sit underneath many different front ends. Instead of SBT handing a borrower off to a third‑party processor or portal, TPP lets us keep the entire flow—tokenization, routing, authorization, settlement, billing, and reporting—running behind the scenes while the borrower stays in a simple text or rich messaging thread.
Those capabilities plug straight into the compliance and consent layer SBT has already built for regulated messaging. We know who to contact, what they’ve agreed to, and how to present offers and reminders in a way that meets financial‑services rules; TPP then turns those compliant messages into executable payment flows through omni-channel APIs that support cards, bank debits, and wallets. Put simply, SBT owns the trusted, auditable conversation, TPP runs the money in a controlled way underneath it, and lenders get a single integrated platform instead of stitching together separate vendors for communication, compliance, and payments.
- How are lenders using messaging-led payments in the real world today—for example, in servicing, collections, or bill pay—and what results are you seeing in terms of repayment velocity and borrower engagement?
We’re seeing lenders pull messaging‑led payments into the middle of their everyday workflows, not just use it as a last‑resort channel.
In servicing and bill pay, that could be a branded text that clearly states what’s due and clearly communicates a few simple options, with the actual transaction happening in‑thread over card, ACH, or a wallet instead of in a separate portal or app. In collections, many are replacing long call sequences and letters with conversational threads that acknowledge the situation, present tailored plans, and let borrowers choose and confirm a payment arrangement in a couple of taps.
The impact shows up quickly in the numbers. Lenders using this approach through FinText have seen text-initiated payments more than double approved payment transaction volume, leading to a 136% increase in approved payment dollar volume. In pilots where Apple Pay and Google Pay were enabled alongside traditional rails, up to 75% of approved payments flowed through those wallets, which tells you borrowers will pay faster and more often when you resolve a one‑tap decision in a trusted thread instead of a multi‑step chore they have to come back to later.
- Looking ahead 12–24 months, what should lenders be doing now to prepare for messaging native payments—RCS, wallets inside messaging, and verified channels—and how will success be measured across delinquency, originations, and time to revenue?
Over the next 12–24 months, I think the most important move is to stop treating messaging as a notification layer and start treating it as the place where the relationship actually lives. That means doing the groundwork now: consolidating phone, email, and basic text into a single, compliant messaging strategy; rolling out verified, branded threads; and piloting RCS and wallets in a few targeted journeys (think renewals, past‑due accounts, or high‑value bill pay) so you can learn what works before this becomes table stakes. It also means tightening things behind the scenes: ensuring your consent records, identity checks, and payment orchestration support “see, decide, pay” flows within a message instead of forcing borrowers back into portals and apps.
If you get that right, the metrics you care about will shift. On delinquency, success will look like more accounts cured earlier in the cycle because the first or second message contains a credible, easy way to resolve the obligation—not ten touches later. In originations, it will lead to higher completion rates from approval to funding, because applicants can move from “you’re approved” to “you’re funded” without leaving the thread. And on time to revenue, you’ll measure how many days you’ve removed between sending a message and receiving a payment; lenders using messaging‑led payments today are already seeing dramatic reductions there, and as RCS, wallets inside messaging, and verified channels mature, that gap will only get smaller for the organizations that started building now.
Published in Partnership with Solutions by Text
