رونوشت 🔗
WEBVTT
00:00:00.719 --> 00:00:06.959
Welcome to the Leaders in Payments Podcast, where we talk to sea level leaders from across the payments landscape.
00:00:07.120 --> 00:00:14.320
We'll be discussing the products and services that impact the payment space today, as well as trends and predictions for the future of payments.
00:00:14.480 --> 00:00:18.079
We will also hear stories from our guests about their journeys to the top.
00:00:18.320 --> 00:00:20.640
Hello, everyone, and welcome to the Leaders in Payments Podcast.
00:00:20.719 --> 00:00:21.920
I'm your host, Greg Myers.
00:00:22.160 --> 00:00:26.800
Today I'm honored to have as my special guest Casey Conley, the Chief Product Officer at Payrock.
00:00:26.960 --> 00:00:29.120
So, Casey, thank you so much for being here and welcome to the show.
00:00:29.440 --> 00:00:29.839
My pleasure.
00:00:30.000 --> 00:00:31.039
Looking forward to the conversation.
00:00:31.359 --> 00:00:39.359
So, this is a special episode focused on the future of payments development and how AI and agentic development are changing the way software gets built.
00:00:39.600 --> 00:00:53.280
We'll talk about PayRock for developers, what it means to be AI native, but not AI only, and how PayRock is giving developers more speed, flexibility, and autonomy while still providing the human expertise that payments often requires.
00:00:53.520 --> 00:00:55.759
So with that, Casey, let's start with a little about you.
00:00:55.840 --> 00:00:59.759
So tell our audience a little bit about yourself, your professional journey, and your role at Payrock.
00:01:00.079 --> 00:01:00.320
Sure.
00:01:00.719 --> 00:01:01.840
A little bit about myself.
00:01:02.079 --> 00:01:07.840
Born and raised in Colorado, been in payments now for about 20 years, 25 years.
00:01:08.079 --> 00:01:09.760
Been a unique path for me.
00:01:10.000 --> 00:01:15.680
Started as an entrepreneur, kind of doing some payment consulting for PhiServe and some other folks.
00:01:15.920 --> 00:01:23.680
Took a step back out of payments, did program project management, some technology stuff for the likes of CenturyLink and Quest.
00:01:23.840 --> 00:01:37.359
And then went on a journey with Mercury Payment Systems in the integrated space through Vantiv, through WorldPay, all the way through FIS, starting as a product manager and ending as an SVP there, managing over a hundred and so products.
00:01:37.439 --> 00:01:47.439
And, you know, right about the time of COVID, I decided to join PayRock and really stand up the product function, take on a CPO role that was newly formed there.
00:01:47.599 --> 00:01:55.439
And it was just a really good time for me to take a step back from Fortune 500 and kind of get back into a little bit more.
00:01:55.599 --> 00:01:59.439
Let's get innovative, let's build, and let's get on the forefront of technology.
00:01:59.599 --> 00:02:02.959
So kind of my quick journey through the payment space.
00:02:03.200 --> 00:02:03.519
Okay.
00:02:03.760 --> 00:02:07.760
So for those who may not be familiar, can you give us a quick overview of Payrock?
00:02:08.080 --> 00:02:11.199
We're a full service processor and acquirer.
00:02:11.520 --> 00:02:22.159
We support every single solitary partner type in the ecosystem from agents, ISOs, embedded software providers, ISVs, FIs, and banks.
00:02:22.400 --> 00:02:29.520
We have a full stack platform from card not present to card present globally with a few of the acquisitions we've had.
00:02:29.599 --> 00:02:34.000
And we're really a partner first white glove human support organization.
00:02:34.159 --> 00:02:37.919
I know we're going to talk a lot about AI today, so we'll kind of get into that.
00:02:38.159 --> 00:02:44.400
But we also believe very much that people do business with people and uh technology is there to support it.
00:02:44.560 --> 00:02:46.319
So we do it all in the payment space.
00:02:46.719 --> 00:02:46.960
Okay.
00:02:47.199 --> 00:02:52.000
Well, agentic development is a term that we hear more and more.
00:02:52.159 --> 00:02:59.039
So in plain terms, what is actually changing in how software gets built and why does that matter for payments?
00:02:59.439 --> 00:03:08.560
Typically in payments, the old way, the old model developers really had to understand read docs, write integration code.
00:03:08.719 --> 00:03:14.080
They had to understand everything from authorization to settlement to money movement.
00:03:14.319 --> 00:03:25.439
And now in the new model using AI, developers can start to interact with payment providers like PayRock using human language and AI as a tool.
00:03:25.680 --> 00:03:32.479
So I want to integrate card-present payments into my solution so that I can type of language.
00:03:32.719 --> 00:03:45.599
And AI has taken some of that expertise out of the backside and the complexities of that integration and allowed them to focus more on the end result and how do they want to do it.
00:03:45.759 --> 00:03:50.960
So there's a lot there, but it kind of took the hand holding out of building out of it.
00:03:51.360 --> 00:03:58.400
The program manager, the project manager, the I need to open up access to API keys.
00:03:58.560 --> 00:04:02.960
I have to understand the code, develop to the spec, test to the spec.
00:04:03.199 --> 00:04:06.400
AI does a lot of those tasks for us now, which is a big change.
00:04:06.560 --> 00:04:06.639
Yeah.
00:04:06.879 --> 00:04:07.120
Yeah.
00:04:07.199 --> 00:04:11.599
And it's interesting because when you say AI, I mean, there's so many parts to it, right?
00:04:11.759 --> 00:04:14.879
I mean, we're talking about just the agentic development part.
00:04:15.039 --> 00:04:20.160
So just want the audience to kind of know that, you know, we're very focused on that right now.
00:04:20.399 --> 00:04:30.879
So what was the signal for you and the team at Payrock that agentic development wasn't just hype, wasn't just something that was going to go away, but a meaningful shift that you
Load full transcript
needed to build a strategy around?
00:04:31.199 --> 00:04:36.639
First and foremost, our delivery model really started to change using agentic and AI.
00:04:36.800 --> 00:04:40.959
We started to partner our product folks with our developers a lot closer.
00:04:41.120 --> 00:04:44.800
It was no longer, hey, write me a 10-page spec.
00:04:44.879 --> 00:04:53.120
Let's go to enterprise architecture and architect this entire solution and then go into a build, test, and launch phase.
00:04:53.439 --> 00:04:56.000
Internally, we partnered our product folks.
00:04:56.079 --> 00:05:15.199
We went to a two or a three-page, what are we trying to accomplish sort of model, partnered our product folks with one or two development resources and said, hey, go build, stop all the other stuff, remove all the ceremonies and everything that gets in the way, and let's just go build product.
00:05:15.279 --> 00:05:20.879
And our development cycles went way down, the quality of the product we were releasing went way up.
00:05:21.120 --> 00:05:23.519
And we were starting to see the success.
00:05:23.680 --> 00:05:48.560
And then coming from our sales channels, there were a number of moments where talking with Khan, who you've interviewed before, and a few other folks in the organization, we really started to run into these, I'll say non-technical software providers that, again, are using AI and Agentic to build new solutions, but with zero knowledge of payments, with zero knowledge of how to integrate those payments.
00:05:48.720 --> 00:05:51.839
And they were coming to us with a lot of requests.
00:05:52.079 --> 00:05:55.519
And as a product team, we started to see that shift.
00:05:55.759 --> 00:06:08.480
And that shift forced our product strategy with our internal development model and those new kinds of customers coming to us to really look at how we support integration into payments.
00:06:08.560 --> 00:06:16.399
We were putting a lot of stress on our integrations team, on our program management team, on our sales solutions teams.
00:06:16.480 --> 00:06:25.199
And we said, hey, we have to look at this a little bit different and allow these people to integrate a lot faster and not become payments experts and try to step up so quick.
00:06:25.519 --> 00:06:25.759
Okay.
00:06:25.920 --> 00:06:35.680
Well, PayRock describes when they're talking about PayRock for developers, its approach as AI native, but not AI only, which I love, by the way.
00:06:35.920 --> 00:06:38.639
So what's the distinction you're trying to make there?
00:06:38.800 --> 00:06:42.319
And why was that important to the way you designed PayRock for developers?
00:06:42.639 --> 00:06:45.600
So AI native was really about speed.
00:06:45.839 --> 00:06:53.360
And not AI only is about knowing exactly where you still want the human in that flow.
00:06:53.519 --> 00:07:00.639
We all know payments is highly regulated, money movement, disputes, chargebacks.
00:07:00.879 --> 00:07:03.439
There's a lot of things you have to know about there.
00:07:03.759 --> 00:07:10.720
And our sort of take from Payrock on it was let's build AI into the substrate of what we're doing.
00:07:10.879 --> 00:07:19.279
Let's expose different agents and jobs and tasks to help developers handle a lot of that.
00:07:19.439 --> 00:07:24.240
But let's really also understand where the human needs to make the decision.
00:07:24.480 --> 00:07:31.040
So again, this is about agentic development, and this is about agents speeding up that development.
00:07:31.279 --> 00:07:44.319
We really wanted to make sure that developers and integrators into our platform were taking the time to really focus on the problems they wanted to solve and really take the machine readable.
00:07:44.480 --> 00:07:46.000
How do I understand the spec?
00:07:46.160 --> 00:07:47.040
How do I do this?
00:07:47.199 --> 00:07:48.079
How do I do that?
00:07:48.240 --> 00:07:52.480
The simple thing that everyone needs to do out of the equation for them.
00:07:52.720 --> 00:08:12.399
So really taking that developer, helping them understand where their time and their effort needs to be focused, and taking a lot of those automated, repetitive, spec understanding sort of guide rail tasks off of them and allowing, you know, agentic development to kind of handle that for them.
00:08:12.560 --> 00:08:17.040
And as I said earlier in the first question, we're a very human first company.
00:08:17.199 --> 00:08:18.399
It's in our DNA.
00:08:18.480 --> 00:08:25.040
We don't want partners to come to our website, not be engaged with our folks, but we want to help people solve their problems.
00:08:25.199 --> 00:08:30.160
We don't want to teach them about payments and help them understand how to integrate to us.
00:08:30.319 --> 00:08:33.120
That can all be handled by a gentic code.
00:08:33.200 --> 00:08:43.200
And we want to be, you know, their trusted partner who helps them differentiate their solution, helps them build new products that solve other people's problems.
00:08:43.440 --> 00:08:50.240
And really where we are with AI native and not AI only is understanding where those lines are.
00:08:50.480 --> 00:08:50.639
Okay.
00:08:50.879 --> 00:08:55.759
Well, as you mentioned, a lot of companies are adding AI features to existing products.
00:08:56.080 --> 00:09:03.120
In your opinion, what does it mean to actually design developer experience for agenc development from the ground up?
00:09:03.679 --> 00:09:06.879
Most companies retrofit AI.
00:09:06.960 --> 00:09:10.799
They put a chat bot on top of their existing doc services.
00:09:11.039 --> 00:09:15.120
They put a chat bot on their developer integration site.
00:09:15.200 --> 00:09:18.960
So ask questions, get answers, point them at those specs.
00:09:19.200 --> 00:09:21.759
We took a different approach at Payrock.
00:09:21.919 --> 00:09:25.360
We said, hey, let's build a dedicated entry point, payrock.ai.
00:09:25.759 --> 00:09:33.440
And rather than build a page
buried in marketing and everywhere else, let's put that page front and center.
00:09:33.679 --> 00:09:40.159
And then we use AI within our developer experience to developer comes in.
00:09:40.399 --> 00:09:42.000
I want to X.
00:09:42.240 --> 00:09:46.320
I want to integrate card present payments into my existing solution.
00:09:46.559 --> 00:09:48.480
AI will build that solution for them.
00:09:48.559 --> 00:09:52.159
It'll point them at all the right agents and all the right documentation.
00:09:52.320 --> 00:09:57.039
And then it feeds directly into whatever tool of their choice is.
00:09:57.200 --> 00:09:58.559
So we use Claude.
00:09:58.720 --> 00:10:01.360
I mean, there's all kinds of development tools out there.
00:10:01.600 --> 00:10:06.480
We built our platform and the capability for those agents to work with the tool of their choice.
00:10:06.639 --> 00:10:08.960
They don't have to understand a tool.
00:10:09.039 --> 00:10:11.519
They don't have to change their development methodology.
00:10:11.759 --> 00:10:18.720
And we really built our developer experience around agentic, agentic coding, like you said, from the ground up.
00:10:18.879 --> 00:10:26.960
We didn't layer it on top of what we already have and fall back on our old ways, processes, and policies.
00:10:27.279 --> 00:10:27.600
Okay.
00:10:27.840 --> 00:10:33.360
One of the big value props or promises here is really to build payments in minutes and not months.
00:10:33.679 --> 00:10:37.279
And payments integration, I mean, you've been in this industry a long time as well.
00:10:37.440 --> 00:10:42.159
Historically, these integrations have been very complex and pretty people dependent.
00:10:42.399 --> 00:10:47.840
So what has changed that makes that kind of speed, build payments in minutes even possible?
00:10:48.159 --> 00:10:52.159
It's the tools, it's the agents, it's the way we wrap stuff around it.
00:10:52.480 --> 00:10:55.840
Agentic Commerce, I want to hit on this a little bit.
00:10:56.000 --> 00:10:57.919
It's kind of the Wild West right now.
00:10:58.159 --> 00:11:07.519
There's all sorts of different standards, different security models, different where a human's in the loop, where a human isn't in the loop.
00:11:07.759 --> 00:11:19.360
Some companies 100% rely on AI and agentic code, which I firmly believe can over-engineer and make things a lot more complex than they did.
00:11:19.600 --> 00:11:25.039
We kind of took a different approach and we said, hey, let's take this from the integration side of the house.
00:11:25.200 --> 00:11:33.840
We believe our partners, our software providers that are building payments into their platform, they understand their market and the problems they're trying to solve.
00:11:34.000 --> 00:11:39.120
Let's take the integration to payments complexity out of that.
00:11:39.279 --> 00:11:41.039
You're spot on in what you said.
00:11:41.200 --> 00:11:43.200
And it makes me laugh a little bit.
00:11:43.440 --> 00:11:51.200
We used to
talk about in board meetings and with our ISV leaders, we've just signed a new ISV or a new partner.
00:11:51.600 --> 00:11:58.559
We won't have them integrated and making revenue for another four to six months.
00:11:58.720 --> 00:12:00.879
It's going to take us three months to integrate.
00:12:01.039 --> 00:12:06.799
It's going to take us another month or two to really start to ramp up and test all that.
00:12:06.960 --> 00:12:08.960
And then they'll start going into it.
00:12:09.120 --> 00:12:15.519
So, like I said, by taking the approach of let's solve that integration problem, let's solve that speed to revenue problem.
00:12:15.759 --> 00:12:21.840
ISBs, all of them, agents and ISOs, they see payments as a big revenue generator for them as well.
00:12:21.919 --> 00:12:24.480
It's software and payment revenue.
00:12:24.639 --> 00:12:30.639
And like I said, we took the approach of everything that can be automated, let's automate.
00:12:30.879 --> 00:12:36.399
So we automated getting test keys for them to start testing their code.
00:12:36.559 --> 00:12:41.840
We automated solutioning with human language of here are the things I'm trying to do.
00:12:42.000 --> 00:12:43.840
And we will actually build that solution.
00:12:43.919 --> 00:12:48.960
I want to use a hosted payment page with Google and Apple Pay to put on my website.
00:12:49.120 --> 00:12:53.759
Here's the solution, here's the agents you need to look at, here's how you plug those into your code.
00:12:54.000 --> 00:12:55.919
Same with CardPresent and everything else.
00:12:56.080 --> 00:13:02.879
So we kind of made the integration portion of that, the speed to revenue portion of that, the core of what we were doing.
00:13:02.960 --> 00:13:04.879
And like I said, took a different angle on it.
00:13:04.960 --> 00:13:10.159
And then with that, by using a Gentic development, our developers can come back at any time.
00:13:10.240 --> 00:13:16.960
And they can say, I want to add, and I keep going to mobile wallets and APMs and all that, because they we get a lot of requests for those.
00:13:17.120 --> 00:13:19.840
But hey, I've done my standard payment integration.
00:13:20.000 --> 00:13:24.879
I'm getting a ton of requests for Apple Pay on my device or hosted checkout page.
00:13:25.039 --> 00:13:26.480
I want to add that to my solution.
00:13:26.559 --> 00:13:28.159
And they have their developer sandbox.
00:13:28.240 --> 00:13:29.440
They can go back at any time.
00:13:29.600 --> 00:13:33.759
It'll point them at the right jobs, it'll point them at the right agents.
00:13:33.919 --> 00:13:42.720
And then those agents integrated with their agentic coding are able to add those without fully understanding that spec and everything on the backside.
00:13:42.960 --> 00:13:43.120
Okay.
00:13:43.279 --> 00:14:03.120
So I think keeping that conversation going, if I'm a developer or increasingly, as you said, like an AI agent working with a developer, what does that experience building with Payrock
look like when you kind of get into like the discovery and documentation and sandboxes and testing and launch and all of those kind of gory details of getting a product to market?
00:14:03.200 --> 00:14:04.159
What does that start to look like?
00:14:04.240 --> 00:14:05.759
What's that experience with payrock now?
00:14:06.000 --> 00:14:07.440
It actually gets really easy.
00:14:07.600 --> 00:14:08.159
It's funny.
00:14:08.320 --> 00:14:12.080
We've had a number of partners start to integrate and play with it.
00:14:12.240 --> 00:14:18.799
We've had our developer integrations team that followed the old traditional way, the head of that.
00:14:19.039 --> 00:14:22.080
He was the first one to pilot our developer experience.
00:14:22.320 --> 00:14:25.600
So he went to developers.payrock.com.
00:14:25.679 --> 00:14:31.360
He said, I want to start taking payments on my website with custom hosted fields.
00:14:31.519 --> 00:14:41.840
And he talked in human language to our agent on the website that spit out a plan for him on here's the agents you need to do this.
00:14:42.000 --> 00:14:48.480
Here's the specs that those are pointed at, and here's what you need to load in your agentic coding tool of choice.
00:14:48.639 --> 00:14:59.360
He was able to take those and load them into our developer portal where he gets automatically his API test keys, his integration plan, his testing plan.
00:14:59.679 --> 00:15:05.360
And he's able to integrate that into his solution and test it against those test keys.
00:15:05.679 --> 00:15:15.600
We've had customers and internal folks that have been able to go through that entire process and take their first payment within 35 minutes of interacting with our website.
00:15:15.679 --> 00:15:19.600
And we're talking about time frames that used to be three and a half or four months.
00:15:19.919 --> 00:15:20.559
It's crazy.
00:15:20.720 --> 00:15:20.960
Yeah.
00:15:21.279 --> 00:15:25.679
So another major theme that we want to touch on is more ways to build.
00:15:25.840 --> 00:15:28.399
So you're building in this developer flexibility.
00:15:28.559 --> 00:15:30.000
So why is that so important?
00:15:30.080 --> 00:15:34.960
And how different might the right integration path look from one software company to another?
00:15:35.279 --> 00:15:41.200
You know, ISVs and software providers and vertical SaaS providers embed payments in so many different ways.
00:15:41.519 --> 00:15:49.840
We find ourselves consulting with these companies all the time, and they all want to find different unique ways to do things.
00:15:50.000 --> 00:16:01.759
I mean, even at PayRock, as the chief product officer, I laugh, but I have to support traditional agent and ISO distribution with products and services for them to sell and take to market.
00:16:02.000 --> 00:16:08.080
We have to support our FIs with different POS solutions and different verticalized software.
00:16:08.240 --> 00:16:12.960
And then we have our embedded channel as well that go to
market in a million different ways.
00:16:13.200 --> 00:16:19.360
Some embedded software providers, they want to be able to refer and they don't want to know anything about payments.
00:16:19.519 --> 00:16:24.080
They want to integrate to us, they want to be able to refer those merchant accounts when they sell their sale.
00:16:24.159 --> 00:16:26.960
They want us to handle that sale for them and sell it.
00:16:27.200 --> 00:16:30.639
And others want to own more of that ecosystem.
00:16:30.720 --> 00:16:38.480
They want to embed the sign-up process, the contracting process, and they want to control the experience beginning to end.
00:16:38.720 --> 00:16:44.240
So what we've really kind of standardized around PayRock is there is no one way.
00:16:44.399 --> 00:16:45.919
There is no right way.
00:16:46.240 --> 00:16:52.879
So we've built our tools and we've built our portal really around the right path depends on who we're talking to.
00:16:53.039 --> 00:16:55.039
Are we talking to somebody in unattended?
00:16:55.200 --> 00:17:03.919
Are we talking to somebody in unattended EV charging versus unattended retail or concession stands or Coke machines?
00:17:04.000 --> 00:17:07.039
I mean, all of them have different ways of doing things.
00:17:07.200 --> 00:17:17.119
And as we've talked about AI and AI first and AI native and all of that as well, the honest truth is we believe that people should be making those decisions.
00:17:17.200 --> 00:17:20.720
And we need to support all of those different models that do it.
00:17:20.880 --> 00:17:23.519
And that's what we want our developers spending their time on.
00:17:23.599 --> 00:17:29.680
And that's what we want to spend our time on is helping our developers solve those problems, not the integration side of it.
00:17:29.839 --> 00:17:40.559
So that's why we've kind of headed down this developer experience path, this agentic AI modeling sort of methodology is that one size doesn't fit all.
00:17:40.720 --> 00:17:41.279
It just doesn't.
00:17:41.599 --> 00:17:41.759
Okay.
00:17:42.000 --> 00:17:46.240
Well, there's this balance between developer autonomy and human expertise.
00:17:46.400 --> 00:17:48.240
I mean, we've talked about that a little bit.
00:17:48.480 --> 00:17:52.400
So where does the self-service, you know, where does that make the biggest difference?
00:17:52.480 --> 00:17:56.319
And where do you believe the human touch still really matters when it comes to payments?
00:17:56.640 --> 00:18:11.759
Self-service wins where things are mechanical, they're repetitive, sandbox provisioning, boilerplate, like straightforward auth, straightforward capture, support docs, and questions around those.
00:18:12.079 --> 00:18:14.799
Human expertise still matters in the middle.
00:18:14.960 --> 00:18:20.720
I mean, the truth is in payments, you make a mistake, there are big ramifications.
00:18:20.880 --> 00:18:24.559
I mean, you're in money movement, you're in compliance, you're in risk.
00:18:24.720 --> 00:18:29.759
I mean, one of the big things we're big at payrock is our consumer choice and our surcharging products.
00:18:29.839 --> 00:18:33.119
And there's a lot of compliance around all of those.
00:18:33.279 --> 00:18:34.640
Those decisions matter.
00:18:34.880 --> 00:18:37.200
Agentic coding and all of that.
00:18:37.359 --> 00:18:41.440
It can integrate those things, but like I said, there's certain compliance things.
00:18:41.519 --> 00:18:43.920
It becomes a business risk if I do it wrong.
00:18:44.160 --> 00:18:48.319
That's where the human expertise and the human portion of it comes in.
00:18:48.559 --> 00:18:59.119
And if you were to go out and play with our dev site, our new developer portal, I think you'd find that that standard, repetitive, mechanical things that used to take people forever to do.
00:18:59.359 --> 00:19:03.440
Read those specs, understand those specs, put those solutions together.
00:19:03.599 --> 00:19:04.720
That's what we automated.
00:19:04.960 --> 00:19:15.759
And finding that balance between compliance, money movement, business risk in my solution and integrating into payments is really where that human element still comes in.
00:19:15.920 --> 00:19:36.000
And we find even in the development that we do, that's where my product team and our development organization really spends the majority of their time talking about how to solve those problems, make them reliable, take the risk out of those processes, not the integration, not the take a payment, not the auth a standard transaction.
00:19:36.160 --> 00:19:39.039
So that's that fine line between human and AI.
00:19:39.200 --> 00:19:41.599
I mean, AI is a tool, it should be used as a tool.
00:19:41.839 --> 00:19:44.160
And we've had our instances and everyone will.
00:19:44.319 --> 00:19:52.799
It's still new where we've relied too heavy and we've had other people rely too heavy on it only to find out that yeah, we weren't compliant and we did something wrong.
00:19:52.960 --> 00:19:57.519
So finding that balance is is critical for everybody in the payment space.
00:19:57.759 --> 00:19:58.079
Okay.
00:19:58.319 --> 00:20:05.279
So let's talk about vertical SaaS companies a little bit and let's go to sort of the payoff, is what I'm going to call it.
00:20:05.519 --> 00:20:16.160
So if you're a CTO or a product leader at a vertical SaaS company, how does improving the developer experience translate beyond just the engineering, just getting the product to market?
00:20:16.319 --> 00:20:18.400
Like, is it faster time to market?
00:20:18.480 --> 00:20:20.160
Is it product differentiation?
00:20:20.400 --> 00:20:22.480
Is it ultimately the monetization?
00:20:22.640 --> 00:20:27.680
Maybe talk about the payoff, the real value beyond just the engineering part of this.
00:20:27.920 --> 00:20:29.359
Yeah, a number of things here.
00:20:29.519 --> 00:20:35.680
I mean, faster integration to a payment company obviously converts directly into faster time to revenue.
00:20:35.839 --> 00:20:42.640
The less I'm spending focusing on integrating to my payment provider, integrating payments in my flow.
00:20:42.799 --> 00:20:54.079
I mean, if we were three to six months, as we've talked about, down to a week, that's faster time to revenue, getting my residuals, I'm getting my commissions, I'm getting my Rev share, a lot, lot quicker.
00:20:54.240 --> 00:20:59.200
It's also a materially better developer experience for the developers that are doing it.
00:20:59.440 --> 00:21:08.079
ISBs can actually talk to their customers about capabilities that we provide and add them at a faster scale.
00:21:08.240 --> 00:21:11.279
So they're solving problems for customers as well.
00:21:11.440 --> 00:21:26.000
If there's a capability we provide in embedded lending or finance or something that one of their customers wants or they want to embed in their solution, they can do that a lot faster and get faster time to revenue there as well.
00:21:26.240 --> 00:21:32.799
And then really the big one for me, and we see this a lot too, is it like the payments integration is no longer a distraction.
00:21:32.960 --> 00:21:34.720
I've been in this business for 20, 25 years.
00:21:34.799 --> 00:21:37.440
I've been in integrated payments now for 15 years.
00:21:37.759 --> 00:21:51.759
How many times I had the conversation with an integrated software provider about I can't start that or put that on my roadmap for another three months because we have five other things we have to do.
00:21:52.000 --> 00:21:56.240
It really allows that integrated provider and that software person to say, you know what?
00:21:56.480 --> 00:21:59.759
95% of my time is serving my customers.
00:22:00.319 --> 00:22:12.400
And solving their problems and differentiating my product, not I need to carve out a quarter of my developers' time to learn, integrate, and test our payments integration.
00:22:12.480 --> 00:22:15.680
And I believe that's a huge benefit for those software providers.
00:22:16.000 --> 00:22:16.160
Okay.
00:22:16.319 --> 00:22:21.680
Well, looking ahead a few years, how do you see agenda development changing payments more broadly?
00:22:21.839 --> 00:22:22.799
So that's the first part.
00:22:22.880 --> 00:22:27.599
And then what should software companies and payments companies be preparing for right now?
00:22:28.240 --> 00:22:29.920
This is a tough question for me.
00:22:30.160 --> 00:22:42.319
Near-term code, test generation, everything we've talked about really accelerating software development and being able to build in faster timelines is probably the near term.
00:22:42.720 --> 00:23:00.079
Medium term, I see platforms starting to evolve to as your partner, and this just isn't in payments, but as your partners or your integrated partners, I mean, in the restaurant space, everybody uses DoorDash and all the other different integrations.
00:23:00.240 --> 00:23:10.799
So medium term, you start to get into how do I change that integration and take advantage of the new features those companies are releasing to me in a timely fashion and automate all of that.
00:23:11.039 --> 00:23:19.519
And then longer term and more a broader bet, which between me and you and your audience and who we're listening to, I don't know when that time comes.
00:23:19.680 --> 00:23:21.839
I mean, everything's so accelerating right now.
00:23:22.160 --> 00:23:26.559
But I think AIA agents really do become a second user.
00:23:27.039 --> 00:23:47.039
You start to automate shopping flows and buying flows and payment flows for individuals, and those agents that you build into your software really start to be self-evolving and taking advantage of new functionality without developers even really getting into the mix and being involved.
00:23:47.119 --> 00:23:58.319
So I know that's a longer-term sort of bet and to be prepared for, but we at Payrock looked at AI agents and agentic agents as another user.
00:23:58.559 --> 00:24:01.200
Longer term, they could be the standard user.
00:24:01.680 --> 00:24:06.079
It is going to be interesting times in payments in the next few years.
00:24:06.160 --> 00:24:10.880
And I think we always say that in payments, like it seems like we always have for at least the last 10 or 15 years.
00:24:11.039 --> 00:24:16.079
But I truly think with agents potentially taking over so much of the buying, it's going to be interesting.
00:24:16.240 --> 00:24:22.480
So we're not really talking today about what AI can do and all of that type of stuff.
00:24:22.799 --> 00:24:27.519
But longer term, I think AI and those agents really will become the customer.
00:24:27.599 --> 00:24:28.079
And you're right.
00:24:28.160 --> 00:24:32.000
For 20 years we've been talking about all the change in payments.
00:24:32.240 --> 00:24:35.119
And it's going to continue and it's going to accelerate for sure.
00:24:35.359 --> 00:24:36.240
Yeah, absolutely.
00:24:36.400 --> 00:24:37.839
So one final question.
00:24:38.000 --> 00:24:47.119
So if a developer or an ISV listening today wanted to start building with payrock, what's the one thing you'd want them to know before they start?
00:24:47.359 --> 00:24:50.960
Start at payrock.ai and docs.payrock.com.
00:24:51.279 --> 00:24:57.119
All the skills and all the tools and all of it is there and it's available for you.
00:24:57.359 --> 00:24:59.599
Fast doesn't always mean unsupervised.
00:24:59.680 --> 00:25:01.359
I really think that's a big thing.
00:25:01.599 --> 00:25:11.119
The self-service speed is real, but the human expertise and the human components are still really, really part of the equation and actually needed.
00:25:11.279 --> 00:25:22.799
And last but not least, I think Payrock, honestly, we've moved from over the last six to 12 months, Payrock's really moved from just a processor to we're a fintech.
00:25:23.039 --> 00:25:28.160
We're getting into this AI agentic coding game in a pretty big way.
00:25:28.319 --> 00:25:30.480
And we're here and we're excited about it.
00:25:30.640 --> 00:25:32.160
So I think that's my closing.
00:25:32.400 --> 00:25:32.720
Okay.
00:25:32.880 --> 00:25:35.680
Well, Casey, I think that's a great way to wrap up the show.
00:25:35.759 --> 00:25:37.200
I know your time's very valuable.
00:25:37.279 --> 00:25:38.960
So thank you so much for being on today.
00:25:39.039 --> 00:25:39.839
I really appreciate it.
00:25:40.000 --> 00:25:40.400
Thank you.
00:25:40.559 --> 00:25:41.519
I appreciate it as well.
00:25:41.680 --> 00:25:44.400
And finally, to all you listeners out there, I thank you for your time as well.
00:25:44.480 --> 00:25:57.119
And until the next story.com, where you can subscribe to the show and where you'll find our show notes.
00:25:57.359 --> 00:26:01.279
If you enjoyed listening, please share on your social channels as well.