You got paid once for building your client's ecommerce checkout.
Everyone else has been getting paid every month since.

That's okay — you didn't know. Nobody had a reason to tell you.

Somewhere out there is an ecommerce store you built. Then another, and another — probably more than you'd bother counting. Every one of them is taking card payments right now, and has been every day since you launched it. Brian explains the whole thing on camera just below — or keep reading.

On every transaction it clears, a list of people get paid — the processor, the ISO, the acquiring bank, the card network, the issuer, and the rep who sold your client the account years ago. Every month, automatically, for the life of the account.

The agency that built the thing is the only name not on that list.

Conduit puts your agency's name there instead. Same work, same clients, nothing new to sell — and revenue that arrives monthly and doesn't stop when the project does.

Book 15 minutes with Brian Nothing to buy · nothing to sign

Rather watch than read? Brian explains it in a few minutes — no signup, no gate.

For web developers, ecommerce shops, marketing agencies, consultants and coaches who build client checkouts.

An ecommerce store you builtLaunched Feb 2023

Your invoice to the client Paid once, in 2023

Months it's been taking cards since 41

Recurring payments the processor has made on it 41

How many of those came to you 0

And the next ecommerce store you build Starts the same way

Illustrative, not a quote. Bring a real client list to the call and Brian will run yours — we won't put a dollar figure in front of you that hasn't been checked against an actual statement.

Hear it from him

Would it be a bad idea to hear it from him before you decide?

You're probably assuming this is a payments guy trying to get you on a call. Fair read — it's what most pages like this are. So here's the version where you don't have to talk to anyone.

No email gate, no signup. If it's not for you, close the tab and we never know you were here.

Video slot — paste Brian's embed here

Brian Manning · no signup, no email gate

Book 15 minutes with Brian

The whole thing

No mystery. Here it is in one paragraph.

Card processing pays a recurring share of revenue to whoever is credited with bringing in the merchant. That isn't a promotion or an incentive program — it's the oldest arrangement in the industry, and it pays out monthly for the life of the account. Conduit changes whose name sits in that field, handles the switch end to end, and pays the agency every month the store keeps taking orders.

How it works now

What it could be

You invoice the build once

You're paid every month it runs

Your revenue ends at launch

It runs as long as the store does

Back to zero every January

Stacks with every ecommerce store you add

You do the work, someone else is paid on it

You do the same work, and you're paid on it

None of this is new. Shopify, Square and Toast all make more money moving payments than selling software. The only unusual part is who got left out — the platforms got in, and agencies doing the identical work never did.

Sixty months. Not one of them goes dark.

Each square is one month. The brighter it gets, the more accounts paid you that month — because the ones from last year never stopped.

Year 1

Year 2

Year 3

Year 4

Year 5

Year one · three buildsYear five · still counting

636 separate payments, from work you did once and then moved on from.

Where that number comes from: three to four new builds a year, every account still running. Real life is messier — merchants close, some get bought, a few switch. Your pace is your pace. It's arithmetic, not a projection, and there isn't a dollar figure anywhere in it on purpose.

That's not a bonus. That's a second business hiding inside the one you already run.

The closest thing in your world is a retainer — except nobody has to service it, and it doesn't end when the relationship cools. You don't work harder in year five. You just stopped giving it away in year one.

Which is also why it isn't only about the month. An agency with recurring revenue sells for a multiple. A project shop sells for whatever's in the pipeline that quarter. Every store you add moves you further from one and closer to the other.

You're already doing this work. You picked the gateway. You wired the API. You tested the checkout at midnight before launch, and you're still the one they call when a card declines on a Saturday.

And it doesn't stop — not when the project ends, not when the retainer ends, not ever. None of them has seen a line of your code.

You're already doing the work. Shouldn't you be getting paid for the work you're already doing?

Here's what we're actually competing with, and it isn't another payments company.

It's what already happens. You tell the client to go get a Stripe account, they come back with credentials, you wire it up, you invoice, you move on. That works. Nothing breaks. Nobody complains.

