Rail.Open workspace
The public collection

02 / Payments

Payment lifecycle

How to prepare, approve, execute, and follow a payment from the operator’s perspective.

3 min readEdition 1.0Reviewed

Prepare an instruction

Choose an existing destination wallet and enter an amount in INR. Check the destination and amount before requesting approval. Payment controls are available only after the workspace has connected to an accessible wallet.

Review the approval

An approval records the proposed payment. It is not confirmation that a transfer has completed. Review the displayed reference, destination, and amount before continuing.

In the local demonstration, approval does not debit the wallet or guarantee that funds will remain available. Execution can still be rejected if the instruction is no longer valid or the available balance is insufficient.

Request execution

Use the execution control for the active approval. Treat the payment as completed only when the workspace receives a confirmation from the service. If a request fails or the connection is interrupted, review the displayed result and refresh the record before preparing a replacement instruction.

A retry of the same confirmed instruction in the demonstration returns its existing result rather than making another transfer. A new instruction is a separate payment and requires its own review.

Follow the record

The workspace displays the confirmation reference and recent activity associated with the active wallet. Refresh the workspace to read its latest available state. A recent-activity list is not a substitute for a financial statement or settlement record.

Understand the animation

Previewing the six-stage engine does not submit a payment or change a balance. A replay illustrates a confirmed response; its speed and stage sequence do not report live processing times. The approval details and service response remain the authoritative interface results.

If a payment needs attention

Check the destination, amount, balance, and any displayed message. Do not assume completion from an animation alone. When the service cannot confirm the result, the interface should be treated as unresolved until the record can be checked.