Built exclusively on Hedera Hashgraph

Stablecoin payroll,
settled in seconds.

PayoutRails turns a payroll run into one atomic, instantly-final on-chain event. Pay remote contractors across Argentina, Nigeria, Vietnam and the Philippines for ~$0.001 a transfer — with an immutable receipt for every payout.

$0.001
Network cost per transfer
4s
aBFT settlement finality
8%
TradFi fee leak removed
Hedera Token ServiceConsensus Service receiptsaBFT finality · 3–5s~$0.001 per transferMirror Node verificationNon-custodial by designHSCS milestone escrowOpen receipt standardHedera Token ServiceConsensus Service receiptsaBFT finality · 3–5s~$0.001 per transferMirror Node verificationNon-custodial by designHSCS milestone escrowOpen receipt standard
The Problem

Paying remote freelancers is slow, costly, and unverifiable

Cross-border freelancer payments fail on three compounding axes — and every freelancer in an emerging market feels all three at once.

01

The fee leak

FX margin + transfer fee + local cash-out fee runs 4–8% of every USD payout. On a $1,000 invoice, that is $40–80 lost — every contractor, every month.

02

The settlement delay

Correspondent-bank rails take 3–7 business days to clear. Contractors finance their own cash-flow gap; weekly or milestone pay is impossible without drowning in fees.

03

The reconciliation burden

Neither side has a shared record. Employers rebuild payroll from bank statements for auditors; contractors reconstruct income from screenshots for tax filings.

The Solution

A payroll run becomes one atomic on-chain event

Funded → Settled → Receipt
1

One signed event

Fund a batch, and a single HTS transaction settles every contractor at once — atomic, all-or-nothing.

2

Receipt as a network fact

Each payout appends a consensus-timestamped message to the employer's HCS topic. No bookkeeping intermediary.

3

Trustless verification

Contractors confirm full payment history straight from the public Mirror Node REST API.

Why Hedera

This could not be built on any other chain

Four Hedera-native properties — and PayoutRails is load-bearing on all of them.

H
0

USD-denominated fixed fees

An HTS transfer costs ~$0.001 regardless of congestion. On an EVM chain a percentage-of-gas fee makes the $50-payout segment structurally unprofitable.

H
0

Native HCS consensus timestamps

Receipts are a first-class network service, not a contract-emitted log. That is what removes the bookkeeping intermediary.

H
0

aBFT finality in 3–5 seconds

Funded → settled → receipt written completes before the employer closes the tab. Finality is the product promise.

H
0

Atomic HTS batching

A payroll run is all-or-nothing by nature. HTS multi-party transfers express that natively — no orphaned transfers.

Features

Everything a payroll rail needs  nothing it doesn't

Built for the three sides of the network: employers, contractors, and the wider Hedera ecosystem.

Employers

One-click batch payroll

Upload a contractor list, fund once, settle the whole batch atomically through Hedera Token Service. All-or-nothing — never a half-finished run.

Employers

Weekly & milestone cadence

Because a payout costs ~$0.001, paying weekly or per-milestone costs essentially the same as paying monthly.

Compliance

Audit-ready receipts

Every payout writes a consensus-timestamped message to the employer's HCS topic. Export a tamper-evident payroll history for any period.

Contractors

Paid in seconds, non-custodial

Contractors hold their own keys. Funds are spendable on arrival — not in 3–7 days — and PayoutRails never holds contractor capital.

Contractors

Independently verifiable

The contractor portal reads straight from Hedera Mirror Nodes. Payment history is provable without trusting PayoutRails' servers.

Ecosystem

Open receipt standard

The payoutrails.receipt.v1 HCS schema is published openly so any Hedera payments project can read and write the same format.

The Flow

Five steps, start to settled

1Step 1 / 5

Fund a batch

The employer uploads a contractor list and funds the run in a regulated stablecoin — USDC.h, AUDD, or a Stablecoin Studio partner stable.

2Step 2 / 5

Settle atomically

A single HTS transaction pays every contractor at once. If any leg is invalid, the whole batch fails cleanly.

3Step 3 / 5

Write the receipt

Each payout appends a structured, consensus-timestamped receipt to the employer's dedicated HCS topic.

4Step 4 / 5

Pay & verify

Contractors receive funds in a non-custodial wallet and verify full history against the public Mirror Node REST API.

5Step 5 / 5

Cash out locally

Integrated, licensed off-ramp partners convert stablecoin to local fiat inside each corridor.

$0T

Digital payments market by 2027

0+

Target monthly on-chain transactions

0

Target active contractor wallets

0

Launch corridors at go-live

Tokenomics

RAILS  a token funded by real payroll volume

PayoutRails works fully without a token. RAILS aligns incentives across the network, with a programmatic buyback funded by real platform revenue.

Token Allocation

1,000,000,000 RAILS · fixed supply
Community & Adoption Incentives0%
Ecosystem & Off-Ramp Partnerships0%
Team & Advisors0%
Treasury & Operations0%
Liquidity & Market Operations0%
Hedera / Thrive Strategic0%

Fee rebates

Employers paying platform fees in RAILS get a reduced effective rate — demand tied directly to real payroll volume.

Staking for premium

Stake RAILS to unlock branded payment pages, merchant API access, higher batch limits and advanced reconciliation.

Contractor loyalty

Contractors paid through PayoutRails accrue RAILS rewards, redeemable for off-ramp fee discounts.

Governance & buyback

Holders steer fee schedules and corridor priority. A defined share of revenue funds a transparent on-chain buyback.

The default payroll rail
of the Hedera ecosystem.

Stablecoins that settle in seconds across continents — that is Hedera's stated 2026 priority, and it is exactly what PayoutRails ships.

Read the Full Whitepaper

Tip: click a button — that burst is mo.js.