Refund review page

Refund and Remake Review

Refund and remake questions are trust questions. This page explains when support can review a delivered file, what evidence helps, and why the published refund policy remains the formal source for eligibility.

Direct answer

Refund and remake review explains how users should ask for support when a paid output, download, passport photo code or prepared photo result appears wrong or unusable.

Clear refund and remake boundaries reduce confusion before checkout and make support review more accountable after delivery.

  • Explains technical rejection evidence
  • Clarifies remake and refund review boundaries
  • Links support, refund policy, and quality review pages
  • Avoids promising control over official application decisions
Prepared UK passport photo with cleaner crop and background
Prepared results should still look natural and easy to verify against the rules.

What evidence helps

Clear evidence lets support understand whether this is a service/output issue.

  • Order reference or email used at checkout.
  • Which output had the issue: digital file, photo code, print sheet, or download link.
  • A short description of the technical issue or route mismatch.
  • Any official rejection wording if the issue happened after submission.

What this page does not promise

The support boundary must stay truthful.

  • It does not promise automatic refunds for every official rejection.
  • It does not guarantee that a weak source photo can be fixed.
  • It does not control HM Passport Office or GOV.UK decisions.
  • It does not replace the privacy policy, terms, or official application guidance.

Why review boundaries matter

Policy clarity helps conversion and reduces unrealistic expectations.

  • A weak source image may need a retake.
  • Wrong output route selection can cause problems.
  • Download or access issues should be handled through support.
  • Refund or remake decisions should follow the published policy.

When to request a review

Refund/remake pages are conversion trust pages, especially for a new brand.

  • The download link does not work.
  • The passport photo code is not recognised and the application route did ask for a code.
  • The delivered output does not match the route selected at checkout.
  • The prepared photo has an obvious visible problem that was not expected from the preview.

When users should contact support

Support pages should reduce chargeback risk by giving users a clear path when something goes wrong.

  • Download links do not work or the expected output is missing.
  • The wrong output route was chosen and the user needs guidance.
  • A warning was unclear and the user needs help deciding whether to retake.
  • The user believes the prepared file does not match the selected service.

Related pages

FAQ

What should I check before paying?

Check the preview, output type, photo route and policy wording before checkout.

What evidence helps with a passport photo refund or remake request?

Order details, the delivered file or reference, and a screenshot or message showing the photo-related rejection reason help support review the case.

Does a refund or remake guarantee official acceptance?

No. Refund or remake review is support for the service output, not a guarantee of an official application decision.

What should I include when contacting support?

Include the order reference if available, the output route you selected, and a concise description of the download, code, print or photo-quality issue.