Prepared for MiCamp

AI systems and automation for fast merchant onboarding

I am Christopher Shearer, an AI automation and integration engineer who built the agent systems, retrieval and test harnesses that connect software fast, after running companies, crews and a multi-agent platform. The five-year projection runs on planning inputs, so MiCamp's own funnel can replace each one and rerun the model.

Austin, TXchris@shearerlabs.com(512) 618-2358github.com/Cshearer210
01

Six processors moved $5.92 trillion in 2025

Together the six moved about $5.92 trillion, up about 16%, and growth ran from 7% at PayPal to 34% at Stripe, so the largest processor was also the fastest growing.

$5.92T
Combined 2025 volume across the six processors, where volume-weighted growth was 15.9%.
Stripe
$1,900B +34%
PayPal
$1,794B +7%
Adyen
$1,575B +8%
Square
$250B +10%
Toast
$195B +23%
Shift4
$209B +27%

Adyen is converted at the ECB 2025 average of 1.12998 USD per EUR and Square is the sum of its four published quarters, so each bar follows its own company's volume definition.

5,671,836
US business applications were filed in 2025, the highest annual total on record (Census Bureau), and each one is a merchant an onboarding path has to win.
17.1%
of US retail sales were online in Q2 2026 (Census, seasonally adjusted), where checkout and integration quality decide whether a sale completes.
84%
of developers use or plan to use AI tools, up from 76% a year earlier, and nearly 80% of new GitHub developers use an AI assistant in their first week.
02

Switching, payments friction and time to first revenue

These figures recur across the category, so together they set what a shorter path from application to first charge is worth.

1 in 5
US small businesses that accept cards changed their primary processor within two years (Mercator Advisory Group, 2,047 firms), so keeping a merchant is as hard as winning one.
80%
of US small employer firms report payments challenges and 52% cite processing fees (Federal Reserve Banks, 2024 Report on Payments, 4,858 firms), the friction an onboarding path has to remove.
20% vs 8%
of new Atlas businesses charged a first customer within 30 days in 2025, against 8% in 2020 (Stripe annual letter), so time to first revenue is now a number processors compete on.
03

How AI assistants select a processor

New merchants increasingly ask an assistant to set up payments, and it answers from pages it can read and verify. Citation follows content that is clear, structured and dated, so the onboarding has to deliver what the page states.

Up to 40%
lift in visibility in generative answers from how a page presents its evidence (GEO study, KDD 2024), so page structure is a lever MiCamp controls.
0.66 to 0.74
correlation of web and video brand mentions with AI visibility across 75,000 brands (Ahrefs, Dec 2025).
MCP and plain text
leading processors publish plain-text docs, an MCP server and an agent setup command, so an assistant completes an integration end to end.

The build

  • Onboarding and pricing pages carry dated figures and onboarding times, so an assistant can quote them and a merchant can check them.
  • Schema markup and plain-text documentation make the same pages readable to an assistant in one pass.
  • Page content comes from complaint mining of public sources, where 85 of my 2,017 hand-labelled complaints concern holds and payouts.

Agent checkout protocols

  • The Agentic Commerce Protocol, announced 2025-09-29, lets an assistant complete checkout on a buyer's behalf.
  • Google AP2 was announced 2025-09-16 with more than 60 organizations behind it.
  • Visa and Mastercard define agent identity and tokens on the card rails, so the protocols settle on the networks MiCamp already uses.
04

How the leaders compare with an embeddable platform

Leader cells come from each vendor's own pages, and the Venditory column shows what already works in the platform I built. A check mark means included in a plan, a plus sign means sold as an add-on or covering part of the job, and a phrase names what the vendor's own page describes for that capability.

One login from counter to lead

Every leader covers the counter, and the lead row stays empty across their core products, so a merchant who wants leads, stock and reports in one login adds tools to any of them.

CapabilityCloverSquareToastShopifyVenditory
Counter and split tender✓✓✓✓✓
Inventory and stock counts+✓++✓
Owner reports+✓✓✓✓
AI assistant inside the productBusinessQ AI predictions✓✓✓✓

What a new merchant meets at sign-up

The leaders start a merchant with an application form, a published list of prohibited businesses and a dispute view after the fact, so Venditory moves the merchant's category and card-network exposure in front of the first application, where a weak one is caught before it costs a review.

