Billing and packages

Billing is metered per GB of traffic (upload plus download) through the gateway, paid from a prepaid USD balance. There are no monthly fees or minimum commitments — see current rates on Pricing.

Topping up with USDT-TRC20

On Billing, pick an amount (or enter a custom one) and continue — you get a dedicated deposit address and QR code for USDT on the TRC20 network. 1 USDT = 1 USD; the full amount received is added to your balance, and some top-up amounts earn bonus credit on top of that.

Send exactly the requested amount, and only USDT-TRC20, to that address — another network or token risks losing the funds. If you're paying from an exchange, raise the withdrawal amount so the "you will receive" figure (after the exchange's own fee) matches what was requested; otherwise less arrives than expected and only the received amount gets credited.

If a payment doesn't show up automatically, the Billing page has an "already sent it?" option to verify a transaction hash and credit the payment manually.

Three ways to pay for the same traffic

• Monthly plan — a fixed GB allowance that renews every month from your balance, at the lowest per-GB rate.
• Traffic packages — one-off prepaid blocks of GB bought from your balance, cheaper per GB than pay-as-you-go.
• Pay-as-you-go — no commitment; every GB is billed straight from your USD balance at the standard per-GB rate.

They stack, and they are consumed in exactly that order: plan GB first, then package quota, then your USD balance. You never pay twice for the same byte, and you never have to switch anything on. If all three run out, new connections are refused with 402 (see Errors) until you top up, buy a package, or subscribe.

Current plan sizes, package sizes and rates are on Pricing; you subscribe and buy from Billing.

Monthly plans: renewal, grace, cancellation

A plan is charged from your USD balance, so keep enough balance for the next renewal — there is no card on file and nothing is charged externally.

• Renewal. On the same day each month (if the next month is shorter, the last day of that month), the plan charges its current price and resets your allowance to the plan's current GB. Editing happens on the plan, not on your subscription: if we change a plan's size or price, the new values apply from your next renewal, never retroactively.
• Unused GB does not roll over. Each period starts at the full allowance and whatever you didn't use is gone. Pick a plan around your typical month rather than your busiest one — traffic above the plan simply falls through to packages and pay-as-you-go instead of failing.
• Not enough balance at renewal? The plan enters a 3-day grace period instead of ending: it stops giving GB (traffic falls back to your packages and balance) and we retry the charge. Top up before the grace deadline and the plan resumes with a full fresh month from that moment. Miss it and the plan expires, and you're back on pay-as-you-go — nothing is blocked, it's just billed per GB again.
• Cancelling takes effect at the end of the paid period: the GB you already paid for stays usable until then, and you can resume any time before that date. There are no refunds for the current period, so cancel when you no longer need the next month, not to get money back. A plan cancelled while in grace ends immediately (nothing was charged for that period, so there is nothing to refund).
• Changing plans is cancel plus re-subscribe: cancel the current plan and subscribe to the new one after the period ends. There is no mid-period upgrade or pro-rating yet.

You get an email and a panel notification on renewal, failed renewal, grace expiry and cancellation, so a silent lapse isn't possible.

Traffic packages

Packages are one-off: buy the GB, use it whenever, nothing renews and nothing expires monthly. Their quota is consumed after any plan GB and before pay-as-you-go billing. Buy one from Billing.

Settlement timing

Usage isn't billed connection-by-connection in real time — traffic is metered and settled roughly every 30 seconds. That means a burst of traffic can show up in your balance and in Usage a few seconds after it actually happened, and any traffic still inside the current settle window at the moment your balance hits zero is still billed once that window settles.

Checking usage

The Usage page breaks traffic and cost down by day (today, last 7 and 30 days), a daily chart, per-settlement records, and a full wallet ledger — top-ups, package purchases, plan charges and usage charges — that you can filter by transaction type. Each settlement record shows how the traffic was covered: from plan, from quota, or billed to your balance. Both the records and the daily breakdown export to CSV from the same page, and the wallet ledger exports from Billing. For the full mechanics of per-GB billing, see Per-GB billing, explained.

Checking your balance from the API

Create an API key under API keys, then send it in the X-API-KEY header — never in the URL — to GET /balance:

curl -H "X-API-KEY: $KEY" "https://oneforproxy.com/balance"

{ "balance": 42.5, "currency": "USD", "quota_bytes_remaining": 5368709120, "price_per_gb": 3.0 }

quota_bytes_remaining is what's left of any traffic package; once it's zero, usage is billed from balance. Poll this before a large job to make sure you won't run dry mid-run.

For everything else — plan GB left, renewal date, usage records, CSV exports and subscribing from code — use the versioned API: see Management API and Docs. GET /balance is kept only for existing integrations; new code should call GET /api/v1/wallet/balance instead.