Frequently asked questions

Account balance is credited when you verify a USDT TRC20 deposit to our configured deposit address. It is used for cards and withdrawals. The generated TRON wallet is standalone: we do not store its private key, and it is not tied to your card product.

No. That page is an on-chain tool. If you are signed in, you can save transfer history to your profile for convenience. Card spending runs through the card issuer network and your card balance.

Top up your account balance first, then purchase a plan from the Cards page. The plan price is debited from your balance. The card starts at $0 on-card until you top it up.

You move money from your RombPay account balance onto the card. A top-up fee (shown per plan) applies; only the net amount is credited to the card. The issuer requires a minimum of $50.00 credited to the card after fee (so you must debit a bit more from balance). You cannot exceed the plan spending limit.

On the Cards page, use View code next to Card details. RombPay fetches one-time confirmation codes from the card issuer (Pay2.House) — the same OTPs that would normally arrive by SMS or email for online checkout or wallet tokenization. The static 3DS password (if any) is shown under Card details.

Each active card has a monthly fee listed in the catalog. On the first day of each month we attempt to collect the total from your account balance, then from card balances if needed. If payment fails, cards may be canceled for non-payment.

You submit a request with a TRON address and amount. The balance is debited immediately. Operators process, complete, or reject requests. Rejections refund your balance. This is not an instant on-chain pipeline.

Referral bonuses are paid on verified top-ups and card purchases along a five-level upline chain. Percentages are shown in the Referrals section of the dashboard.

Yes. Server-side integrations use client API keys and the REST surface documented on /docs (including webhooks where configured). The API is separate from the browser-only wallet generator.

The Top up page lists supported methods (for example USDT TRC20 and selected USDC networks). Always match the exact asset and chain shown — wrong networks can mean permanent loss.

Common reasons include wrong token or network, an address that is not your assigned deposit address, insufficient confirmations, or a hash that was already processed (top-up verification is idempotent).

No. The generated wallet is independent and non-custodial on your side. Your dashboard deposit address is provisioned for balance credits after hash verification.

Signed-in users browse the live card catalog in the dashboard. Monthly fees, plan prices, and card top-up percentages come from that catalog and backend configuration.

On-chain USDT (TRC20) needs bandwidth and energy. RombPay’s transfer tooling can route through pooled energy so typical network cost is lower than naive sends — exact savings depend on chain conditions.

Automation is via your own treasury sending funds to the deposit address, then calling the verification endpoint/API with the transaction hash. There is no substitute for correct on-chain execution.

Treat dashboard-issued client API keys like passwords: they authorize your server to call permitted endpoints (for example via X-Client-Api-Key). Never embed them in public frontends; rotate immediately if a key leaks.

No. Card spend uses issuer rails and the card balance you load from your RombPay USD account balance (after fees). Your standalone TRON wallet is unrelated unless you manually bridge funds through deposits.

Withdrawals are operator-processed queues, not instant on-chain pipelines. Status transitions (pending → approved/completed/rejected) are visible in the dashboard; rejections refund reserved balance.