HEALTHCARE & RETAIL SAAS
Practice management, pharmacy, point-of-sale, retail platforms
Problem. Declines, ACH returns and slow payouts cost you money.
Outcome. Bad payments caught before they fail. Payouts on the right rail. Same processor.
MODERN PAYMENTS · MONEY IN AND MONEY OUT
Money in from your customers. Money out to suppliers, contractors and payees. Every payment is approved, held or declined against your rules in under 20 ms, before it moves. Keep your processor. Add AI agents when you're ready.
00 · DECIDE FIRST, THEN EXECUTE
ezpymt decides. Your rails execute, or our partner banks' rails do. Same five gates, same signed record.
THE BRAIN · DECISION
Decides if the payment should move.
1 · REQUEST
Your platform
A user, a job or an agent asks to pay.
2 · DECIDE
ezpymt engine + your signals
Five gates. Approve, hold or decline.
THE MUSCLE · EXECUTION
Moves the money.
3 · EXECUTE
Your rails, or partner bank rails
Approval Layer: your processor. Governed Payments: partner bank rails.
4 · OUTCOME
A governed payment
Right rail. Signed record.
Approved crosses to execution. Held goes to review. No money moves until the decision says yes.
TWO WAYS TO BUY · 01
Keep your processor and bank. ezpymt decides; they execute.
TWO WAYS TO BUY · 02
Licensed partner banks run ACH, RTP, FedNow and stablecoin rails.
01 · WHO IT'S FOR
Three kinds of platform. One decision layer.
HEALTHCARE & RETAIL SAAS
Problem. Declines, ACH returns and slow payouts cost you money.
Outcome. Bad payments caught before they fail. Payouts on the right rail. Same processor.
Agent ezPay™ · GENERALLY AVAILABLE
Problem. An agent can't be trusted with money until the limit is a rule, not a prompt.
Outcome. The limit holds even when the agent is wrong. Agent payments become a product you sell.
Agent ezPay™ is live in production. Activation follows your approved integration. Give agents spending authority, initiate payments through the API or MCP, and apply your payment rules before money moves.
B2B MARKETPLACES & ENTERPRISE
Problem. Slow payouts lose sellers. Untraceable payouts lose hours.
Outcome. Instant payouts, each tied to an invoice and a tenant.
02 · WHERE IT SITS
Fraud tools score. Processors move money. ezpymt decides.
LAYER 1 · SIGNAL IN
Stolen cards and fake accounts. Their score feeds the decision.
Blind spot: a valid card in a 14-payment loop.
LAYER 2 · DECISION · ezpymt
Approves what fits. Holds loops and overspend for review. Declines the unauthorized.
Then hands off to execution.
LAYER 3 · EXECUTION
Move and settle the money.
Blind spot: any valid request gets paid.
03 · HOW IT WORKS
Under 20 ms, then the best rail. If a gate can't run, a person decides.
01
Person, service or AI agent. Verified before anything else.
02
Per payment, per day, per customer. Nobody raises their own limit.
03
A loop or spike trips a breaker. That flow is held; everything else keeps moving.
04
Sanctions, KYB, your fraud score, your rules.
05
Small on card. Large on ACH, RTP or stablecoin.
04 · FOR YOUR TEAMS
Your team sets the rules. The code enforces them.
APPROVAL CONSOLE
For payments, product and finance.
APPROVAL API
For engineers and AI agents.
05 · THE 90-DAY PILOT
Shadow Mode watches your live payments and reports what it would have done. Nothing changes.
STEP 1 · DAY 1
Mirror your traffic. No migration, no code change in Shadow Mode.
STEP 2 · WEEKS 1–12
What you could have approved. What you would have caught. Zero money at risk.
STEP 3 · DAY 90, OR SOONER
One call before each payment. Live.
06 · FOR DEVELOPERS
One call before each payment. SDKs, a sandbox, and AP2 and MCP when you need them.
Read the docs →import { ezpymt } from '@ezpymt/sdk';
const result = await ezpymt.approve({
caller: { type: 'user', id: 'billing_admin_17' },
payment: { amountCents: 1425000, currency: 'USD' },
to: 'supplier_10928',
policy: 'payouts_default',
});
if (result.approved) {
await result.send(); // your processor or partner rails
} else {
// result.status is 'held' or 'declined'
console.warn(result.status, result.gate, result.reason);
}07 · COMMON QUESTIONS
Short answers. Long ones in the docs.
Both, through the same five gates. Most start with today's payments and add agents later.
More approvals, cheaper rails for large payouts, and new paid flows such as instant and agent payments. Shadow Mode shows the numbers first.
You are. So the limit must live outside the agent. ezpymt enforces a rule the agent can't change and signs the record.
No. ezpymt decides. With Approval Layer, your processor (for example Stripe) moves the money. With Governed Payments, our licensed partner banks run ACH, RTP, FedNow and stablecoin settlement, with their own onboarding.
No. Shadow Mode changes nothing. Live adds one call per payment.
It's held and sent to review with the reason. No money moves until a person or a rule says yes.
Sandbox keys now, or a 90-day Shadow Mode pilot on real traffic.
Or get sandbox keys with no call needed. No money moves in Shadow Mode.