Which makes it very hard to beat, because doing nothing is free, requires no decision, and can never turn out to have been the wrong call.

Most agencies who read this page will do nothing, and it won't be because they didn't believe it. It'll be because Tuesday went the way Tuesday always goes.

Is it you?

This works for about five thousand shops in the country.

Published counts don't agree — Census-based figures put US advertising establishments near 15,000, industry analyses put marketing agencies around 41,000, and Promethean Research counts 71,000 digital agencies across North America. We work from the middle.

~41,000US marketing and web agencies

~12,000that touch a checkout at all

~5,000agencies, consultants and dev shops shipping ecommerce regularly, with clients they still talk to after launch

The first number is published. The second two are our arithmetic, not a census. We'd rather show you the math than quote a number we can't defend.

Ruled out: one ecommerce build a year, payments handed off and never touched again, or reselling a closed platform that locks the processor — GoHighLevel, ServiceTitan and similar.

Everything after this assumes you're one of the five thousand.

Questions everyone asks

The questions everybody asks.

Answered here rather than three emails from now.

"Is this a referral program? Because I have three of those in a drawer."

No, and that's the point. Referral programs die signed — somebody makes an introduction, nobody activates anything, the paperwork sits there for two years. This gets embedded in what you build. Propelr runs the application, the onboarding and the support behind it, so it works whether or not anybody remembers to push it.

"I don't want to become a payments salesperson."

You specify it on the build, the way you'd specify a host or a CMS. We do the application, the underwriting, the integration support and the cutover.

"My existing clients are on Stripe. This sounds like a migration project."

It isn't. Everything you run today stays exactly where it is. We're not asking you to move anything.

"Does this widen my client's PCI scope? Because that lands on me."

No script and no iframe of ours goes on the checkout page. Credentials are brokered server to server, so the merchant stays at SAQ A instead of getting pushed to SAQ A-EP. Details below.

"What does this cost me?"

Nothing. The only real cost is developer hours to wire the API — hours you'd bill a client for on any payment integration.

"Does this put you between me and my client?"

No. The relationship stays yours and we have no contact with them you didn't create. If you walk away, the account belongs to your client — they keep everything. Your recurring payments stop, and nothing else does.

What actually happens

Your part is one sentence long.

A client asks who they should use for payments. You tell them it's handled. Everything after that — application, underwriting, account setup, integration support, and the calls afterward — happens on our side.

The client

Needs an ecommerce site and has no idea which payment provider to use.

02 · YOU

Your agency

The only step you're in.

"It's built in. It's better. We've got it."

Behind the scenes

Propelr runs the application, underwriting, merchant account setup, integration and ongoing support.

Live

The store goes live and payments work. Nobody had to shop for a processor.

Credited to you

Your agency is credited on the account and paid every month it keeps running.

Recurring revenue, every month it runs.

Five steps. You're in one of them.

The part you say out loud It's built in. It's better. We've got it.

Nine words, and it replaces the conversation where you send a client off to open a Stripe account and then wait two weeks to find out what they did.

We are not asking you to move a single existing client.

Don't touch your book. Migrating clients is ten times the work and nobody should do it on a stranger's say-so.

Try it on one new client — the next ecommerce build through your door.

And to be clear about the obvious suspicion: this isn't a foot in the door where we come back in six months asking for your book. If you ever move an existing client onto it, that'll be because you ran the numbers and wanted to — not because anyone asked you to.

One new client · not your book

The whole offer, in one place.

No part of this is held back for the call.

What you get

Your agency credited on every merchant account that comes through your builds, paid monthly for as long as that account runs
Sandbox credentials and API docs before you commit to anything
Application, underwriting, onboarding and cutover handled on our side
An onboarding specialist for the build, a support team after it
Your clients call our support number, not yours

What it costs

Nothing out of pocket. No fee, no minimum, no license, no seat, no exclusivity
Developer hours to wire the API — which you bill your client for, as you would on any payment integration

What we ask

Use it on one new build. That's the entire ask. Everything after it is ours.

