What is Zenoz?

An overview of the Zenoz payments platform and the services it offers tenants, merchants and sales organizations.

Zenoz is a payments platform for software companies, payment facilitators and sales organizations that want to offer payments to their own merchants. You bring the merchants. Zenoz provides the onboarding, underwriting, money movement, card acceptance, reporting and compliance tooling behind them, through one REST API and a web dashboard.

How Zenoz is organized

Everything in Zenoz belongs to one of three levels. Each API key and login is scoped to one of them, so a caller only ever sees its own data.

LevelWho it isWhat it does in Zenoz
TenantThe platform or partner integrating ZenozBrands the experience, configures rails and pricing, manages its merchants, team, webhooks and settlement
MerchantA business that takes or sends paymentsAccepts cards, collects and pays out by bank transfer, manages recipients, and reads its transactions, statements and pricing
Producer (ISO, agent)A sales organization that signs merchants upSubmits merchant applications and follows the merchants in its book of business

Services

Merchant onboarding and underwriting

  • Self-serve application. Merchants apply through a hosted, tenant-branded wizard with email verification and status tracking. No login is needed to apply.
  • Agent-submitted applications. ISOs and agents can submit an application on a merchant's behalf through the Agent Onboarding API. Sensitive details (SSN, driver's license, bank account and ACH authorization) are never sent by the agent. Zenoz emails the business principal a secure, single-use link to supply them directly.
  • Underwriting. Every application runs through identity, sanctions and business checks, a risk score, and a document review sized to the merchant's industry. Applications are approved automatically or routed to an underwriter.
  • MCC lookup. Describe a business in plain words ("medical devices") and get ranked merchant category codes to choose from.
  • Activation. On approval, the merchant is invited to its dashboard and guided through setup until its first payment.

Accepting cards — Zenoz Cocoon

Cocoon is a set of hosted card fields you embed on your checkout page with one script, monarch-zenoz.js. Card numbers go straight from the shopper's browser to the Zenoz vault and never touch your servers, which keeps your PCI scope to SAQ A.

  • Publishable keys locked to your checkout domains
  • Payment intents with a client secret, confirmed from the browser
  • 3-D Secure challenges, card-testing protection and rate limiting built in
  • A full sandbox with test cards that trigger approvals, declines and challenges

See Cocoon Hosted Card Fields to integrate.

Bank payments and payouts

Zenoz moves money by bank transfer in both directions:

  • ACH debits and credits, same-day and next-day, with bank-account instruments and recipient ACH authorizations
  • Instant payouts over RTP and FedNow
  • Push-to-card payouts (OCT), domestic and cross-border
  • Recipients. Register each payee and their bank account or card once, then pay them by reference. Raw account numbers are never returned.
  • Quote, then commit. A payout is quoted first (amount, fee, rail and checks), then committed with an idempotency key, so a retried request can't send money twice.

Which rails a merchant can use is configured by its tenant, along with per-transaction and monthly limits.

Settlement, reporting and statements

  • Transaction history and analytics for tenants and merchants
  • Settlement reporting for tenants
  • Merchant statements and tax forms
  • Each merchant's effective fee schedule, and account-fee history for tenants
  • ACH returns tracking and reporting

Producers (ISOs and agents)

  • Manage ISOs, their agents and ISO managers
  • Agents see the merchants in their book of business and the progress of each application

Platform tools

  • API keys of distinct types, each limited to one job: server keys, publishable keys for the browser, payout keys and agent onboarding keys
  • Webhooks for payment, payout and application events, signed so you can verify them
  • Tenant branding (name, logo, colors) on the hosted pages and emails your merchants see
  • API version pinning, rate-limit visibility, a public changelog, and a US banking-holiday calendar for scheduling
  • Postman collection for the sandbox, available from the merchant dashboard
  • AI assistants. A Zenoz MCP server lets tools like Claude read your data and, where enabled, prepare payouts and applications on your behalf

Environments

EnvironmentUse it forCards
Sandbox — sandbox.zenoz.aiBuilding and testing your integrationTest cards only; no real money moves
Production — cloud.zenoz.aiLive merchantsReal payments

Each environment has its own accounts, keys and data. Keys carry an environment prefix (for example pk_test_ and pk_live_), and an environment refuses keys from the other one.

Next steps


Did this page help you?