USD payment troubleshooting: when the credited figure is not the one you sent

Which causes are on the sending side?

A network fee taken out of the amount, which is why Sportsbet.io says its minimums are the amount it receives after network fees. A provider's share on a card purchase, which BetFury's example puts as high as 14.6% on a small one. And an amount under the minimum: Rollbit says deposits below its minimum will not credit and cannot be recovered by support, and Stake says it cannot process crypto deposits under a cent automatically and asks for a message to support.

Which causes are on the operator's side?

The conversion at deposit, since Duelbits says the rate at the time decides how many of its coins arrive. The display currency, which can make a correct balance look wrong. And a stage delay, which BetFury says in rare cases can be 24 to 72 hours for a deposit.

What should be gathered before writing to support?

The unit and amount sent, the method, the time, the unit and amount credited, the display currency, and the transaction hash if the deposit was a transfer. Duelbits has an article on finding a transaction hash; most operators have an equivalent. A message that carries these lets support answer in one reply.

When to wait and when to write

Wait when the stage is still running. Roobet says a purchase made in its cashier usually arrives within minutes and may take up to 30; BetFury says a deposit may in rare cases take 24 to 72 hours. Those are figures for the stage they describe, so decide first which stage you are in.

Write when the stage has plainly ended and the figure still does not fit: the transfer shows as confirmed on the network, or the card payment shows as settled, and the balance has not moved. Include the items above and say which stage you believe has stalled.