The order-review workflow for historical product purchases processed through the Platform.
1. Overview
This policy applies to historical Product Purchase orders processed through the Platform. For those orders, Ai MarketSpace records delivery and provides a process for buyers to review a delivery, request a correction within the purchased scope, or ask for help with an order issue. This process does not guarantee a refund or replace any mandatory statutory consumer rights.Direct collaborations
Direct collaboration records document terms and progress only. Ai MarketSpace does not collect, process or verify the agreed price, promise a refund or provide financial protection for payments arranged between participants. Mandatory statutory rights remain unaffected.2. Historical Product Purchase payments
- —For historical product purchases made through Platform checkout, card payments were processed by Stripe.
- —Card details are entered directly with Stripe and never touch Ai MarketSpace servers.
- —Direct collaboration payments are arranged between participants and are not processed or verified by AI MarketSpace. This policy does not promise a refund or payment protection for them.
3. Product Delivery
Builders are responsible for delivering the purchased product exactly as described in the listing. Depending on the product, delivery may include:
- —Files
- —Documentation
- —Setup instructions
- —Access credentials
- —Implementation materials
After a delivery or revised delivery, the Buyer has seven (7) calendar days to confirm it, request an in-scope correction, or open an order support review. The deadline is shown on the order. Builders must deliver the agreed listing and order scope; requests for new features or additional work are outside the original scope and require a separate agreement.
4. Requesting an in-scope correction
During the delivery review window, the Buyer may request a correction that addresses something included in the original listing and order scope, such as:
- —Missing deliverables that were promised in the listing.
- —A promised item or instruction is missing.
- —The delivered result does not match the agreed scope.
- —Setup or access instructions needed for the agreed delivery are incomplete.
5. Order support review
A Buyer may ask for support for a substantive order issue, including non-delivery, material scope differences, a non-working delivery, a non-responsive Builder, or a legitimate access or security concern. Provide accurate information and relevant evidence. Knowingly false or abusive claims, demands for out-of-scope work, and threats involving refunds or reviews are not permitted and may lead to account restrictions.
An open support review pauses order completion and future payout eligibility while the issue is reviewed. It does not automatically refund the purchase. The order conversation and attached evidence remain available to the participants.
6. Refund Eligibility
A refund request may be considered when:
- —The product was not delivered.
- —The delivered product is substantially different from the listing description.
- —The builder fails to provide the agreed deliverables.
Each case is reviewed individually based on the evidence provided. Submitting a request does not guarantee a refund. Refund requests are handled separately under the Refund Policy. Nothing in this policy limits mandatory statutory rights.
7. Buyer Responsibilities
To remain eligible for buyer protection, buyers must:
- —Review the listing details and setup requirements before purchasing.
- —Keep order communication on the Platform and do not share passwords, API keys, 2FA or recovery codes, session cookies, or other credentials.
- —Use accurate information and relevant evidence when asking for support.
- —Use a revision request only for corrections within the agreed scope.