Connect your billing.
Activate the brain.

Architecture Overview

ZenoPay is a tenant-based platform. Each business that connects is a tenant. Each tenant has its own customers, subscriptions, guardrails, vault, and brain instance. Data is fully isolated by Row Level Security at the database layer.

Data Isolation Model

All tables are protected by Row Level Security. A tenant can only read and write their own data. The cross-tenant fraud signal network shares anonymized BIN/IP/device hashes only — no customer PII ever crosses tenant boundaries.

What ZenoPay Does

Once connected, ZenoPay operates autonomously across your customer base. These are the systems that activate after connection.

Quickstart: Connect in 6 Steps

From zero to first autonomous decision. Estimated time: 30–60 minutes depending on your existing billing setup.

curl https://app.zenopay.ai/api/tenant \
  -X POST \
  -H "x-intake-api-key: YOUR_INTAKE_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Acme Corp",
    "slug": "acme-corp",
    "platform_name": "Acme Billing",
    "support_email": "billing@acme.com",
    "plan": "standard"
  }'

# Response
{
  "success": true,
  "tenant_id": "a1b2c3d4-...",
  "slug": "acme-corp",
  "note": "Tenant created in SHADOW_MODE. Disable via guardrail config after testing."
}

curl https://app.zenopay.ai/api/billing/plans \
  -X POST \
  -H "x-intake-api-key: YOUR_INTAKE_KEY" \
  -d '{
    "action": "create",
    "tenant_id": "YOUR_TENANT_ID",
    "name": "Scale",
    "slug": "scale",
    "amount_cents": 9900,
    "currency": "usd",
    "interval": "monthly",
    "features": ["Multi-rail routing", "Fraud detection"],
    "usage_limit": 10000
  }'

curl https://app.zenopay.ai/api/vault/tokenize \
  -X POST \
  -H "x-intake-api-key: YOUR_INTAKE_KEY" \
  -d '{
    "tenant_id": "YOUR_TENANT_ID",
    "customer_id": "cust_abc123",
    "rail": "stripe",
    "processor_token": "pm_1NXxx2...",
    "last4": "4242",
    "brand": "visa",
    "expiry_month": 12,
    "expiry_year": 2027,
    "is_default": true
  }'

# Supported rails: stripe, authnet, adyen, braintree, gocardless,
# checkout, crypto, upi, alipay, wechat_pay, unionpay, pix, mpesa,
# 2c2p, promptpay, apple_pay, google_pay

curl https://app.zenopay.ai/api/billing/subscriptions \
  -X POST \
  -H "x-intake-api-key: YOUR_INTAKE_KEY" \
  -d '{
    "action": "create",
    "tenant_id": "YOUR_TENANT_ID",
    "customer_id": "cust_abc123",
    "plan_id": "YOUR_PLAN_ID",
    "trial_days": 14,
    "metadata": { "source": "web", "campaign": "q2-launch" }
  }'

curl https://app.zenopay.ai/api/agent/guardrail \
  -X POST \
  -H "x-brain-secret: YOUR_BRAIN_SECRET" \
  -d '{
    "tenant_id": "YOUR_TENANT_ID",
    "name": "shadow_mode",
    "value": "false",
    "reason": "Verified brain decisions in audit log. Ready to go live."
  }'

# The brain is now live. First autonomous decision incoming.

Authentication

ZenoPay uses two keys. Both are set in your Vercel environment variables and never returned after creation.

Billing API Reference

Migrating from Stripe Billing

If your application already uses Stripe Billing (Stripe Subscriptions, Stripe Customer Portal), you can connect ZenoPay alongside Stripe without migrating away from it. ZenoPay operates as an intelligence and routing layer on top of your existing Stripe setup.

Option A — ZenoPay alongside Stripe (recommended for existing customers)

Keep Stripe as your primary rail. ZenoPay adds routing intelligence, churn scoring, and the autonomous brain without touching your existing checkout flow.

// After your Stripe PaymentMethod is created in the browser...
const { paymentMethod } = await stripe.createPaymentMethod({ type: 'card', card })

// Send processor token to ZenoPay vault (server-side)
await fetch('https://app.zenopay.ai/api/vault/tokenize', {
  method: 'POST',
  headers: {
    'x-intake-api-key': process.env.INTAKE_API_KEY,
    'Content-Type': 'application/json'
  },
  body: JSON.stringify({
    tenant_id: process.env.ZENOPAY_TENANT_ID,
    customer_id: stripeCustomer.id,
    rail: 'stripe',
    processor_token: paymentMethod.id,  // e.g. pm_1NXxx2...
    last4: paymentMethod.card.last4,
    brand: paymentMethod.card.brand,
    expiry_month: paymentMethod.card.exp_month,
    expiry_year: paymentMethod.card.exp_year
  })
})

// ZenoPay now tracks this customer, scores their churn risk daily,
// and will intervene autonomously if they show at-risk signals.

Option B — Full ZenoPay billing (new customers)

For new customers, use ZenoPay's billing API directly. ZenoPay manages the subscription lifecycle, routes charges across all 15 rails, and handles all dunning logic. Stripe becomes one of many possible rails rather than the billing engine.

Shadow Mode

Shadow mode is a safety mechanism for onboarding. When enabled, the brain reasons through every decision and logs what it would have done — but executes no real charges, rail switches, or subscription changes.

Use shadow mode to:

• Verify the brain is making sensible decisions for your customer base
• Check that webhook events are arriving and being parsed correctly
• Confirm rail scoring matches your expectations for your regions
• Review guardrail configurations before real money moves

Reading the audit log in shadow mode

curl "https://app.zenopay.ai/api/compliance/audit?tenant_id=YOUR_TENANT_ID&limit=20" \
  -H "x-intake-api-key: YOUR_INTAKE_KEY"

# Each entry includes:
# - decision_type: charge | retention | rail_switch | escalate | etc.
# - reasoning: Natural language explanation of the decision
# - guardrails_checked: List of guardrails validated
# - confidence: 0.0–1.0
# - was_blocked: Whether the guardrail engine blocked the action
# - shadow_mode: true if this was a simulated decision