CapabilityCloverSquareShopifyVenditory
Setup questionnaire that shapes the menuQuick online applicationSign-up asks business typeOptional customized setup questionnaire✓
Readiness checklist before a high-risk applicationSeven-step start-up checklistUnsupported industries list publishedProhibited list, check before signup✓
Category and restricted-terms check at sign-upMerchant category rulesReviews sign-up info, rechecks laterEligibility rules stated before signup✓
Chargeback ratio shown beside card-network limitsDisputes tab with status labelsDispute rate card on dashboardChargeback rate in settings and reports✓

AI assistants in the product

Square, Toast and Shopify each ship an assistant that reads the merchant's own data and Clover has only announced plans, which makes an assistant in the product the baseline that a processor's merchants will expect.

ProductAssistantWhat the vendor says it does
SquareSquare AIAnswers questions about the owner's own business data and pins charts that refresh.
ToastToast IQA conversational assistant announced 2025-10-29 for U.S. customers on mobile and web.
ShopifySidekickAn assistant inside the admin, named on Shopify's point-of-sale page.
CloverBusinessQ AI predictionsAI-driven predictions inside Clover analytics, with Fiserv planning a marketing agent.
VenditoryAssistant in the suiteWorks beside the counter, stock and reports and accepts files the owner attaches.
05

Merchant-reported friction across the category

Complaints cluster in five places, and each cluster maps to a decision in the onboarding path.

Holds and payout timing

Funds are held following approval and payout schedules change without notice, so the first fix is a published, dated schedule.

Fee transparency

Rate changes and itemised fees differ from the quoted price, so the quote and the statement have to show the same lines.

Support response

Replies are scripted and escalation is slow on integration questions, so an integration question needs a route to someone who owns the integration.

Integration fit

Some processors do not connect to the software the business already runs, so the connector belongs inside the onboarding and not at the end of it.

Termination without a route back

Account closures come with no stated path to reinstatement, so a closed merchant needs a written route back.

2,017

hand-labelled public complaints sit in my mining pipeline, where I rank them by count and severity to decide what the onboarding pages answer first.

06

One platform with payments at the center

Businesses choose the vendor that lets them get on with their work, and Okta counts 101 apps per company. Payments-led financial technology is 82% of Toast's revenue and 65.6% of Shopify's merchandise volume runs through Shopify Payments, so payments pull the rest of the suite along.

227
pages in Venditory, with 43 routes, 377 migrations and 307 tables, which carry the counter, stock, reports, lead finding and email outreach in one codebase.
$82.1B
gross transaction volume at ServiceTitan, a vertical platform with embedded payments, which shows how far one trade's software can carry payments.
9.2M
business members on BILL's payment network, with $98.2B of quarterly payment volume.
07

Controls that keep a high-risk book inside network limits

The card networks publish the limits that bound a high-risk book, and each control below keeps an account inside them.

Published network limits

  • Visa VAMP merchant excessive was 220 bps and fell to 150 bps on 2026-04-01, with at least 1,500 monthly events.
  • Visa VAMP acquirer is above standard at 50 bps and excessive at 70 bps, so the acquirer's ratio moves with its merchants' ratios.
  • Mastercard's excessive chargeback program starts at 100 chargebacks and 1.50%, with fines from $1,000 to $200,000.
  • Visa Order Insight let merchants deflect 40 to 45% of confirmed first-party disputes.

Controls

  • Underwriting screens site, product and licence, and runs rules in shadow mode against historical applications before release.
  • Rolling reserves and delayed settlement are sized to the ratio, so exposure follows the risk.
  • Continuous chargeback scoring and checkout-page script monitoring (PCI DSS 4.0.1, 6.4.3 and 11.6.1) catch movement before a threshold does.
  • Dispute evidence is assembled automatically and every automated decision is logged for replay (Federal Reserve SR 26-2).
08

Projection: onboarding, volume and revenue, five years

Automated onboarding raises application-to-live activation and lowers the cost to board a merchant, and every line below is computed from the planning inputs in the first table. The same model reruns on MiCamp's boarding data, so each input can be replaced with a measured one.

7,939
Active merchants at the end of Year 5 in the base case, once activation rises from 55% to 70%.
$1.8B
Processed volume in Year 5 of the base case, which follows from the active merchants and the volume per merchant.
$4.4M
Incremental net revenue over five years in the base case, which is the revenue the faster path adds.
$5.6M
Cumulative net contribution in Year 5 net of the program cost, so the cost of the dedicated builders sits inside the figure.
Year 1
First year the program is cumulatively positive in the base case, once savings and added revenue pass the program cost.
55% to 70%
Application-to-live activation, current to automated, where the automated path is the one the program builds.

