Skip to content
Rydlnk

How it works

Money in at the top. A seat, a receipt and a journal line at the bottom.

Three mechanics do all the work: a credit ledger that never mutates a balance, corridor pooling that bills you per seat, and a roster feed that means nobody books anything daily.

Credits

A credit is a unit of account, not a coupon.

Everything is double-entry. A wallet balance is a projection over entries, never a column somebody updates — which is what makes month-end reconcile without an argument.

  1. 01

    You fund a float

    One purchase order, one invoice, one ledger entry. The float is company money sitting in a wallet Rydlnk holds but doesn't own.

  2. 02

    Rules allocate it

    Credits move from the float to employee wallets on a schedule you set — every Monday, on roster publish, or once. Each movement names a source, a destination and a reference.

  3. 03

    Seats consume it

    At the boarding PIN, credits move from the employee's wallet to a seat. That entry is the invoice line, the benefit record and the audit record.

  4. 04

    The remainder returns

    Unspent credits expire back to the float on your cycle. A leaver's wallet is frozen on the termination webhook, not overnight.

Split tender, worked through

An employee books a 41 miles drop-off on a corridor capped at 25 miles. Policy covers the first 16 credits; the difference comes off their own balance. They're told before the trip confirms, and the seat still gets one manifest entry.

Seat price, 41 miles
8 cr
Company policy cap
−6 cr
Employee balance
−$2.10
Pooling

You pay for the seat, not the vehicle.

On a pooled corridor your staff share the run with approved employers going the same way. You're billed per seat occupied. On an exclusive corridor you charter the whole vehicle and buy every seat on it, full or not.

4/5

corridors open to pooling

67%

average seat fill across live corridors

2 cr

back to your float per spare seat sold

What other employers see

An occupancy count. Not a name, not a department, not a home address. Authorization is scoped per seat at the query layer, so asking for a trip you partly own returns your seats and a number.

Why the price never moves

Seat price is fixed per corridor and time band — not the vehicle cost divided by whoever showed up. Another employer's no-show can never change what you pay. Rydlnk carries that yield risk.

Roster sync

Nobody books a trip. The roster does.

Your shift system already knows who works when and where they live. Rydlnk reads it, clusters people into corridors, and publishes manifests — so the daily booking step that kills every staff-transport scheme simply isn't there.

Shifts in

A nightly pull plus a webhook on roster publish. 412 shifts becomes 96 trips across five corridors.

Manifests out

Published to drivers and riders with a lock four hours before departure. After the lock, a no-show is charged to the cost center.

Leavers out

Terminations arrive on a webhook, not the nightly job. A leaver who rides on Monday morning is money out of the float.

See it against your own roster.

Send a week of shifts and the cities your staff live in. We'll show you the seats you're currently paying for twice.