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

Version: v0.1
Last updated: 2026-07-16
Website: https://apiflux.ai/

Translation notice: This English version is a working translation pending professional review.

Important: This Notice forms part of the ApiFlux Terms of Service and does not constitute legal advice to any user.

Payment and support summary

Supported regions: the United States and other countries and regions permitted by applicable law, United States sanctions and export controls, payment channels, and 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); 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/maximum top-up: the limits displayed at checkout; limits may differ by payment channel and risk controls
Refund window for unused balance and mistaken top-ups: 7 calendar days after payment
Billing-dispute period: 30 calendar days after the transaction or billing event
Paid-balance validity: no automatic expiration while the account remains active; promotional, referral, and gifted credit expires 90 days after issue unless the applicable page states a longer period
Unified contact channel: https://apiflux.ai/contact
Service status: there is currently no separate public status page; maintenance and major incidents are announced through the ApiFlux website, console, or account notices
Documentation: https://apiflux.ai/docs
Security-report acknowledgment target: 3 business days; no vulnerability bounty is currently offered

1. Pricing and billing

ApiFlux may charge principally by model, input/output tokens, cache, request, channel, or feature. 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, or promotion. The final price is the price displayed and recorded by the system on the console, model page, or order page when the request occurs.

A request may incur a charge even if it does not return a complete result where an upstream provider has processed tokens, streaming has begun, or the user interrupts the connection. An internal automatic retry or failover attempt that returns no model content to the user is not billed separately. A retry actively initiated by the user or the user's application is billed as a new call. Billing is based on calls marked billable in the console and their actual input/output tokens.

Users should monitor console balances, call logs, tokens, models, latency, and charges and set appropriate budgets, limits, and alerts. Estimates may lag because of data synchronization, upstream billing corrections, or currency conversion.

2. Top-ups, balances, and redemption codes

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, and channel are those shown on the payment page.

Unless law or a page expressly provides otherwise:

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

A user-purchased paid balance does not expire solely because time passes while the account remains active. Promotional, referral, gifted, or redeemed credit expires 90 days after issue unless the issue page expressly provides 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 handled as required by applicable law and the notice then in effect.

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, or expired because of a payment channel, risk control, bank, network, or compliance 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, retain the transaction ID and payment evidence and contact 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.

4. Refunds and cancellation

Unless mandatory law, the payment page, or ApiFlux's written 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, gifted, and redeemed credit cannot be refunded or converted to cash;
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, 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 at https://apiflux.ai/contact and mark it “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 through https://apiflux.ai/contact, marked “Billing Dispute,” and provide the request ID, model, time, API Key prefix/suffix, and relevant logs. We generally provide an initial response within 10 business days and investigate using ApiFlux and 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 charge 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 model or API provider permits it. Sanctions and upstream rules may apply by person, entity, region, industry, and end use, so ApiFlux does not maintain a permanent fixed country list.

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, 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

General support: https://apiflux.ai/contact (mark “Support”)
Billing and refunds: https://apiflux.ai/contact (mark “Billing/Refund”)
Privacy requests: https://apiflux.ai/contact (mark “Privacy Request”)
Abuse reports: https://apiflux.ai/contact (mark “Abuse”)
Security reports: https://apiflux.ai/contact (mark “Security”)
Legal notices: submit an electronic copy through https://apiflux.ai/contact and mail it to NovaSpan LLC, c/o Registered Agents Inc, 30 N Gould St Ste R, Sheridan, WY 82801, United States
Contact form: https://apiflux.ai/contact
Documentation: https://apiflux.ai/docs
Service status: maintenance and major incidents are currently announced through the website, console, or account notices

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

Standard support hours are Monday through Friday, 09:00–17:00 United States Mountain Time, excluding United States federal holidays. General and billing requests have a target response time of 2 business days. Suspected account takeover, key exposure, or an active security incident has a target response time of 1 business day. These targets are not an availability guarantee unless separately agreed in a written support or SLA agreement.

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 and 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 contact https://apiflux.ai/contact marked “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, use https://apiflux.ai/contact and mark the report “Security Vulnerability.” Include the vulnerability type, affected URL/function, reproduction steps, impact, proof of concept, and secure contact details. Initially provide only the minimum evidence necessary and do not publicly disclose details before remediation.

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, 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 these rules, stops immediately when requested, causes no third-party harm, and does not violate applicable law, NovaSpan LLC will not assert solely on the basis of that authorized-scope research that the researcher violated this Acceptable Use 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 to provide progress updates based on risk. These response times are targets, not guarantees.

10. Consent text before registration or top-up

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; model prices, availability, and upstream channels may change.

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 policies and will state the update date. Where reasonably practicable, a material adverse change to price, refund eligibility, balance validity, or supported regions will be communicated through the website, console, or registered email. Applicable legal requirements prevail.