Assumptions

InputConservativeBaseUpsideBasis
Applications in Year 11,5002,5004,000Planning input for MiCamp's boarding funnel
Annual growth in applications10%15%20%Planning input
Application-to-live activation, current55%55%55%Planning input
Application-to-live activation, automated64%70%78%Planning input
Annual card volume per active merchant$180K$250K$350KPlanning input
Net revenue on volume0.30%0.40%0.50%Planning input
Annual merchant attrition23.6%23.6%23.6%Published merchant-services attrition figure
Cost to board one merchant, current$300$300$300Planning input
Cost to board one merchant, automated$120$80$60Planning input
Program cost per year (dedicated builders and tooling)$500K$500K$500KPlanning input

Active merchants (projection)

7,9395,9543,9691,9850Year 1Year 2Year 3Year 4Year 5

Every bar is computed from the assumptions above, so changing an input moves the bar.

Base case by year (projection)

Base caseYear 1Year 2Year 3Year 4Year 5
Applications2,5002,8753,3063,8024,373
New active merchants, current1,3751,5811,8182,0912,405
New active merchants, automated1,7502,0122,3142,6623,061
Active merchants at year end, current1,3752,6323,8295,0176,238
Active merchants at year end, automated1,7503,3504,8736,3857,939
Processed volume, current$171.9M$500.8M$807.6M$1.1B$1.4B
Processed volume, automated$218.8M$637.4M$1.0B$1.4B$1.8B
Net revenue, current$688K$2.0M$3.2M$4.4M$5.6M
Net revenue, automated$875K$2.5M$4.1M$5.6M$7.2M
Incremental net revenue$188K$546K$881K$1.2M$1.5M
Boarding cost saved$550K$632K$727K$836K$962K
Program cost($500K)($500K)($500K)($500K)($500K)
Net contribution$238K$679K$1.1M$1.5M$2.0M
Cumulative net contribution$238K$916K$2.0M$3.6M$5.6M

Incremental net revenue (projection)

$7.3M$5.5M$3.7M$1.8M$0Year 1Year 2Year 3Year 4Year 5

Cumulative net contribution after program cost (projection)

$24.7M$18.5M$12.3M$6.2M$0Year 1Year 2Year 3Year 4Year 5

Three cases, Year 5

Year 5ConservativeBaseUpside
Active merchants, automated3,8587,93915,944
Processed volume, automated$636.1M$1.8B$5.0B
Incremental net revenue, Year 5$268K$1.5M$7.3M
Incremental net revenue, five-year total$791K$4.4M$20.0M
Cumulative net contribution($61K)$5.6M$24.7M
First cumulatively positive yearbeyond Year 5Year 1Year 1

Unit economics

MeasureBase caseDerivation
Net revenue per active merchant per year$1Kvolume per merchant times net revenue rate
Expected merchant lifetime4.2 yearsone divided by annual attrition
Lifetime net revenue per merchant$4Knet revenue per year times lifetime
Boarding cost per active merchant, current$545cost per board divided by activation
Boarding cost per active merchant, automated$114cost per board divided by activation
Lifetime revenue to boarding cost, automated37xlifetime net revenue divided by boarding cost

Every figure is per merchant, so the model scales from one unit, and each 1% of the $77B+ annual volume on MiCamp's site that goes live, or goes live sooner, is $770M of annual volume.

Conditions the projection depends on, and the response to each

ConditionResponse
MiCamp's funnel differs from the planning inputsThe model reruns on the real boarding funnel, and the three cases bracket the range until it does.
Capacity for the buildDedicated builders, written runbooks and a replay log for every automated decision keep the work independent of any one person.
Card-network limits tightenContinuous chargeback scoring against the published thresholds, with reserves sized to the ratio, moves the response ahead of the limit.
Regulatory change in high-risk categoriesLicence and category screening at underwriting is reviewed with MiCamp's compliance team ahead of release, so a rule change reaches production with that review behind it.
Competitors move first on AI discoverabilityComplaint-driven pages and plain-text documentation ship in the first phase, which is the lead time that matters here.
09

Test depth: experimentation and verification

Decisions rest on many options tried from many angles, and every check is proven on a planted fault before it counts.

