Each payor keeps its own record
Vendor codes, names and addresses stay as the payor uploaded them. Matching links the vendor to the verified payee and leaves the payor's record alone.
Business payments platform
Pay verified vendors by the right method, with every step on record.
ZinPay matches every vendor to one verified payee, routes each payment by ACH or check, and gives payors, suppliers and operations their own view of the same payment.
How it works
From spreadsheet to settled, in one system.
Six steps carry a payable from the file your team already has to money in the vendor's account.
-
1
Import
Upload a vendor or payables sheet in any layout. ZinPay maps the columns and shows a preview before anything is saved.
-
2
Verify
Each vendor is matched to a verified payee. An operations reviewer confirms every match.
-
3
Approve
Payables follow your approval workflow. Each decision is recorded with who made it and when.
-
4
Route
Each payment goes by the first method in your order that the payee accepts.
-
5
Send
ZinPay submits the payment and tracks it from sent to settled.
-
6
Reconcile
Each bank debit ties back to the payables it funded.
The apps
One payment. A view for everyone involved.
Payors, suppliers, operations and platform admins each get their own app on the same records.
Pay app
Import, approve and pay.
Finance teams load vendors and payables, approve them through configurable workflows and follow each payment to settlement.
- An import wizard that reads any spreadsheet layout, detects the columns and saves the format for next time.
- Approval workflows with templates, triggers and role-based approvers.
- A Needs Attention queue for vendors and payables that need a decision.
- Reconciliation that ties each bank debit to the payables it funded.
Supplier app
See what was paid and where it went.
Suppliers accept an invitation and see their payments from every payor on the network in one place.
- A payment list and payment details across payors.
- Exports for their own accounting.
- Payout accounts added through a secure enrollment flow, so bank details never travel by email.
Ops app
Verify vendors and keep the payee directory clean.
Operations reviews every new and changed vendor, and owns the payee records that payments are sent to.
- A vendor review queue with a recommended action for each vendor.
- Payee records with parent and child entities, aliases, documents and payment destinations.
- Suspending a payee holds its in-flight payments until it is active again.
- An audit log of every change, by person and by record.
Platform app
Run many tenants from one place.
Platform admins create tenants, set what each one can do and watch the system that runs underneath.
- Tenants with their own payors, payees, settings and API keys.
- Roles and permissions, users, and impersonation that is read-only by default and fully audited.
- AI models, payment providers, queues and schedules, and an email log.
Vendor management
Two payors, two spellings, one verified payee.
Vendor lists are messy. ZinPay compares each uploaded vendor to the payee directory by bank account, name, address, email and phone, and recommends an action. A reviewer makes the decision.
People make the decision
ZinPay recommends match, create or send back to the payor. Nothing is linked until a reviewer confirms it.
Changes go back to review
When a verified vendor's bank details or address change, a reviewer sees the change before it takes effect.
Payment routing
Each payment takes the best route the payee accepts.
Set the order of payment methods once. For every payment, ZinPay checks which of the payee's accounts accepts it and picks the first method available.
- Rules for each payee account: accept, decline, or accept under conditions such as an amount limit.
- Overrides for one payor or one vendor, so a payor's money goes to the account that payor supplied.
- If the best route changes after approval, the payment holds. It never switches method without your approval.
AI assistants
AI that works inside your permissions.
ZinPay's assistants use the same actions as the people they work for. An assistant can do only what its user is allowed to do, and only what the assistant was granted.
Assistants for everyday work
Ask about payables, vendors and holds, get a daily summary, or have the Workflow Builder draft an approval workflow.
A second opinion on vendor reviews
The Vendor Review Agent checks a vendor against the directory and public web sources, then records a recommendation. The reviewer decides.
Your own AI client
Connect an MCP-compatible client with an API key, read-only or read-write. Bank details are withheld from external clients.
Controls for each tenant
Choose the model provider, set budgets and allowed topics, and review a trace and cost for every run.
Enrollment
Onboard a payor or a bank account with one link.
Send a secure link. The applicant fills in business and bank details, signs the agreement and submits. Your compliance team clears it, sends it back or rejects it.
- No account needed: the link is short-lived and opens one enrollment only.
- Steps, forms and decisions are templates you edit, with a live diagram of the flow.
- The same flow adds funding accounts for payors and payout accounts for suppliers.
- It runs in your brand, on its own page or inside the app.
Multi-tenant
One platform, many networks, each under its own brand.
Each tenant has its own payors, payees, settings and keys. Its colors and logo carry across every app, the enrollment flow and email.
- Tenants are separated in the data itself. One tenant's payees and bank accounts are never offered to another.
- Settings for each tenant: payment method order, vendor review rules, document categories and AI models.
- Tenant admins see every payor in their network without switching accounts.
Built for money movement
The parts you do not see carry the payment.
Its own ledger
ZinPay keeps its own ledger and tracks the balance of each account.
ACH and check
Two payment methods behind one provider interface, so a bank or check printer can change without changing the product.
No double payments
Submission is idempotent: a retried request does not send the same payable twice.
Permissions on every action
Every change is checked against the user's role, for people and for assistants alike.
A complete audit trail
Each record keeps its history: who changed it, when, and on whose behalf.
API keys and signed webhooks
Integrate with keys scoped to a tenant and receive signed events as each payment changes status.
Get in touch
See how ZinPay fits your payments.
Tell us a little about your business and how you pay vendors today. We will reply by email.