And to be plain about the category: this is an integration program, not a referral program. The difference is that a referral depends on somebody remembering to act, and an integration doesn't.

It plugs into what you already build — Shopify, WooCommerce, BigCommerce, Adobe Commerce, custom builds, and anywhere a client takes a card through software you touched. Sandbox and docs before any commitment.

Worth knowing

Every launch decides this for years. Then it's decided.

This is the part that makes waiting expensive, and it's worth being precise rather than dramatic about it.

When an ecommerce store goes live, the merchant account behind it gets credited to somebody, and that's settled. Not for a quarter — for the life of the account. Nobody goes back and re-credits it later. There is no mechanism anywhere in the card industry for claiming one of these retroactively.

So the meter only runs one direction. Every ecommerce project that launches out of your shop between now and whenever you get around to this is decided the day it goes live, and decided for as long as it runs.

Not delayed. Decided. Two builds this quarter is two accounts that will still be paying somebody in 2031, and it won't be you.

Nothing about that is urgent in the manufactured sense. No deadline, no expiring offer — we'd rather you took your time and got it right. It's just arithmetic that runs whether or not anybody's watching it.

Book 15 minutes with Brian 15 minutes · nothing to sign

Who you'd talk to

Twenty years on the same side of this.

Brian came up through the CardConnect and CardPointe side of the industry and has spent two decades working with small businesses one at a time. He holds our processor relationship and he takes the first call himself. After that you get an onboarding specialist and a support team, because one person does not scale and you would feel it inside a quarter.

He's served thousands of small businesses, but his actual specialty isn't merchants — it's agencies, consultants and technology providers who want payment integration to stop being their problem. That's an unglamorous way to build a reputation, and a very hard one to fake.

Brian takes your first call because that conversation needs judgment. Everything after it goes to people whose entire job this is — a program depending on one person answering stops working the moment it succeeds.

And don't take our word for any of it. Call whoever sold your biggest client their merchant account and ask who collects the recurring payment on it. Nobody in the industry will deny it — they'll just wonder why you're asking.

These aren't agencies. That's the point.

An optometrist, a tire shop, a med spa. None is an agency and none is talking about this program — read them as evidence of exactly one claim: this is an organization that stays with an account for years rather than disappearing after the signature. Anyone can say "white glove." Almost nobody can produce a decade of named clients willing to say the same thing.

"I can always call you with any questions, and you're always there."

Susan Loman
Owner, Loman Eyecare

"It's not just the rates. It's the service and who stands behind it."

John Cannon
Owner, MyCarDoc

"I love knowing I can call you at any time."

Brooke Tetrault
Manager, Clarity MD

And who's actually behind it.

The rails Propelr
Registered ISO of KeyBank, Woodforest National Bank and Pathward, N.A. Settlement runs through national banks, not a fintech balance sheet.
Scale Not a startup experiment
Propelr acquired Ireland Pay in 2024 and partners with FreedomPay on enterprise deployments. The infrastructure predates this program and doesn't depend on it.
The people An onboarding specialist, then support
One person assigned to your integration, talking to your developers. After launch, your clients call our number — declines, chargebacks, batch issues, none of it routes back to you.

Stated plainly

There is a catch. Here it is.

We get paid on processing, which means we only make money if your clients stay and keep running volume. If the service doesn't hold up, we lose worse than you do and for longer.

Here's the other half, and it's the part most people expect us to dodge: we work with agencies across the country because it's far more efficient than signing merchants one at a time. You already own the integration decision on every ecommerce store you build. Reaching the people who make that decision beats knocking on ten thousand doors — and that efficiency is what funds your share. Nothing altruistic about it.

On rates — they're fair, and in line with what your client would get from Stripe. We're not trying to win on price and you shouldn't sell it on price. The reason to use it is that it's yours, offered to clients who already trust you. You've done the hard part already.

Questions

The rest of it.

What does my client actually pay?

Fair rates, in line with what they'd get from Stripe. We're not built to win on price and you shouldn't be selling it on price.

