How fast does support respond?
In-app tickets are the fastest channel — first response typically within minutes, 7×24. For complex issues involving upstream checks we state a clear ETA.
How fast support responds is really two questions stacked together: how quickly someone picks it up (first response), and how quickly it gets fully closed out (resolution). First response follows the same rhythm for every ticket; closing it out depends on whether the matter needs verification with the upstream issuer. But before you reach out to support, it's worth knowing that the two most common types of problems — failed payments and top-ups being credited — usually don't require waiting for a person: the specific reason a charge failed is written in the transaction details on the card details page, and the top-up fee and each network’s crediting time are shown on the top-up page. These self-check paths are visible instantly and are often faster than going through an agent.
First, sort it out: which problems don't require waiting for support, and which must go through a ticket
| Your problem | First step (most need no support) | Do you need a ticket? | Expected timing |
|---|---|---|---|
| Subscription / charge declined | Open the transaction details on the card details page and check the reason for failure (insufficient limit / insufficient balance / card details entered incorrectly) | With a clear reason you can fix it yourself — no ticket needed | Instant self-check |
| Charged $20 but it shows over $21 | Factoring in sales tax in some US states, a $20 plan usually comes to $20–22 actually paid | Not needed | Instant self-check |
| Top-up still not credited | Usually 1–5 minutes on TRC20, 1–30 minutes on other networks (counting from when your exchange shows the withdrawal as Completed) | If it is past the time shown on the top-up page and still not credited, send the transaction hash (TxID) or a screenshot of the withdrawal to live support — no ticket needed | Live support checks the payment records manually |
| Wrong network / wrong token | A transfer on the wrong network or in the wrong token may not be credited — first check the network and token in the withdrawal record on your exchange | Send the transaction hash (TxID) to live support for an investigation | Support will help investigate but cannot guarantee recovery |
| Freeze appeal / account closure review | Submit a ticket for manual review | Ticket required | Replied within the verification timeframe after first response |
| Prepayment refund / closing a single card | Self-service in the account centre | No ticket needed | Refunds: available once the 24h quiet period has passed, paid out automatically after the cooldown; up to 72h if a risk review is triggered |
First response is a uniform rhythm; resolution time depends on whether upstream verification is needed
All tickets are handled 24/7 and usually get a first response within a few minutes, and this step doesn't slow down just because a problem is complex. What really varies is the time to close out: purely platform-side issues (checking an order, confirming that a top-up was credited, changing a billing address) can be resolved in a single pass; issues that require verification with the upstream card issuer are subject to external constraints — for example, unsettled in-flight transactions on a card have to wait for the merchant to complete settlement (typically 1-7 days, up to 30 days for cases such as hotel pre-authorisations). For timeframes like these we tell you clearly upfront when we take on the ticket, rather than making you ask repeatedly. Giving you a specific timeframe is itself part of the response.
Include these items in your ticket for the fastest resolution
- Describe the symptom in one sentence: the type of problem plus when it happened.
- For top-up issues: include the transaction hash (TxID) or a screenshot of the withdrawal — it is how we locate a missing credit.
- For payment failures: include the last digits of the card (support can't see the full card number) and the failure reason from the transaction details.
- State the self-checks you've already done and your conclusions to save back-and-forth.
- When helpful, attach a screenshot of the screen — it aligns us faster than a text description.
On-site support tickets are the preferred and fastest channel: they go straight into the processing queue and leave a fully traceable record, so the status and outcome of your issue are always documented. RDVCC doesn't yet have a standalone app, but the ticket system and all features are optimized for mobile browsers on the web, so you can submit and follow up right from your phone.