1. Available plans and billing cycles
QuantFlow may offer Starter and Premium subscriptions in monthly, quarterly, or yearly billing cycles. The current Pricing page is the source of truth for published plan names, features, price, and access level at checkout time.
- Starter access is intended for core modules such as Dashboard, Economic Calendar, and COT Report.
- Premium access is intended for broader platform access according to the active plan configuration.
- Plan features, prices, support scope, and billing cycles may change over time, but confirmed subscription records remain traceable in the audit system.
2. Payment gateway confirmation rule
Automated paid access is activated only after QuantFlow receives and verifies a successful payment confirmation from the payment gateway server-side callback. For VNPay, that means a valid IPN event, valid signature, successful response code, successful transaction status, correct order reference, correct amount, and idempotency protection.
- The browser Return URL is not enough to activate access automatically.
- Failed, cancelled, missing-signature, invalid-checksum, wrong-amount, expired, or duplicate-unsafe events do not activate a plan.
- Payment audit records separate Browser Return events, VNPay IPN events, and Email Notice events for operational clarity.
3. Currency, displayed amount, and VNPay raw amount
VNPay sends amount values in the gateway format required by VNPay. The Payment Audit may show both the raw gateway amount and the actual customer-facing amount to prevent confusion.
- For example, a VNPay raw amount of 22500000 represents an actual amount of 225,000 VND because VNPay amount values are multiplied by 100.
- QuantFlow may price plans in USD for product display while using a configured USD/VND conversion rate for VNPay checkout.
- Production pricing and conversion rules should be confirmed before real-money payment launch.
4. Subscription period and access timing
Subscription duration is based on the selected billing cycle and begins when the subscription is activated in the access system. The user Billing page shows current status, valid-until timestamp, and unlocked modules.
- Monthly, quarterly, and yearly periods may be calculated by the subscription store according to the active plan rules.
- Access may appear after the gateway IPN reaches the server and passes verification.
- If a payment succeeds but access does not appear, users should contact support with the transaction reference.
5. Renewals, plan changes, and manual admin actions
Unless the Pricing page or checkout flow states otherwise, QuantFlow subscriptions are checkout-based and do not imply automatic recurring billing. Users may purchase a new period or request support for plan changes when available.
- Admins may grant, extend, downgrade, suspend, cancel, or reactivate access when justified by payment audit, support review, or internal operations.
- Manual changes should be recorded in subscription and audit logs.
- Plan upgrades or downgrades may affect module access immediately or at the next support-approved transition depending on the admin action.
6. Failed, cancelled, pending, and expired orders
A pending order is not a paid subscription. Orders may remain pending while the user is on the gateway page, while the gateway processes the transaction, or while the system waits for a verified callback.
- Pending checkout intents may expire automatically to reduce abandoned orders and duplicate payment risk.
- Users should avoid opening many payment sessions at the same time for the same account and plan.
- Failed or cancelled payment events do not activate subscription access and should not trigger subscription activated emails.
7. Payment audit, exports, and support review
QuantFlow keeps payment audit records so admins can review checkout intent, Browser Return, VNPay IPN, email notice, amount, status, signature result, processed state, and subscription update result.
- Admins may use Payment Audit filters and CSV export to review payment provider, user, status, event type, and transaction references.
- Payment Detail pages should mask sensitive fields and clearly identify raw gateway amount versus actual amount.
- Audit records support billing questions, refund review, duplicate-payment checks, and production readiness evidence.
8. Production payment lock
VNPay production mode must remain locked until merchant approval, production credentials, settlement account confirmation, policy pages, successful sandbox testing, failed/cancelled testing, idempotency checks, audit review, and rollback readiness are confirmed.
- Production TMN_CODE and HASH_SECRET must never be committed to source code or shared in chat.
- Bank settlement details should live in the VNPay merchant agreement or approved internal record, not in project ZIP files.
- A small real-money test should be performed only after production onboarding is complete and rollback is ready.
9. Billing support
For payment, activation, renewal, refund, or billing questions, contact support@hbquantflow.com with the account email, plan, payment time, amount, and transaction reference if available.
- Do not send card numbers, bank passwords, OTPs, VNPay hash secrets, or full bank account details through email or chat.
- Support may ask for additional masked screenshots or gateway references to locate the payment record.
Billing Policy FAQ
Why does my VNPay Return page say success waiting IPN?
Because the browser return page is only informational. QuantFlow waits for the verified server-to-server VNPay IPN before activating the subscription automatically.
What does raw amount mean in Payment Audit?
VNPay raw amounts are multiplied by 100. For example, 22500000 means the actual customer-facing amount is 225,000 VND.
Does QuantFlow automatically renew subscriptions?
Unless a checkout page clearly states otherwise, QuantFlow uses checkout-based subscription periods rather than automatic recurring billing.
Can production VNPay be enabled now?
No. Production should stay locked until production merchant approval, settlement account confirmation, production credentials, sandbox failure tests, idempotency checks, policies, and rollback readiness are complete.