Think of it the way a restaurant thinks about the drink that comes with the meal. Nobody orders the meal because the drink is cheaper somewhere else — they take it because it's already there, from someone they trust. You spent years earning that trust. This is you finally getting paid for having it.

What kind of support is provided?

An onboarding specialist for the build, a support team after it. Your clients call our number — declines, chargebacks, statement questions, none of it lands back on your inbox at four on a Friday.

Can I test the API before committing to anything?

Yes. Sandbox environment and published docs, before any agreement and before it goes near a client project. Break it first — that's the correct order.

What actually happens after the call?

Sandbox credentials and docs go to your dev team. When a client project comes up, you specify it on the build and we send your client the application. Underwriting runs on our side. Your team wires the API — we're available to them throughout. The store goes live, and the account is credited to you from the first transaction it clears.

On Woo, Shopify or BigCommerce that integration is configuration rather than development; on a custom build it's a normal API job. Nothing in the sequence requires you to sell anything, and you can stop at any stage.

What if my client doesn't get approved?

It happens — underwriting declines a percentage of applicants in every industry, and certain business types are ineligible regardless of who applies.

Which is why we tell you before it goes on the build. If a client is in a category that won't clear, you'll know at the point where it costs you nothing, not after you've told them it's handled. Nobody's reputation should ride on our underwriting.

When do I actually see the first payment?

Once the account is live and clearing volume, it's credited to you and pays on the processor's normal monthly cycle.

It is not large in month one. That's not the point — the point is that it doesn't stop, and it stacks with every store you add after it.

Is this exclusive? Am I locked in?

No. You keep every processor relationship you have, you can use whatever you like on any project, and there's no volume commitment. Use it on one build and never again, and that account keeps paying you anyway.

Other companies offer something like this. How should I compare them?

They do, and you should compare. Here's what separates them, in the order that matters:

Is it a referral or an integration? If your only role is passing a name along and hoping, it's a referral — and referrals die unactivated in a drawer. Ask who does the application, the underwriting and the cutover.

Does their code go on your client's checkout? A hosted script or iframe is the fast build and it pushes your client from SAQ A to SAQ A-EP. Ask specifically.

Who answers when a merchant calls, and whose account is it? If merchant support routes to you, that's unpaid work — and if your client can't keep processing after you walk away, you've put them somewhere you'd regret.

Take those four to anybody. If someone answers them better than we do, use them.

Next step

Two ways this goes.

You take the call

Fifteen minutes. You find out whether the numbers are interesting for a shop your size, and you either use it on the next build or you don't.

Worst case, you spend a quarter of an hour learning how the payments side of your own industry actually works.

You don't

Nothing bad happens. No deadline passes, nothing breaks, no one calls you about it.

Which is exactly the problem. Your next build goes live, the account gets credited to somebody else, and that's settled for as long as the store runs. Not a disaster — just a decision made by default.

So — is it ridiculous to spend fifteen minutes finding out?

Fifteen minutes, no deck. Tell Brian roughly how many new ecommerce builds you take on in a year and he'll show you what that compounds to. You can ask him anything, including what he makes on it.

Nothing to buy on the call, nothing to sign after it, and zero expectation of immediate action on your part.

Pick any slot that suits you. Move it or cancel it later without telling anyone why.

The calendar widget didn't load — usually an ad blocker or a privacy setting.

Open Brian's calendar in a new tab

Calendar not loading? Open it in a new tab

Or don't talk to anyone yet.

Email brian@conduitpaysolutions.com and we'll send sandbox credentials and the API docs. No agreement, no signature, no call.

Hand them to whoever owns your integrations and let them try to break it. That's the fastest way to find out whether any of this page is real, and it costs you nothing either way.

Or it's just not this quarter.

That happens, and it's a perfectly good answer. Email brian@conduitpaysolutions.com with the word later and Brian will check in once, in about six months.

One email, from a person. Not a newsletter, not a sequence, and we won't sell your address — you know exactly what a list like this is worth, which is why we're telling you what we'll do with it.

You got paid once for building your client's ecommerce checkout.Everyone else has been getting paid every month since.