Refund Policy

1. Marketplace principle

Request coordinates payments and workflow between fans and independent creators. Refund eligibility depends on request status, payment status, creator action, delivery evidence, fraud signals, processor rules, and applicable law.

2. Automatic or normally eligible refunds

• Creator rejects the request before starting work.
• Creator fails to accept or deliver within the platform deadline and no approved extension applies.
• Payment was duplicated or technically erroneous.
• Request cancels a transaction for policy, fraud, compliance, or safety reasons before delivery.
• Applicable law requires a refund that cannot be waived.

3. Usually non-refundable situations

• The creator substantially delivered the accepted request and there is proof of upload, delivery, or download availability.
• The fan is dissatisfied with subjective creative choices, tone, performance, style, timing, or personal preference.
• The fan submitted unclear, incomplete, unlawful, abusive, or policy-violating instructions.
• The fan cannot access content because they provided wrong contact details or failed to follow reasonable download instructions.
• The fan attempts payment abuse, chargeback abuse, account manipulation, or fraud.

4. How to request a refund

Email support@request.cx with your tracking code, the email address used at checkout, the payment ID or receipt if available, the creator page or request details, a concise explanation of the issue, and supporting evidence such as screenshots, timestamps, delivery errors, or correspondence.

Request normally reviews refund requests within 5 business days after receiving the required information, though complex fraud, delivery, chargeback, or safety reviews may take longer. Request may approve, deny, partially refund, credit, extend, replace, or escalate a refund request at its discretion, subject to applicable law and payment processor rules.

5. Dispute workflow

Fans should contact support promptly and include the tracking code, request details, issue description, and any evidence. Request may ask the creator for proof of delivery, context, replacement delivery, or clarification. Request may decide to refund, partially refund, deny, credit, extend, or escalate the matter at its discretion.

Disputes should be raised within 7 days after delivery or the expected delivery deadline unless law requires a longer period. Late claims may be denied where evidence is unavailable or the delay prejudices defense.

6. Chargebacks and processor disputes

If a fan files a chargeback or bank dispute, Request may submit evidence including request text, timestamps, IP/device signals, payment records, delivery proof, download events, communications, policy acceptance, and support records. Request may suspend related accounts and hold payouts while the dispute is pending.

7. Creator obligations

Creators must maintain delivery evidence, respond to support requests, avoid misleading commitments, and cooperate with refund and dispute reviews. Creator payouts may be reversed, held, offset, or reduced for refunds, chargebacks, fraud, processor fees, or policy violations.