How a sales company becomes a payments company.
Notes from the team building the engine behind VizyPay. What we learned turning a sales organization into a payments company, and how you can too.
The API That Refuses to Ship Incomplete
How we built the API guardrails that prevent incomplete merchant portals from ever shipping.
Read the post →Silent Failure: The Robot That Went Green While Doing Nothing
The most dangerous system state is not broken, it is broken while reporting success. This is the story of our re-test robot and the day we made failure loud.
Read the post →Practice Mode Shipped Because One Rep Asked For It
A sales rep asked for a safe place to practice inside our quoting tool. A day later he was the one who proved it worked. Here is why every tool we build gets a practice mode.
Read the post →The Bug Report That Redesigned Our Front Door
One word on a weekly checklist, FAIL, on a screen that technically worked. Seven weeks of compounding later, it had redesigned our platform's front door.
Read the post →The Silent Failure We Shipped to Our First New User
The most dangerous bug is the one that works. Our second user ever got locked out of an account he did not know he had, and the fix was live the same afternoon.
Read the post →The Tester Who Designed the Feature
Ben Le passed all ten test items, then found what the checklist missed and designed a feature that shipped the same afternoon with his name in the record. How we run QA.
Read the post →The Placeholder Is Dead
The placeholder is dead. Real rates are in, every number hand-walked, and one stale label caught that green tests missed. Why an honest estimate beats fake precision every time.
Read the post →Nobody Asked Him to Build It
The newest feature on our platform started as a file nobody asked for. Built by operations, not product. Here's what we did with it.
Read the post →The Post Our Own Software Refused to Publish
Today I tried to publish a social post and my own software told me no. No override existed. Good. Here's why we built the gates that way.
Read the post →No Receipt, No Commission
Most ISOs pay commissions on trust and memory. This week we armed a rule in our own payroll tool: no receipt, no commission. Refused at the door, not flagged for review.
Read the post →The Day a Negative Number Tried to Lie to Us
Every test was green. The tool still lied. What a returns-heavy day taught us about building honest activation tracking.
Read the post →Your Merchant Boarding Process Should Live in the Software, Not in Someone's Head
Our ops lead wrote down how the team really moves a deal from paper to live equipment. We built their process as a guided flow wired to real deal state, then walked it and found what a thousand green tests missed.
Read the post →Least privilege is not overhead, it is how you protect money
Role-scoped permissions, server-side enforcement, and immutable audit trails protect commissions and trust.
Read the post →The Money Your Client Book Is Handing to Someone Else
How a regional pest control business captured payment revenue from 2,000 existing clients and built a second revenue engine in 90 days.
Read the post →Security Is Not a Launch Feature. It Is a Birth Criterion
We banned the phrase "just a prototype." Everything built into VEXIS carries day-one security, proven on our own company before any lane opens.
Read the post →Your residuals are compounding faster than your base business
Residual income compounds. Most ISOs have never calculated what that means for agent economics or retention.
Read the post →Your agents need to see what their merchants actually process
Transaction-level history bridges the agent-to-merchant support gap.
Read the post →One merchant dashboard for your entire agent network
How to structure agent hierarchies so payouts are clear, screening stays tight, and you never lose sight of your merchant base.
Read the post →Compliance, Built In: How VizyPay Runs OFAC Screening on Every Account, Every Day
Why every payments company inherits a federal compliance job on day one, and what actually happens when a screening system flags someone.
Read the post →When you run payments for your clients, you need to see everything in one place
When you become the payments company for your clients, their entire payment trail becomes your job to see. Here is why we consolidated every batch, chargeback, and authorization into one view, and why we built it for our own team first.
Read the post →We have not published in this lane yet. New field notes drop regularly. Subscribe below and you will be first to see them.
The engine behind VizyPay. Soon in your inbox.
Launch news, the details that matter, and every new field note. No spam, ever.