LastPay does not ask businesses to change how they work. That is the most distinctive thing about the company co-founded by Austin Diaz and Max Umlas.
The product runs on a simple principle. The accounting tool the business already uses is the source of truth. Invoices originate there. Reconciliation lives there. The processor’s job is to plug into that environment, move the money, and disappear.
Today that environment is QuickBooks for most LastPay customers. The integration is bidirectional. A business creates an invoice in QuickBooks, the customer pays, and LastPay routes the transaction and syncs the result back into the ledger. No exports. No spreadsheets. No Friday morning ritual to true up the books.
Tomorrow that environment will be Sage, NetSuite, Xero, or Go High Level for a wider slice of the customer base. LastPay has those integrations in development. The thesis is that businesses should not have to swap accounting tools to access better processing. The processor should travel with the business as it grows.
The pricing posture is the second pillar. LastPay’s sales process opens with a side-by-side audit. A prospect sends in a recent processing statement. LastPay returns a like-for-like comparison. The numbers tend to do the closing. Customers commonly report savings in the thousands per month, with high five figures annually for businesses with mid-market volume.
The third pillar is the part that does not show up on a feature list. Reliability. Funding times that match the rest of the software industry. A statement that an owner can read. A support team that picks up the phone. These are the things that owners notice in month two, after the savings have already started to show up.
The brand position is short. Get paid faster. Keep more of every transaction. Stay in the tools you already use. Diaz drives the product. Umlas built the operational infrastructure that keeps onboarding fast and the backend stable. There is no exotic product roadmap. There is no surprise pricing change. There is no growth tactic that depends on owners not paying attention.
Customer types tend to fall into three groups. Service businesses that send invoices and want lower fees with cleaner reconciliation. B2B subscription operators that need recurring billing and stronger reporting. Agencies and managed service providers that route a high volume of invoices through a small team and cannot afford a Friday reconciliation tax. The product was built with those three groups in mind.
Security and compliance get less stage time in marketing than they should. LastPay handles PCI scope the way a modern processor is supposed to handle it. Card data is tokenized at the network. The customer’s accounting platform never touches a primary account number. Audit logs trace every transaction back to a user, an invoice, and a settlement record. The boring work of being a credible processor is, again, the work that earns the renewal.
What stays out of the marketing is the integration work that runs behind the scenes every quarter. QuickBooks updates its API. Card networks adjust assessments. ACH rails ship new return codes. Each of those changes can break a customer’s workflow if the vendor is not paying attention. LastPay’s engineering team treats those updates as the floor of the job, not the ceiling. Customers do not see the work. They see the workflow staying intact through a year of platform churn.
The product roadmap stays public on request. Customers can ask for the next two quarters of planned work and get an honest answer. The team would rather underpromise and ship than build a marketing list that drifts past its own deadlines.
For businesses that have been with the same processor since the early 2010s, LastPay is the cheapest piece of software they will ever evaluate. The audit is free. The savings show up the first month. The hardest decision is not whether to switch. It is what to do with the money the company stops losing.
For a closer look at the platform, watch How To Send Quick Invoices Using LastPay on the LastPay YouTube channel.