1,703
trained runs across 670 model families and 6,525 fold evaluations in one competition, where a scorer rejected 157 of 183 candidates.
775
registered checks and 1,232 self-testing scripts, with 72 scripts that plant faults, so every check has been seen to fire.
2,131
page visits in one full walk of a platform I built, which covered 232 addresses and 5 user roles.
4,259
logged checks across a course pipeline, where each patch is applied on its own passing check.
60
agents and 187 automated jobs run my company across three machines for $200 a month, behind an evidence-gated ledger.
17 of 17
planted faults were caught in the offline sale queue, because every sale carries a unique reference and a search runs ahead of any retry.
10

What I have built for onboarding

Five builds cover the path from sign-up to a monitored live account, and each one comes with the measured result beside it.

Merchant onboarding automation

A setup questionnaire configures the product to a business at sign-up, and a readiness checklist and restricted-terms gate screen high-risk merchants before an application goes out, so a weak application is caught before it costs a review.

Processor choice screen

It compares 4 processors with every fact carrying a source and a checked date, and offers three ways to connect, an embedded account, the business's own processor or a referral, so the merchant picks the route that fits.

Complaint mining

I labelled 2,017 public merchant complaints by hand and found 85 on holds and payouts, the cluster that decides which onboarding pages and support flows come first.

Sandbox integration testing

I wrote a shop's card path against a processor's sandbox, broke it on purpose four ways with all four caught, and caught 17 of 17 planted faults in an offline queue.

Chargeback and compliance monitor

It scores a merchant's chargeback ratio against card-network limits, including Visa's 150 bps threshold from April 1, so a high-risk account is flagged ahead of the limit.

11

Leadership and operations

Onboarding is an operations problem as much as an API problem, so these two results show how I run people, budgets and rebuilds.

75+ stores

Medicus

I founded a state-licensed company at 24, raised investment and secured one of the first licenses issued in Oklahoma in 2018, then sold its products myself to 75+ stores for $1.3 million of revenue in its first year. I hired over 20 people, set salaries and raises, built a budget for each part of the business and wrote the SOPs and training the team ran from.

$60,000 a month

Volta

I commissioned a $500,000 cryogenic extraction plant three prior hires had failed to run, diagnosed the fault from the process behavior, and re-routed the system with $5,000 of parts, which took a business with two years of no sales to $60,000 a month within two months. I recovered batches already written off, 50 kg of extract to 30 kg at 99% purity, by building a pesticide remediation line.

12

Core competencies and evidence

AI systems and agent methods

Autonomous fix loops

I run research, build, test and repair loops on predetermined methods that do not drift, watched by over 750 daily checks and ratchets that only let counts improve, which closed 3,531 requests in 30 days.

Per-pipeline memory

I built a memory that saves what each loop learns into its own pipeline folder, 14 folders and 703 loop records, so parallel sessions never overwrite each other or mix one pipeline's work with another's.

Custom model stacks

I train and score custom models, 477 across 11 Kaggle competitions, using neural networks, distillation, learned combiners and stacked ensembles to build a stack for each task.

Retrieval and research loops

I combine local indexes over 82,859 passages with research loops that scan hundreds to thousands of sites a day, including about 17,900 reviews and posts, and pull the newest tools and methods into the system.

Agent orchestration

I run parallel agents in isolated clones with enforced file ownership and a single merge, behind 66 gates that refuse unsafe writes and unproven claims of done.

Token optimization at scale

Forty enforced methods, among them local models, batching, slicing, background tasks and indexing, make Claude use 30 to 50 percent fewer tokens on identical graded work: 50 percent on a 14-task benchmark and 30 percent on an 84-task one against a default agent.

Closed-loop process control

I tuned soak times and temperatures per batch against HPLC assays taken before and after extraction, the measure-and-adjust loop I now run on software.

Human-in-the-loop change

I built the agent a shop owner types requests into, where it edits a disposable branch, a reviewer battery checks it in a sandbox and a human approves, and 29 requests have passed.

Payments and integration

Point of sale

Counter, split tender, stock and reports in one retail system, with 31 pages, 53 API endpoints, server-recomputed tax and a spreadsheet sync that updates a sale instead of duplicating it.

Processor research

I compared 30 payment processors on methods, onboarding, restricted categories, reserves and holds, and recorded a cell as Yes only where the vendor's own page said so, so every yes traces to a source.

Reconciliation

I built a tender ledger for split payments and settlement matching that ties each deposit to the sales it covers, and cleared 25 of 25 payment-risk cases on holds, reserves and chargeback limits.

Integration layer

I built a commerce platform's connectors for Stripe, Shopify, WooCommerce, TikTok, Twilio and a card processor's gateway, checked by 192 Stripe tests and 82 webhook-signature tests, so each connector is proven before a merchant relies on it.

13

Sources