Security and access statement

Account access

Use a unique operator ID and a strong passphrase. Keep credentials private and avoid reusing a passphrase from another service. Do not enter real financial credentials or sensitive personal information into the demonstration.

A connected production service controls account access. Creating or signing into a local demonstration account does not establish an account with a payment provider.

Wallet boundaries

Wallet details and recent activity are restricted to the active operator’s permitted workspace. Changing a destination does not grant access to another operator’s wallet or records. Access is checked by the service; a visible link or control alone does not establish permission.

Payment confirmation

Preparation, approval, and execution are separate actions. Review the instruction before execution and use the confirmed response to determine the outcome. A preview, replay, or temporary loading state is not proof that money has moved.

Session responsibilities

Sign out when you finish, particularly on a shared device. Closing a tab does not necessarily end a session. When a session expires or the service rejects access, sign in again through the workspace.

Production access should take place over a secure connection. If you are unsure that a page belongs to Rail, avoid entering credentials until the address has been checked.

Assurance scope

This statement describes access behavior and user responsibilities. It is not an independent security assessment, regulatory certification, or guarantee that every risk has been eliminated. Production payment safeguards and account policies require assessment of the connected service.