paylode
Payment infrastructure for platforms

The payment layer
platforms build on.

Board unlimited merchants, route across processors like TSYS and Fiserv, and give every merchant a virtual terminal, reporting, and a clean API — without ever holding their funds.

Get started →See features
paylode/ops · terminal
Amount
$42.00
•••• •••• •••• 1111
12 / 30 ···
Charge $42.00
Result
$42.00succeeded
pay_BQQu… · phonypay
Features

Everything a platform needs to process payments

Board unlimited merchants

Onboard merchants in one call. Each gets an isolated profile, scoped keys, and their own processor credentials — you stay the orchestration layer, never the custodian of funds.

Processor-agnostic routing

Route payments across TSYS, Fiserv, and a growing connector set. Pin a connector or let Paylode decide. Swap processors without touching merchant code.

Virtual terminal

A full keyed-entry terminal for every merchant: authorize, capture, void, and refund — with the result, connector, and status surfaced in real time.

Reporting & insight

Per-merchant processing summaries — captured volume, transaction counts, success rates — plus a drill-in transaction ledger for you and your merchants.

Card-on-file & recurring

Vault a customer’s card on first charge, then bill it off-session — no card data re-entered. Saved methods per customer, ready for repeat and recurring payments.

Signed webhooks

Subscribe a URL to payment, refund, and dispute events. Every delivery is HMAC-signed and retried with backoff, so your systems stay in sync automatically.

⟨⟩

Developer-first API

A clean REST API with an OpenAPI spec and generated keys. Your merchants integrate server-to-server with an x-api-key — no engine internals exposed.

Resellers & role hierarchy

Built for layered distribution: admins see everything, resellers manage their own book of merchants, and each merchant runs their own account. Scope and isolation at every tier.

How it works

From zero to processing in three steps

01

Board a merchant

Create a merchant from your dashboard or API — Paylode provisions everything underneath.

02

Attach a processor

Add the merchant’s TSYS / Fiserv credentials (or a sandbox connector to test). Stored encrypted, never exposed.

03

Process payments

Use the virtual terminal or the API. Authorize, capture, refund — with reporting out of the box.

Start orchestrating payments.

Board your first merchant in minutes. Test with a sandbox connector — no processor account required.

Open the dashboard →