Frequently Asked Questions

ReliancePay helps businesses quote and execute fiat, NGN, USD, HKD and USDT settlement routes with visible exchange rate, payout timing and compliance checks.

Yes. A business can review NGN to USDT pricing, submit account onboarding, and execute after KYB, AML and payment-path checks are complete.

Common USDT settlement paths are designed for a 10-30 minute execution window after payment confirmation, with final timing depending on network, bank and compliance review.

Prepare company registration details, beneficial owner information, expected monthly volume, source of funds, preferred currency path and receiving account or wallet information.

Use the login entry to contact the account team or submit the required business profile. The team reviews entity details before activating production access.

Yes. A business can review supported currency combinations, collection paths and expected proceeds first; KYB and AML checks continue during account opening.

The system shows dedicated funding references, beneficiary information and execution notes, while KYT, AML and route review help control risk before settlement.

The quote page shows the mid-market reference, estimated total fee and expected proceeds together before execution.

Common routes can generate an initial reference quote and collection path within minutes. If manual review is required, the account team follows up within a predictable window.

ReliancePay fits high-value collections, fiat conversion, stablecoin return flows and multi-market treasury consolidation for business cross-border funds.

A super administrator can create ordinary users, manage status, reset passwords and maintain company profile information.

Core routes cover USDT, NGN, USD and HKD, with additional fiat currencies used for market display, treasury planning and future routing expansion.

Execution uses server-side configured rates. Public market references may use external market data, and final execution rates are rechecked before settlement.

Yes. The exchange page validates the available balance server-side before deducting the source currency and crediting the target currency.

The system blocks execution and shows a lightweight warning. The server never trusts modified front-end amounts for balance updates.

Deposit addresses are assigned and maintained by a super administrator. Ordinary users can view assigned addresses but cannot edit them.

Submit the deposit amount, transfer TxHash and optional note. The deposit remains pending until an administrator approves it.

Yes. Rejected deposits remain visible to the ordinary user with a clear rejected status and the rejection reason.

Timing may vary because of blockchain confirmations, banking partner processing, liquidity checks and compliance review.

Yes. Funding, exchange and payout events are recorded so finance and operations teams can review the settlement trail.

Yes. Deposit approval is grouped by user so each account's funding activity is reviewed without mixing records across companies.

Public pages focus on the expected result and settlement timing. Internal execution can calculate fees server-side before posting balances.

Minimum requirements depend on the currency, network and account policy. The portal can show the applicable guidance on the deposit page.

Yes. Limits can be controlled through account policy, available balance checks, compliance review and administrator approval.

Balance-changing actions are processed server-side with validation, audit records and role-based permissions.

Typical controls include KYB, AML, wallet risk screening, payment-path review and administrator approval for sensitive actions.

Ordinary users can view their company information and assigned deposit address, while administrative edits are limited to super administrators.

Businesses can use the portal for deposits, exchange, payouts and settlement records, with account support for onboarding and operational questions.