Every character has two balances: cash carried by the character and money held in the bank. Use /balance whenever you need to check both. Jobs and player services may pay into cash, while depositing and withdrawing let you decide how much to carry.

Understand cash and bank money

Cash and bank money are separate:

  • Cash is the balance used for a nearby payment to another player and for activities that charge carried money.
  • Bank money stays in your bank balance until a supported activity uses it or you withdraw it.
  • Moving money into the bank reduces cash by the same amount. Withdrawing does the reverse.

The money shown by /balance is the server’s current balance, not an amount supplied by your game client. The cash display on the HUD follows that server balance, but /balance is the clearest way to review cash and bank together.

Deposit or withdraw money

Deposits and withdrawals work at the configured bank counter. Its map marker uses the dollar-sign bank icon; use that established location rather than assuming every decorative cash machine supports banking.

  1. Go to the configured bank counter and stand close enough to use it.
  2. Use /bank to move the chosen amount from cash into the bank, or /withdraw to move it from the bank into cash.
  3. Wait for the result message. A successful transaction shows the amount moved and your resulting cash and bank balances.
  4. Use /balance if you want to verify them again before your next purchase or payment.

The command is refused before moving money if you are away from a banking location, enter an invalid amount, or lack the source funds. Correct that reported condition before trying again. A later transaction failure never represents a partial deposit or withdrawal, but an interrupted response can make it unclear whether the whole movement completed; check the balances before doing anything else.

Pay another player in cash

A player payment is a consent offer, not an instant handoff.

  1. Meet the intended recipient in character and remain nearby in the same in-game space.
  2. Use /pay to offer the chosen cash amount to that player.
  3. Check that the waiting message identifies the intended payment. The recipient sees who is paying, the amount, and the keys for accepting or declining.
  4. The recipient accepts or declines the offer. Unanswered offers expire, and a recipient can have only one pending offer at a time.
  5. Treat the payment as complete only when the success messages confirm that one player paid and the other received the money.

The game checks the scene again when the offer is accepted. Both characters must still be available and close enough, and the payer must still have the cash. If someone walks away, disconnects, spends the money, declines, or lets the offer expire, the payment does not complete. Restore the conditions and create a new offer only if both players still want the exchange.

Sending the offer is not proof of payment. Do not hand over goods or conclude the roleplay transaction until the payment success message appears.

What happens when a transaction completes

Money movements are recorded as balanced transactions: the source loses exactly what the destination gains. The server updates spendable balances only after it can safely complete the whole movement. This gives staff a durable transaction record to investigate without relying only on screenshots or the HUD.

After a successful deposit or withdrawal, the result line includes both balances; after a player payment, each participant can use /balance to check their own side. A clear validation refusal leaves the balances unchanged.

Recover from an unclear outcome

If lag, a disconnect, or a missing message makes the outcome unclear:

  1. Do not immediately repeat or reverse the transaction.
  2. Use /balance to check the character’s authoritative cash and bank balances.
  3. For a player payment, ask the other participant to check their own balance before either of you sends another offer.
  4. Retry only after a clear pre-transaction refusal, or when the checked balances make it clear that the movement did not occur.
  5. If you did not know the earlier balances, or the balances and visible result still do not explain what happened, keep the approximate time, amount, and other character’s name for a support report instead of guessing.

This avoids duplicate payments after a delayed or ambiguous response. See Offers and incomplete transactions for the distinction between consent and final settlement. Use the generated command panel for current command syntax. See Finding work for established ways to earn money, Inventory and items for item handovers, and Commands and help when a command form or prompt is unclear.