This Refund Policy outlines how subscription payments and refunds are handled for the Credora Business OS platform (the "Service"). We aim to be fair, transparent, and straightforward in all our billing and refund practices.
General Policy
Credora is a subscription-based software platform. When you subscribe, your payment provides access to the full Business OS—including all modules, features, and integrations—for the duration of your active billing period.
Our goal is to provide a reliable, high-quality service. We encourage users to explore the platform and review our product overview and pricing parameters before committing to a paid subscription track.
Refund Eligibility
Refunds may be considered and issued under the following specific architectural and transaction failure conditions:
- 01 // Billing Errors: If you were charged incorrectly due to an isolated technical system ledger error on our part, you are entitled to a full correction refund.
- 02 // Duplicate Charges: If multiple transaction executions occur concurrently for the same billing period due to a gateway loop, duplicate charges will be reverted.
- 03 // Technical Outages: If a verified technical block on Credora's infrastructure prevents access to core platform systems for a significant portion of your active window, and our engineering desk fails resolution promptly.
Non-Refundable Cases
To preserve operational scaling consistency and system fairness, refunds are strictly denied under these conditions:
Cancellation Policy
You can strip out subscription loops smoothly at any given milestone:
- • Subscriptions can be discontinued manually via the user console profile parameters or direct support line routing.
- • Upon termination, terminal access maintains capability through to the validation edge of the paid period.
- • Downstream billing tasks are hard-canceled immediately upon processing authorization.
- • Active configuration datasets adhere to our Privacy policy retention matrices before erasure routines.
Requesting a Refund
To request a billing adjustment check, your communication must pass these parameter attributes:
- • Account Registry Email
- • Settlement Date & Exact Figure
- • Core Gateway Transaction ID
- • Comprehensive Fault Summary
Processing Time
Approved settlement loops dispatch straight back down initial transaction pipelines under strict tracking limits:
| Processing Stage | Target Window | Execution Protocol |
|---|---|---|
| Ledger Reversal | 5 to 10 Business Days | Initialized automatically from our settlement architecture back to your native payment array channel. |
| Bank Clearance | Varies by Carrier | Outside clearance timelines depend entirely on the partner banking house or card issuer network infrastructure. |
Changes to This Policy
We may update this Refund Policy model to maintain alignment with billing practices or structural legal shifts. Revisions will trigger platform broadcast modules or direct email queues prior to execution timelines.
Billing Inquiries
To resolve transactional questions, investigate unexpected bank charges, or submit formal refund validation assets, open an infrastructure communication ticket directly with our dispatch node: