Skip to main content

Documentation Index

Fetch the complete documentation index at: https://orbit-docs.devotel.io/llms.txt

Use this file to discover all available pages before exploring further.

Cryptocurrency payments

Orbit accepts cryptocurrency top-ups alongside credit/debit cards. Crypto payments settle to your Orbit wallet in USD-equivalent credits, the same as Stripe top-ups. There are no separate “crypto credits” — once a payment confirms, the funds are indistinguishable from any other top-up and can be spent on messaging, voice, and AI as usual. Crypto payments are powered by NOWPayments and use their hosted invoice flow. You never share wallet keys with Orbit; the only information we record is what NOWPayments reports on the IPN callback.

What is crypto top-up?

Crypto top-up is an alternative to credit/debit card payment. You choose an amount in USD, click “Pay with crypto”, and NOWPayments mints a hosted invoice showing the exact crypto amount to send to a one-time receiving address. Once the network confirms the transfer, your Orbit wallet is credited automatically. The flow is one-shot per top-up. Crypto auto top-up is intentionally not supported — auto top-up remains card-only (USD via Stripe) because crypto prices are volatile and there is no on-file credential we can charge.

Supported coins

The list of accepted coins is dynamic and pulled from NOWPayments at request time. At launch the typical roster includes:
  • Bitcoin (BTC) — Bitcoin mainnet
  • Tether (USDT) — Tron (TRC-20) and Ethereum (ERC-20)
  • USD Coin (USDC) — Ethereum (ERC-20) and Solana (SPL)
  • Ethereum (ETH) — Ethereum mainnet
  • BNB Smart Chain (BNB) — BSC mainnet
  • Solana (SOL)
  • Tron (TRX)
  • Polygon (MATIC)
The hosted invoice surface from NOWPayments shows the full live list when you proceed to checkout. If a coin you want is not visible, contact support — the operator may have it disabled.

Payment flow

  1. In Dashboard → Billing, choose Cryptocurrency in the payment method selector above the amount preset ladder.
  2. Pick an amount (preset or custom). The “Pay with crypto” button opens a NOWPayments hosted invoice in a new browser tab.
  3. On the hosted invoice, pick the coin you want to pay with. NOWPayments shows the exact crypto amount + the one-time receiving address.
  4. Send EXACTLY the requested amount from your wallet to the displayed address. Underpayments and wrong-amount sends are flagged for manual review.
  5. The Orbit dashboard shows a pending-payment card with live status while the network confirms. Once finished, your balance updates immediately.

Status meanings

The pending-payment card surfaces nine status states reported by NOWPayments. The most common transitions in practice are waiting → confirming → confirmed → sending → finished.
StatusPlain English
waitingInvoice issued, waiting for you to send from your wallet.
confirmingTransfer detected on-chain — waiting for block confirmations.
confirmedNetwork has confirmed; NOWPayments is finalising the deposit.
sendingNOWPayments is moving the funds into your Orbit balance.
partially_paidYou sent less than the invoice asked. Flagged for review.
finishedDone — wallet credited, ready to spend.
failedTop-up could not complete. Open a new invoice to try again.
refundedOrbit operator initiated a payout to your wallet.
expiredInvoice timed out before any payment landed. Try again.

Important warnings

Crypto payments are FINAL and NON-REFUNDABLE without operator action. Once the network confirms a transfer, Orbit cannot reverse it from the dashboard. If you need a refund, open a support ticket and a human operator will process it manually (see Refund process below).
Wrong-chain transfers CANNOT be recovered. If the invoice asks for USDT-TRC20 and you send USDT-ERC20 (or vice versa), the funds land at an address that exists on a different network. Neither NOWPayments nor Orbit can recover them. Double-check the network displayed on the invoice before you send.
Send EXACTLY the requested amount. Underpayments are flagged for manual review and may delay your top-up by hours. Overpayments are credited at the USD-equivalent we observe at the time of confirmation — not at the rate displayed on the invoice.

How long does it take?

Confirmation time is set by the blockchain, not by Orbit or NOWPayments. Typical observed times:
  • Bitcoin (BTC) — 10 to 60 minutes (1-6 confirmations)
  • Ethereum (ETH) and ERC-20 (USDT, USDC) — 2 to 10 minutes
  • Tron (TRX) and TRC-20 (USDT) — 1 to 3 minutes
  • BNB Smart Chain — 1 to 3 minutes
  • Solana (SOL, USDC) — under 1 minute
Some coins require more confirmations than others; the hosted invoice shows the required count + the live counter as blocks roll in.

Receipts and tax

Crypto top-ups produce the same kind of receipt as card top-ups, available under Dashboard → Billing → Invoices. The receipt records:
  • Payment method: Cryptocurrency
  • Network and coin (e.g. USDT-TRC20)
  • USD-equivalent at the time of confirmation
  • NOWPayments fee (when the tenant pays it on top — see the fee policy below)
  • Transaction hash (when NOWPayments reports it; not all coins surface this on the IPN payload)
The fiat-equivalent USD figure is recorded at confirmation time and is the value used for tax/accounting purposes. Subsequent price moves of the underlying crypto do NOT change the recorded USD amount.

Fee policy

For top-ups of 50orless,OrbitabsorbstheNOWPaymentsnetworkfeeyoupayexactlytherequestedamount.Fortopupsabove50 or less, Orbit absorbs the NOWPayments network fee — you pay exactly the requested amount. For top-ups above 50, the network fee is shown as a “Network fee” line item on the pre-checkout summary and is added to the amount you send. Either way the USD credited to your wallet is the amount you requested.

Refund process

Crypto refunds are not self-service. To request a refund:
  1. Open a support ticket from the dashboard. Reference the original transaction id (visible under Dashboard → Billing → Invoices).
  2. Provide the destination wallet address. This must be a wallet you control on the same chain as the original payment — wrong-chain refunds are irrecoverable and we will not initiate them.
  3. The operator reviews the ticket and, when approved, submits a payout via NOWPayments. You receive a confirmation when the on-chain payout is broadcast and again when it confirms.
Refund processing time depends on the chain (same ranges as for top-ups). The operator’s response time is up to 24 hours during business days.

Auto top-up

Auto top-up is not available for crypto. The auto-replenish setting on Dashboard → Billing remains card-only (USD via Stripe). This is by design:
  • Crypto prices are volatile, so an auto-charge would have to re-quote on every trigger — non-deterministic from a budgeting standpoint.
  • There is no on-file crypto credential we could charge against; every send has to be initiated manually from a wallet you control.
If you have auto top-up enabled and want to switch to crypto for a manual top-up, the auto setting is unaffected — you can do both.

Troubleshooting

The pending card shows partially_paid. You sent less than the invoice asked. Contact support and reference the transaction id. The operator will either credit the partial amount manually or refund the partial transfer (your choice). The hosted invoice expired. Invoices time out if no payment is detected within their window (typically 60 minutes). Click “Try again” in the dashboard — a fresh invoice is issued. My balance didn’t update after finished. Refresh the dashboard. The pending card normally invalidates the balance query automatically; if it doesn’t, the next page load will pick up the new balance. If the balance still doesn’t reflect a finished top-up after 5 minutes, contact support with the transaction id. I sent on the wrong chain. Unfortunately, neither Orbit nor NOWPayments can recover wrong-chain transfers. The funds remain at an address on the chain you sent on; whether they’re spendable depends on whether you control a wallet at that derivation path on the other chain. This is a hard limitation of how cross-chain transfers work, not an Orbit policy.