ApiFlux Payment, Supported Regions, Customer Support, and Security Notice

Version: v0.3
Last updated: 2026-08-19
Website: https://apiflux.ai/

Important: This Notice forms part of the ApiFlux Terms of Service. It is an operating document, not legal advice.

Payment and support summary

Supported regions: the United States and other countries and regions permitted by applicable law, United States sanctions and export controls, available payment channels, and the applicable Upstream Services
Billing entity: NovaSpan LLC, a Wyoming limited liability company
Registered and mailing address: 30 N Gould St Ste R, Sheridan, WY 82801, United States
Billing currency: United States dollars (USD), unless the checkout page expressly states otherwise
Taxes: displayed prices exclude applicable taxes unless checkout expressly states otherwise
Payment channels and processors: the methods and third-party processor displayed at checkout at the relevant time
Minimum and maximum top-up: the limits displayed at checkout; limits may differ by payment channel, account, region, and risk controls
Refund window for an unused balance or mistaken top-up: 7 calendar days after payment, subject to Section 4
Billing-dispute period: 30 calendar days after the transaction or billing event
Paid-balance validity: no automatic expiration solely because time passes while the account remains active, subject to the rules below and applicable law
Promotional, referral, bonus, and gifted credit: expires 90 days after issue unless the applicable page or offer states a longer period
Affiliate commission: cash-denominated inviter commission is not account credit; accrual, hold period, verification, and minimum withdrawal follow Section 2 and the numbers displayed in the console or program page
General support: [email protected]
Billing and refunds: [email protected] with Billing/Refund at the start of the subject line
Security reports: [email protected] with Security Report or Urgent Security at the start of the subject line
Privacy requests: [email protected] with Privacy Request at the start of the subject line
Partnerships and enterprise inquiries: [email protected]
Documentation: https://apiflux.ai/docs
Public service status: https://status.apiflux.ai/
Formal legal notices: [email protected] with Legal Notice at the start of the subject line, plus mail to NovaSpan LLC, c/o Registered Agents Inc., 30 N Gould St Ste R, Sheridan, WY 82801, United States
Security-report acknowledgment target: 3 business days; no vulnerability bounty is currently offered

1. Pricing and billing

ApiFlux may charge by model, input tokens, output tokens, cached tokens, request, channel, feature, plan, or another method displayed on the applicable page. Model pages may show reference prices in USD per one million tokens. Actual prices may vary by model version, upstream channel, cache hit, routing policy, currency, tax, promotion, or account configuration.

The final price is the price displayed and recorded by ApiFlux on the console, model page, or order page when the request or transaction occurs, subject to correction of an obvious error and applicable law.

A request may incur a charge even if it does not return a complete result when an Upstream Service has processed tokens, streaming has begun, or processing has otherwise started. An internal automatic retry or failover attempt that returns no model content to the user is not billed separately where the system records it as an internal retry. A retry actively initiated by the user or the user's application is a new call and may be billed separately.

Billing is based on calls marked billable in the ApiFlux system and the applicable input, output, cache, request, and route records. Estimates may lag because of data synchronization, upstream billing corrections, retries, or currency conversion.

Users should monitor console balances, call logs, tokens, models, latency, errors, charges, budgets, limits, and alerts. Users are responsible for controlling their own application traffic and spending.

2. Top-ups, balances, credits, and referral programs

Users may top up a prepaid balance through payment channels available in the console or add credit through a valid redemption code. The minimum top-up, fees, currency, payment channel, and risk controls are those displayed on the payment page at the time of the transaction.

Unless law or an applicable page expressly provides otherwise:

A balance may be used only to purchase ApiFlux services;
A balance is not a bank deposit, electronic money, security, investment, or financial product;
A balance earns no interest, may not be transferred or sold, and cannot be redeemed for cash;
Promotional, referral-bonus, gifted, or redeemed credit may have expiry, model, region, or account restrictions;
Credit obtained through fraud, error, vulnerability, duplicate posting, chargeback abuse, or rule violation may be revoked or corrected;
Users must not exploit top-ups, refunds, redemption codes, referral programs, or balances for arbitrage, money laundering, payment evasion, or regulatory evasion.

A user-purchased paid balance does not expire solely because time passes while the account remains active. Promotional, referral-bonus, gifted, or redeemed credit expires 90 days after issue unless the applicable issue page states a longer period. The system uses the credit that expires first.

