Skip to content

Payments · Beta

PayFac you can leave.

Embed charges for your customers and merchants. Your name on the statement. Settlement you can open.

pnpm add @vortex-api/payments-sdk
import { createVortex, getMerchantAccountSettlements } from "@vortex-api/payments-sdk/2026-08";

// vb_test_ key = sandbox
const vortex = createVortex({
  apiKey: process.env.VORTEX_API_KEY,
});

const { data } = await getMerchantAccountSettlements({
  client: vortex,
  path: { merchantAccountId: "mer_…" },
});

Install an SDK. Create a charge against sandbox.

Minutes
to a sandbox key
0
API operations
0
SDKs

How it works

Sandbox key to first settlement in one sitting.

  1. 01

    Get a key

    Open the dashboard. Copy a vb_test_ key. No sales call for sandbox.

  2. 02

    Charge

    SDK or curl. Merchants are API objects your platform owns.

  3. 03

    Inspect settlement

    Gross, fees, net — on the settlement object finance can read.

Who buys this

If you take money for customers, this is for you.

Four seats at the table. One API.

  • Founders

    Launch payments without becoming a payments company. Keep the merchant relationship. Keep the option to leave.

  • Developers

    Charges, refunds, disputes, merchants, webhooks — OpenAPI and versioned SDKs, not a PDF and a hope.

  • Engineering managers

    Ship a money path the team can own. Readable settlement. Docs that include migrate-away.

  • Business & ops

    Statement branding is yours. Fee lines are explicit. Sandbox numbers match the shape of production objects.

Why Payments

Platform money without the black box.

Built for products that take payments — SaaS, marketplaces, platforms.

  • Sub-merchants as objects

    Onboard merchants in the API. They settle under your PayFac — not as a mystery spreadsheet.

  • Inspectable settlement

    Every closed settlement shows gross, fees, and net. Your eng and finance teams see the same truth.

  • Webhooks you can run locally

    Signed events. Forward to localhost while you build. Same contract in sandbox and beyond.

  • Leave-able by design

    We document migrate-away. Lock-in is a product failure — not a strategy.

Use cases

Where teams put Vortex Payments.

  • SaaS that invoices customers

    Charge cards, refund cleanly, settle under your brand. Billing product sits on the same key.

  • Marketplaces & platforms

    Merchants as API objects. Platform fee and processing fee visible on settlement.

  • Product-led startups

    Founder + one eng. Sandbox in minutes. Ship the money path before you hire payments specialists.

  • Teams replacing a bolt-on

    Tired of a payments vendor that owns the customer relationship. Reclaim statement branding.

Straight talk

What we claim — and what we don’t.

Beta means sandbox-first. We sell the path, not theater.

  • Sandbox key in minutes. Self-serve.
  • 173 OpenAPI operations. Three SDKs: TypeScript, Python, Go.
  • Your name on the statement. Settlement is inspectable.
  • We are not an agent wallet. Natural covers agent money — Vortex is PayFac for your customers.
  • Tax calculation is separate; we do not claim MoR tax liability.

Get a sandbox key.

Founders open the dashboard. Devs open the docs. Same key either way.