Ryan Dew and Kieran Draper made their case on a recent webinar titled ‘Built to Last: what card programs that scale have in common’. Three points from that conversation are worth a closer look.
The relationship continues well past launch, and so does the risk attached to it. Draper built B4B Payments' US business over six years, with steady growth in customers and volume. Partway through, circumstances at their sponsor bank, involving a different client entirely, led that bank to exit the fintech space. Draper had to migrate to a new sponsor bank while protecting a program that had done nothing wrong and continued to grow. It shows why staying closely engaged with a sponsor bank pays off well beyond launch. The programs that treat it as an active, ongoing relationship are the ones best placed to adapt when circumstances change, and to keep scaling without losing momentum.
Dew made a related point from the platform side: programs that treat a sponsor bank as a vendor, paying a fee for a defined service, are the ones most likely to be caught off guard when something changes. The ones that treat it as an ongoing partnership tend to have already asked what happens if the relationship ends, before they needed the answer.
Daily reconciliation is already required to meet scheme rules, so it isn't where programs differentiate anymore. The real gap has moved to whether reconciliation happens in real time or still waits for an end-of-day batch process. Dew said that as payment rails move toward instant settlement, on-demand reconciliation stops being optional. The complexity compounds for programs operating across multiple markets, where time zone differences alone can shift when reconciliation needs to happen. The programs handling this well are already building toward real-time reconciliation.
Dew described a program that looked like a clear success: strong funding, a compelling product, and rapid growth in its first six months. It missed its dispute resolution SLAs, the backlog grew, and the program ran into real problems within that same window. The growth didn't cause the problem. The processes needed to handle disputes at that volume hadn't been built yet, and nobody had flagged the gap before it became urgent. Growth just made it visible faster.
It's part of why Thredd works to prepare new clients for what each stage of growth requires, not just get them live. Each of these points is easy to overlook, because none of them feels urgent in the moment. The programs built to last are the ones that treat them as ongoing work, not settled questions, long after launch.
You can watch the full conversation between Ryan Dew and Kieran Draper here: watch the webinar.
Speak to our team about what operational readiness looks like for your specific card program.