If NovaSpan LLC discontinues the service, eligible unused paid balances will be refunded or otherwise handled as required by applicable law and the notice then in effect.

Referral program

The referral program may provide two benefits with different legal character:

Bonus credit is promotional account credit. It may carry expiry, model, region, or account restrictions and cannot be transferred, refunded, or converted to cash. It expires under the applicable offer terms.
Affiliate commission is cash-denominated commission accrued by an inviter on eligible invitee top-ups. It is not account credit and is governed by the referral-program terms and rates displayed in the console or program page.

Commission accrues when an eligible invitee top-up is confirmed, at the tier rate displayed at that time. Tier assessment, hold periods, minimum withdrawal, payout channel, identity verification, compliance review, and tax treatment are those displayed in the console or program page at the relevant time.

Commission may first enter a pending state. If the underlying top-up is refunded, charged back, or reversed, the corresponding commission may be deducted or clawed back. Commission obtained through self-referral, fabricated accounts, payment fraud, or program abuse may be voided and recovered, and related accounts may be suspended.

Program parameters may be changed prospectively. A change does not retroactively alter commission already validly accrued, except for reversal, fraud, chargeback, error correction, or another lawful basis.

3. Payment authorization, taxes, and failed transactions

Users confirm that they are authorized to use the selected payment method and authorize ApiFlux and its payment provider to process information necessary for the transaction.

Users are responsible for applicable taxes, bank charges, payment fees, and currency-conversion costs unless checkout expressly provides otherwise.

A payment may be successful, processing, failed, expired, reversed, or held because of a payment channel, risk control, bank, network, sanctions, compliance, or fraud-prevention matter. Balance is credited only after payment is confirmed.

Do not repeat a payment while it is processing. If funds were debited but no balance appears, keep the transaction ID and payment evidence and email [email protected] with the subject prefix Billing Support.

ApiFlux may correct an obvious price, balance, or posting error. Where permitted by law, if a system error caused an undercharge, we may correct it after providing reasonable records and notice. If it caused an overcharge, we will return the corresponding balance or payment as appropriate.

4. Refunds and cancellation

Unless mandatory law, the payment page, or a written ApiFlux agreement provides otherwise:

Completed API calls and consumed credit are non-refundable;
A request for which upstream processing cost has been incurred is generally non-refundable;
Promotional, referral-bonus, gifted, and redeemed credit cannot be refunded or converted to cash;
Affiliate cash commission is not account credit and follows the referral rules in Section 2;
Payment fees, taxes, bank charges, and foreign-exchange losses are generally non-refundable;
No refund is provided where an account is suspended or terminated for violation, fraud, stolen payment, chargeback abuse, account sharing, resale, or evasion;
An unused paid balance or mistaken top-up may be refunded within 7 calendar days after payment only if no API call or credit consumption occurred after that top-up was posted, the applicant passes account verification, and the payment channel supports a return to the original method.

Where mandatory consumer law provides a cooling-off period, cancellation right, or refund right that cannot be excluded, that law applies. A user who requests immediate digital service and begins consuming credit may lose the corresponding cancellation right where permitted by law.

Request a refund within 7 calendar days after payment by emailing [email protected] with the subject prefix Billing/Refund. Include the account email, order number, transaction ID, amount, time, and reason. An approved refund is generally submitted to the original payment channel within 5 business days; actual arrival depends on the payment provider.

ApiFlux may deduct a non-refundable payment-processing fee, tax, or currency-conversion cost where lawful and will explain that deduction in the refund decision.

5. Billing disputes and chargebacks

Users must submit a billing dispute within 30 calendar days of the transaction or billing event by emailing [email protected] with the subject prefix Billing Dispute. Provide the request ID, model, channel if known, time, API Key prefix or suffix, order number, and relevant logs.

We generally provide an initial response within 10 business days and investigate using ApiFlux and applicable upstream records.

Users should contact billing support before submitting a card chargeback or payment dispute. A malicious or baseless chargeback may result in suspension of the account and API Key, a frozen balance, and recovery action. This does not limit a user's lawful right to dispute a transaction with a payment provider.

6. Supported countries and regions

ApiFlux is available in the United States and other countries and regions where local law permits the service, United States sanctions and export controls permit it, an available payment channel permits it, and the selected Upstream Service permits it.

Sanctions and upstream rules may apply by person, entity, region, industry, and end use. ApiFlux therefore does not maintain a permanent fixed country list in this Notice.

