Turnkeyxgaming

Guide · Wallet

Showing a currency is not the same as settling in it

Some lobbies display amounts in the player's local currency and settle the game in a wallet currency such as EUR or USD. That can be legitimate. It is a dispute factory if the rate and the settlement currency are hidden.

7 min readUpdated By the Turnkeyxgaming team

Both numbers, or neither conversion

If you convert for display, show the settlement amount and the display amount, and show the rate and who set it. A chip that only says a local figure will be screenshotted, and the wallet line will show a different number. Support cannot win that conversation. If you do not want the complexity, launch and display in the same currency and let the cashier convert deposits beforehand.

The game client will render the currency you launched. Do not launch in EUR and overlay a second currency inside a webview. The client and the overlay will drift. One source of display, and the wallet as the source of settlement, is the whole design.

If you do convert for display, the rate, who set it, and both amounts have to be on the screen the player will screenshot. Support cannot reconcile a chip that showed only a local figure with a wallet line in the settlement currency. The cashier is the right place to convert a deposit into the settlement currency before launch, if you would rather not maintain two numbers at all. Pick one design and use it on history as well as on the chip. A history row in a third format is a new dispute.

Three ways to show money, one of which drifts

Display and settlement may differ. They may also be the same currency. An overlay that invents a third figure will not match either source when the rate moves.

DesignWhat the player seesWhat a dispute uses
Launch, display and settle in one currencyThat code, on the chip and in history.The wallet line, which shows the same numbers. Conversion, if any, already happened in the cashier.
Display converted, settlement unchangedBoth amounts, the rate, and who set the rate.The settlement amount on the wallet line, plus the rate you published. One of them alone will look like a short payment.
A webview overlay on a client that already has a currencyWhichever layer last repainted.Nothing reliable. The client and the overlay update on different clocks.

Pick one design

  1. 01

    Same currency

    The simple path: launch, display and settle in one currency.

  2. 02

    Or show both

    If you convert for display, show rate, source and both amounts.

  3. 03

    No overlay

    Do not paint a second currency over a client that already has one.

A screenshot of the chip will be the player's evidence

If the chip shows only the familiar local figure, that is the number they will send to support. The wallet will show the settlement amount. Put both on screen, with the rate, or do not convert the display.

Follow one euro through five screens

A player deposits in a local currency. The cashier converts at a rate it stamps, the wallet holds euros, the launch is in euros, and a bet of 1.00 wins 2.40. The chip shows both figures with the rate underneath. Four days later the player requests a withdrawal and the rate has moved. Nothing in that sequence is wrong, provided every screen can be rebuilt later from stored fields.

Write down what each one holds: the cashier receipt with the rate and the moment it was applied, the chip with the settlement amount and its local equivalent, the history row with the same pair, the statement with the settlement figure and the rate used, and the support view with all of it. The statement is where builds usually fall short, because a different team generates it from the one that built the chip.

The stall is nearly always the same. The display rate is applied inside the client or a lobby overlay and written nowhere, so a week later nobody can reproduce the number in the screenshot. The argument then becomes about the player's memory instead of about a record. If a figure is worth showing, it is worth storing beside the round that showed it.

Five places a money figure appears, and what has to sit beside it

ScreenCurrency shownWhat to store beside it
Cashier receiptLocal amount, and what was credited in the wallet currencyThe rate, its source, and the timestamp
Game chipSettlement figure, plus the local equivalent if you convertThe same rate and the same timestamp
History rowThe pair, never a third formatThe round id, so chip and row can be compared
Monthly statementSettlement figure as the record, local figure as a renderingThe rate used, or an explicit note that none was applied
Support viewBoth, with the launch currency namedThe launch currency and the rate source, with no editable second field

FAQ

Questions operators ask

Who owns the FX rate?

Whoever converted the money. If that is your cashier, you publish the rate. The game studio should not be converting again inside the round.

Who publishes the rate when the chip shows a converted figure?

Whoever performed the conversion. If that was your cashier or your display layer, you show the rate and stand behind it. The studio should not convert again inside the round. A rate that exists only in the overlay cannot be reconstructed a week later.

Can history stay in the settlement currency while the chip shows the local one?

Only if the chip also shows the settlement amount. A history page in one code and a chip in another, with no rate beside either, is the dispute. Use the same pair of figures in both places.

Which rate applies if it moved between the bet and the withdrawal?

The rate on the conversion that actually moved the money, which is the cashier's, and the receipt is its record. The chip shows a rendering of a bet already settled in the wallet currency. Decide that once and print it on both screens, or two teams will answer it two ways in the same week.

Can we keep only a local-currency figure per round to simplify reporting?

You can render one, but storing only that loses the figure the wallet settled. Reporting, disputes and the daily file all start from the settlement amount. Keep that as the record and treat the local figure as a view with its rate attached, so a later reader can move between the two unaided.

Keep reading

Related pages

  • Guide · WalletSeveral currenciesHow to launch a game in a chosen wallet currency, why the game must never invent a conversion, and where the FX decision belongs.Read
  • Product · WalletWalletBalance, bet, win and rollback on one seamless wallet: idempotent transaction ids shared by casino games and sportsbook alike.Read
  • Product · PaymentsPaymentsDeposits and withdrawals stay with your payment firms. The aggregator never moves SEPA, cards or USDT and never holds player funds.Read
  • Guide · SupportRound historySupport can search a disputed round by id, stake, credit and status. A player's screenshot is not a lookup key; the round id is.Read

Get a written quote and sandbox access

Tell us your licence, target markets and products. You get the GGR rate in writing, the studio list for your markets and sandbox credentials.

Telegram @turnkeyxhub WhatsApp Email Contact form