Payment failure capture
Capture failed payment events without depending on private checkout, theme or store-specific modifications.
PAYMENT OPERATIONS
Fencair Payment Recovery
A standalone OpenCart extension focused on capturing payment failures, preserving useful order and payment context, and supporting controlled recovery workflows.
The extension is currently in standalone validation. Final compatibility and availability claims will be published only after clean-install testing is complete.
CURRENT VALIDATION SCOPE
What is being separated and tested
The production implementation is being converted into a standalone extension without private-store dependencies.
Order and payment context
Preserve the identifiers and operational state needed for troubleshooting and recovery without storing unnecessary data.
Controlled recovery workflow
Define when recovery actions are permitted, suppressed or require manual review.
Admin visibility
Surface useful operational information so failures can be investigated without direct database access.
WORKFLOW01 02 03 04
A controlled recovery pipeline
The extension treats payment recovery as an explicit operational workflow rather than an uncontrolled retry mechanism.
Payment failure detected
A supported payment failure event is captured together with the relevant order context.
Context normalized
Useful identifiers and failure information are normalized into a consistent recovery record.
Recovery rule evaluated
The extension determines whether recovery handling is allowed, suppressed or requires manual intervention.
Outcome recorded
The resulting action and state are logged so the workflow remains observable and auditable.
ADMIN VISIBILITY
Operational context without database inspection
The administration interface is intended to expose the information required to understand a failed payment and its recovery state while keeping the workflow bounded and maintainable.
COMPATIBILITY
Compatibility is verified before release
Version support is published only after standalone installation and runtime testing.
| OpenCart | PHP | Status |
|---|---|---|
| 3.0.3.x | Testing pending | In validation |
| 3.0.4.x | Testing pending | In validation |
RELEASE STATUS
Not publicly released
Payment Recovery is currently undergoing standalone packaging, dependency removal and compatibility testing. Marketplace availability, pricing and final version support have not yet been published.
RELEASE REQUIREMENTS
What must be complete before release
The release is gated by installation, compatibility, lifecycle and documentation validation.
Standalone installation
Install successfully on a clean OpenCart environment without MyKite-specific code or unrelated extensions.
Compatibility matrix
Record the OpenCart and PHP combinations that have actually passed testing.
Lifecycle validation
Verify install, upgrade, configuration changes and uninstall behavior.
Operational diagnostics
Ensure failures expose enough information for practical troubleshooting.
Documentation
Complete installation, configuration, troubleshooting, upgrade and uninstall guidance.
FAQ
Payment Recovery questions
Current answers reflect the validation-stage product and will be updated as the release candidate is finalized.
Is Fencair Payment Recovery available for download?
Not yet. The extension is currently in standalone validation before public release.
Which OpenCart versions are supported?
Final OpenCart compatibility will be published after clean-install testing. Unlisted versions should be treated as unverified.
Which PHP versions are supported?
PHP compatibility testing is still in progress. Final supported versions will be listed in the compatibility matrix.
Does the extension depend on a specific OpenCart theme?
The release goal is a standalone extension without dependency on a private store theme or unrelated extension.
Does Payment Recovery automatically retry every failed payment?
No. Recovery handling is designed around explicit rules and controlled outcomes rather than uncontrolled automatic retries.
Will installation and uninstall instructions be provided?
Yes. Installation, configuration, upgrade, uninstall and troubleshooting documentation are part of the release gate.
DOCUMENTATION
Follow the validation and release documentation
Technical documentation will record compatibility, installation requirements, operational behavior and release changes as the extension moves toward a public build.