The default payment stack most businesses inherit was designed to onboard as many merchants as possible with as little friction as possible. That is not the same as being designed for your business. When your revenue model is subscription-based, your checkout is embedded in a platform you built, your customer base operates internationally, or your product category sits outside the standard risk matrix — the default stack starts showing its edges.
Proficient designs payment systems from the infrastructure up, built around what your business actually does rather than adapted from what a standard processor already offers.
What off-the-shelf costs you
An off-the-shelf processor charges what it charges and routes how it routes. You get a merchant account, an API, and a rate schedule that was built for their margin, not yours. If you want a different routing path, a custom risk tolerance, a specific settlement window, or a gateway that integrates directly with software you built — you are working against the product instead of with it.
The cost shows up in basis points you cannot negotiate, authorization rates lower than they should be, development time spent working around API limitations, and eventual termination risk when your volume or category no longer fits the processor's appetite. A payment system that was never designed for your business will eventually make that clear.
What designing for your business actually looks like
Building a payment system around a specific business starts with understanding what the business does — not at the product level, but at the transaction level. How does money move? Who initiates the payment? What triggers a refund? What does a dispute pattern look like for this category? What volume is expected in month one versus month twelve? What happens at peak?
From that picture, the architecture follows. Proficient builds across four layers that are configured specifically for each business relationship:
- Gateway architecture — custom routing logic, failover paths, and network selection based on your transaction profile and volume
- Underwriting parameters — risk tolerance and approval criteria set around your actual business model, not a category average
- Software and tooling — APIs, webhooks, dashboards, and reporting built to connect with your existing stack rather than requiring you to adapt to ours
- Banking lines — direct relationships with acquiring banks selected for your category, volume tier, and geographic footprint
Business models that standard processors handle poorly
Some business models are structurally difficult for off-the-shelf processors to support well. Not because the businesses are problematic, but because the standard product was not designed with them in mind.
- Subscription and recurring billing businesses with trial-to-paid conversion structures and high cancellation rates
- Marketplaces and platforms that split payments across multiple sellers with variable payout timing
- High-ticket merchants in services, coaching, or professional categories where individual transaction size is well above standard averages
- High-risk verticals — nutraceuticals, telehealth, adult, travel, firearms accessories — where the standard processor relationship ends at the first chargeback spike
- Software platforms embedding payments as a feature inside a product they built and own
- International merchants processing in multiple currencies with cross-border settlement complexity
Each of these situations benefits from a payment system designed with the business model in mind from the start — not retrofitted into one that was built for someone else.
The difference between configuration and architecture
Most processors offer some degree of configuration: you can adjust retry logic, set velocity limits, add descriptor text. Configuration works within the boundaries of the existing system. Architecture sets the boundaries.
When Proficient builds a payment system for a specific business, the routing decisions, the risk parameters, the settlement structure, and the software layer are all built for that business from the start. If the business changes — new product line, new geography, new volume tier — the system can change with it, because the team that built it is still running it.
Starting the conversation
The starting point is not a form or a rate quote. It is a conversation about what your business does, where it is going, and what the current payment setup is costing you — in fees, in declined transactions, in development time, or in risk.
If you have outgrown the processor you started with, or if you are building something new and want the payment infrastructure designed correctly from the beginning, that is the conversation Proficient is built for.