Take payments via SagePay Form AND SagePay Direct
When using SagePay Form, the customer is taken to SagePay to make a secure payment. Because SagePay handles the payment process for you, no SSL certificate is required on your site. After the customer completes payment, the order is confirmed and the user is taken to the Thank You page on your site.
When using SagePay Direct the customer stays on your site for the entire transaction, so an SSL certificate is required.
Comparison:
SagePay Form
When using SagePay Form, the customer is taken to SagePay to make a secure payment. Because SagePay handles the payment process for you, no SSL certificate is required on your site. After the customer completes payment, the order is confirmed and the user is taken to the Thank You page on your site.
When using SagePay Direct the customer stays on your site for the entire transaction, so an SSL certificate is required.
Comparison:
SagePay Form
- Customer is redirected to SagePay to complete payment – simplifies PCI Compliance
- SSL Certificate not required
- Customer stays on your site for entire transaction
- SSL Certificate required
- Supports WooCommerce Pre-Orders extension
- Supports WooCommerce Subscriptions extension
- Supports refunds in WooCommerce admin
Why choose NulledFire?
- ✅ Original GPL files
- 🛡️ Malware scanned
- 🔄 Updated daily
- 🌐 Unlimited websites
- 🔔 Email notifications
- 🚀 Fast CDN download
What's new in Version 5.16.1
* Opayo Direct - filter for failed order return URLs
* Opayo Direct - move token saving
* Opayo Pi - validate browserLanguage
* Opayo Direct - move token saving
* Opayo Pi - validate browserLanguage
What's new in Version 5.16.0
n/a