ApiFlux does not provide service to a country, region, entity, or person subject to applicable sanctions, export controls, embargoes, regulatory restrictions, payment restrictions, or Upstream Service restrictions. Users must not use a VPN, proxy, false address, third-party payment method, or another method to evade regional restrictions.

Model and payment-channel availability may vary by region and may change with law, upstream policies, payment rules, and risk conditions. Before registration, top-up, or calling a particular model, users should confirm that their location and intended use comply with applicable requirements.

7. Customer support

Use the following email routes. Put the specified subject prefix at the start of the subject line:

General support: [email protected] - Support
Billing and refunds: [email protected] - Billing/Refund
Billing disputes: [email protected] - Billing Dispute
Privacy requests: [email protected] - Privacy Request
Abuse reports: [email protected] - Abuse
Account appeals: [email protected] - Appeal
Security reports: [email protected] - Security Report
Urgent security incidents: [email protected] - Urgent Security
Partnerships and enterprise: [email protected] - Partnership or Enterprise
Formal legal notices: [email protected] - Legal Notice, plus mail to NovaSpan LLC, c/o Registered Agents Inc., 30 N Gould St Ste R, Sheridan, WY 82801, United States

When requesting support, provide the account email, order number, request ID, request time, model or channel, error code, API Key prefix or suffix, screenshots, and reproducible steps where relevant. Do not send a full API Key, password, private key, card information, CVV, or unrelated personal data.

Support response targets are operational targets, not availability guarantees. Unless a separate written support or SLA agreement states otherwise, we do not promise a particular response time or resolution time.

Public service status is available at https://status.apiflux.ai/. Maintenance and major incidents may also be announced through the ApiFlux website, console, or registered account notices.

8. Account and API Key security

Users should use a unique strong password, enable available two-factor authentication or a passkey, limit team permissions, use separate API Keys for separate environments, and rotate credentials regularly.

An API Key should be stored only on a server or in a secure secret-management system. It must not be embedded in a public frontend, client application, source repository, screenshot, or support message.

If a user detects a suspicious login, key exposure, unknown call, or balance anomaly, the user must immediately revoke or rotate the relevant credential, preserve request IDs and the timeline, and email [email protected] with the subject prefix Urgent Security. We may temporarily restrict an account or key to prevent continuing harm.

9. Vulnerability disclosure and security research

To report a potential ApiFlux vulnerability, email [email protected] with the subject prefix Security Report. Include the vulnerability type, affected URL or function, reproduction steps, impact, proof of concept, and safe contact details. Initially provide only the minimum evidence necessary and do not publicly disclose details before remediation or written permission.

Without written authorization, researchers must not:

Access, modify, download, or delete another user's data;
Conduct DDoS, resource-exhaustion, spam, social-engineering, phishing, or physical attacks;
Deploy malware, maintain persistence, or move laterally;
Disrupt payments, bypass payment controls, or conduct availability-impacting load tests;
Continue testing beyond what is necessary to confirm the vulnerability;
Disclose keys, personal information, User Content, or other confidential data to a third party.

Where research is conducted in good faith, minimizes impact, is reported promptly, complies with this Section, stops when requested, causes no third-party harm, and complies with applicable law, NovaSpan LLC will not assert solely on the basis of that authorized-scope research that the researcher violated this Policy. This safe harbor does not authorize violation of third-party terms or law and does not bind law-enforcement bodies or third parties.

ApiFlux currently offers no vulnerability bounty or reimbursement of testing costs. We aim to acknowledge a security report within 3 business days and provide progress updates based on risk. These are targets, not guarantees.

10. Consent text before registration or top-up

The registration or top-up flow may display the following consent text:

I have read and agree to the ApiFlux Terms of Service, Privacy Policy, Acceptable Use Policy, and Payment, Supported Regions, Customer Support, and Security Notice. I understand that ApiFlux routes API requests to third-party models or providers and processes request content, responses, usage, logs, account, and payment information under applicable settings. I understand that model prices, availability, and upstream channels may change.

Where technically and legally appropriate, the system should record the user ID, account email, organization ID, agreement name and version, language version, consent time, IP address, User-Agent, triggering context, and the links or text snapshot presented.

11. Updates

We may update this Notice because of changes in the product, price, payment channels, law, security, or Upstream Services and will state the update date. Where reasonably practicable, a material adverse change to price, refund eligibility, balance validity, supported regions, or security handling will be communicated through the website, console, or registered email address. Applicable legal requirements prevail.