A recent Truvo gateway update resolved duplicate order issues and introduced a new blacklist feature for enhanced fraud control. This guide outlines the step-by-step process our development team followed to test and deploy the updated Truvo plugin safely to a live WordPress site.
Issue background
The Truvo payment gateway released an update on November 29 designed to address two major concerns:
- Duplicate order processing – Some merchants experienced multiple identical transactions being processed.
- Chargeback abuse – To combat frequent chargebacks, Truvo added a new Blacklist tool, allowing merchants to block specific customers from future purchases.
This update promised improved performance and stability, with additional upcoming features like a statements tab and one-click checkout.
Diagnosis
The previous plugin version (labeled 1.0.0-BETA) remained installed on the client’s site. While Truvo confirmed that the update would resolve duplicate transaction issues, it was crucial to verify functionality in a safe environment before updating live.
Our developer initiated the process on the staging environment, ensuring that all payment gateway operations and order flows worked without issues.
Resolution steps
1. Test the updated plugin on staging
- Logged into WordPress > Plugins.
- Deactivated and deleted the old Truvo plugin.
- Navigated to the Truvo API documentation portal and downloaded the updated version of the plugin (accessible via the green download button).
- Reinstalled and activated the plugin on the staging site.
- Confirmed the version remained labeled 1.0.0-BETA, which was expected despite the internal updates.
- Verified checkout flow and transaction behavior – no duplicate order issues were observed.
2. Validate stability and confirm approval
QA confirmed no errors or disruptions. The project manager and QA lead both reviewed the staging site to confirm no visual or functional regressions.
3. Deploy to live
- After confirmation, the plugin was updated on the live site following the same process:
- Deactivate and delete the previous version.
- Upload and activate the new plugin.
- Perform a live test transaction to confirm proper checkout behavior.
4. Rollback plan
To ensure minimal downtime or disruption, a rollback plan was prepared:
- A BlogVault backup was taken before the live update.
- If issues were found post-launch, reverting to the previous plugin version would simply involve restoring the backup and clearing caches.
Final outcome
The new Truvo gateway plugin was successfully deployed to the live site without incident. Post-launch testing confirmed the resolution of duplicate orders and verified that the new blacklist feature was functioning correctly. The site’s checkout remained stable, and the update enhanced overall payment reliability.
Key takeaways
- Always test payment-related plugin updates in a staging environment before applying them live.
- Maintain a backup and rollback plan using tools like BlogVault for safety.
- Confirm version labeling directly with the plugin vendor—sometimes internal patches retain the same version number.
- Communicate closely with your payment processor’s support team for additional release notes or hidden feature flags.
Need help with plugin updates or payment gateway integrations?
Freshy’s WordPress experts specialize in safe, reliable plugin management and payment integration troubleshooting.
👉 Contact us today for expert help
