PHP Decode Statuses, Partial Results, Manual Review, and Refunds

Understand queued, processing, completed, partial, and failed PHP recovery results, including the difference between manual review and credit refunds.

3 min readBy PHPDecompile TeamLast updated: Oct 22, 2026

A processing status describes a file's progress through the workflow. It is not a certificate of source-code correctness. Read the status, warnings, and available actions together before deciding what to download or escalate.

Interpret the outcome per file

Outcome What it means for your next step
Queued or processing Wait for a file outcome; record the order reference if progress appears stuck
Completed Download and review the result before treating it as usable source
Completed with a partial indication Inspect the limitation and consider the offered review action; do not assume completeness
Pending manual-review choice after failure Choose the available investigation or credit-refund route
Manual review requested or in progress Follow the order's investigation state rather than resubmitting the same file blindly
Failed Keep the original and the reported error for the next decision

A project can contain a mixture of these outcomes. An available download for successful files does not imply every selected file succeeded.

No fixed turnaround promise

Automated processing, queue time, file complexity, and manual investigation are different sources of delay. A quick preview on a small file does not establish a deadline for a large project. This guide does not promise a universal completion time.

If a status appears unchanged, retain the order/file reference, the displayed state, and the time you observed it. Contact support with that evidence rather than creating several duplicate paid orders.

Manual review is an investigation

For a failed paid file awaiting a decision, the order can offer submission for manual decrypting. Review may involve administrator access to the original file and additional analysis. It cannot guarantee recovery when required information is unavailable or the protection is unsupported.

A completed partial result can also be eligible for an improvement request. That result remains a completed delivery with a partial indication; it is not automatically treated as the same failure state as an unsuccessful paid file.

Understand the refund action

When the failed-file workflow offers a refund instead of manual review, the action returns credits to the account for that file's applicable share. It is not a promise that all orders, completed partial files, or every quality concern have the same action. Read the current refund policy and the choices shown for your file.

Trial files do not use the paid manual-review/refund action. A failed trial is not evidence that a paid order was charged.

Report a problem without losing context

Include the order reference, original filename and path from your own manifest, reported encoder/PHP information, and the error or partial notice. Describe what you expected to recover and the specific issue observed. Avoid sending unrelated credentials or public source-code dumps.

Keep the original package and any downloaded result. If manual work produces an improved version, reconcile that version against your working tree and rerun the relevant tests.

FAQ

Does “completed” guarantee identical original source?

No. Review the output and its warnings, then test the code in context.

Can I request the same credit refund repeatedly?

Use the single offered file action and check the account's transaction history. Contact support if the state or balance is unclear.

Should I delete a failed original?

Keep your own copy and its project context. Missing or modified inputs can make investigation harder.

Next steps

More in Check results and maintain the application.

Ready to decode ionCube and SourceGuardian files?

Try PHPDecompile free. No credit card required.