Service overview

Purpose

Rail presents a considered approach to payment control: prepare a clear instruction, approve it, execute it, and follow its record. The public site introduces that experience; the operator workspace lets visitors explore it through a demonstration.

Current service scope

The demonstration uses simulated wallets and balances. It does not move real money, settle payments, or provide a bank account. Rail is not presented here as a licensed bank or regulated payment institution.

Production account access depends on a separately configured service. When that service is unavailable or has not been configured, account and payment actions cannot proceed. The public introduction and documentation remain available independently.

Operator experience

An operator can view an accessible wallet, choose a destination, prepare an amount, review an approval, and request execution. Recent activity provides a way to follow the result. A payment instruction and a completed payment are different states; the interface labels them separately.

Public information

These documents describe visible behavior, user responsibilities, and current limits. They do not publish private account information or implementation specifications. The scope is intended to help visitors understand what they can use and what they should expect.

Reading the collection

Start with the payment lifecycle for the operator journey. Read the security and access statement, data handling notice, and operating limits before using the workspace.