Refund rules

Refund Policy

This Refund Policy explains how HB QuantFlow reviews refund and billing questions for digital subscription access. It is designed to be clear before production payments are enabled and to support fair handling of duplicate, failed, or technical payment issues.

Effective: 2026-06-10Updated: 2026-06-10Keyword: QuantFlow Refund Policy
This page is an operational website policy for production readiness. It is not a substitute for legal advice. Review with a qualified professional before full commercial launch.

1. Digital subscription delivery

QuantFlow sells access to a digital financial intelligence dashboard. Once a verified payment activates the selected plan, the service is considered delivered for the subscription period shown in the user Billing page.

  • Starter and Premium plans unlock different modules according to the published Pricing page.
  • The Billing page shows current plan, status, valid-until time, and unlocked modules.
  • Payment success is determined by verified gateway records and the QuantFlow payment audit trail.

2. Refund request window

Unless a different written agreement applies, refund requests should be submitted within 7 calendar days after the payment date. Requests submitted later may still be reviewed for duplicate payment, confirmed technical failure, or legally required handling, but approval is not automatic.

  • Send requests to support@hbquantflow.com from the email connected to the account when possible.
  • Include account email, plan, billing cycle, payment time, amount, payment provider, and transaction reference.
  • Do not include card numbers, bank passwords, OTPs, or full bank account details in the support email.

3. Cases that may qualify for review

HB QuantFlow may review refund or credit requests when payment records show a clear billing issue or access problem.

  • Duplicate successful payments for the same account, plan, billing cycle, or order context.
  • Payment marked successful by the gateway but access was not activated after reasonable support review.
  • Incorrect plan activation caused by a verified platform or admin processing error.
  • A payment gateway or server incident that prevented normal subscription delivery.

4. Cases that normally do not qualify

Refunds are generally not granted for reasons unrelated to payment or platform delivery.

  • Trading losses, investment losses, market outcomes, or disagreement with research interpretation.
  • Failure to use the service during an active subscription period.
  • Account sharing, policy violation, attempted abuse, chargeback fraud, or unauthorized redistribution of paid content.
  • Requests based only on a browser return page when the payment gateway/IPN did not confirm success.

5. Failed, cancelled, and expired payments

Failed, cancelled, expired, invalid, or unverifiable payment events do not activate access. If money appears to have been deducted but QuantFlow did not receive a valid payment confirmation, the user should contact both the payment provider or bank and QuantFlow support with the transaction reference.

  • QuantFlow will rely on payment audit records, gateway references, and merchant portal evidence when reviewing the issue.
  • If the gateway later confirms the payment was not successful, no subscription will be activated automatically.
  • If the gateway confirms a successful payment and the platform failed to activate access, support may correct the subscription after verification.

6. Duplicate payment handling

If duplicate successful payments are confirmed, HB QuantFlow may provide a refund, subscription extension, plan credit, or other reasonable correction depending on payment gateway rules, merchant settlement status, and the user account record.

  • Duplicate handling is based on transaction references, amount, plan, account email, and audit timeline.
  • Only confirmed successful transactions are considered for duplicate payment review.
  • Refund timing may depend on the payment gateway, bank, merchant settlement cycle, and production agreement.

7. Chargebacks and payment disputes

If a user opens a bank or gateway dispute, QuantFlow may provide account, access, payment audit, IPN, and support records to respond to the dispute. Access may be suspended while a dispute is under review.

  • Users should contact support first so the issue can be reviewed quickly with the payment audit trail.
  • Fraudulent disputes, abuse, or repeated chargebacks may lead to account suspension or termination.

8. How to request refund support

Email support@hbquantflow.com with a clear subject such as “Refund request” or “Billing review”. Include only the information needed to locate the payment and account.

  • Account email and username if available.
  • Plan and billing cycle purchased.
  • Payment provider, payment time, amount, currency, and transaction reference.
  • A short explanation of the issue and any relevant screenshots with sensitive information masked.

Refund Policy FAQ

Can I get a refund because of trading losses?

No. Refunds are not granted because of trading losses, market outcomes, investment performance, or personal trading decisions.

What if I paid twice by mistake?

Contact support@hbquantflow.com with both transaction references. Duplicate successful payments may be reviewed for refund, extension, or account credit depending on gateway and merchant records.

What if VNPay says payment succeeded but my plan is not active?

Contact support with the transaction reference. QuantFlow will review the gateway event, IPN status, signature verification, and payment audit record before correcting access.

How quickly are refunds processed?

Review time depends on the evidence, gateway records, and merchant settlement status. Bank or gateway return timing may vary after approval.

Support contact: support@hbquantflow.com. For billing support, include account email, plan, payment time, amount, and transaction reference when available.
Never send card numbers, VNPay hash secrets, full bank settlement details, passwords, OTPs, or private documents through public chat.