Title: Sage Pay Protocol (version 3.00)
Last modified: August 21, 2016

---

# Sage Pay Protocol (version 3.00)

 *  Resolved [zakgrindle](https://wordpress.org/support/users/zakgrindle/)
 * (@zakgrindle)
 * [11 years, 11 months ago](https://wordpress.org/support/topic/sage-pay-protocol-version-300/)
 * Hi,
 * I have been advised by Sagepay to upgrade the protocol we are using from 2.23
   to 3.00. Does this gateway support this and work with 3.00?
 * Cheers,
 * Zak
 * [https://wordpress.org/plugins/sagepay-direct-for-woocommerce-payment-gateway/](https://wordpress.org/plugins/sagepay-direct-for-woocommerce-payment-gateway/)

Viewing 5 replies - 1 through 5 (of 5 total)

 *  Plugin Author [swicks](https://wordpress.org/support/users/swicks/)
 * (@swicks)
 * [11 years, 11 months ago](https://wordpress.org/support/topic/sage-pay-protocol-version-300/#post-5150568)
 * Hi
 * This version only currently supports 2.23, when SagePay stop supporting 2.23 
   or when there is a feature requirement to upgrade then we will upgrade to version
   3.00.
 * Regards
 * Steve
 *  Plugin Author [swicks](https://wordpress.org/support/users/swicks/)
 * (@swicks)
 * [11 years, 11 months ago](https://wordpress.org/support/topic/sage-pay-protocol-version-300/#post-5150904)
 * resolving this ticket – please feel free to re-open if you still have any questions.
 *  [Jason Judge](https://wordpress.org/support/users/judgej/)
 * (@judgej)
 * [11 years, 6 months ago](https://wordpress.org/support/topic/sage-pay-protocol-version-300/#post-5150937)
 * SagePay are no longer supporting the test instance of 2.23 from tomorrow (12 
   January 2015). Support for the production protocol will be removed July 2015.
   So the clock is ticking.
 *  [otaku888](https://wordpress.org/support/users/otaku888/)
 * (@otaku888)
 * [11 years, 4 months ago](https://wordpress.org/support/topic/sage-pay-protocol-version-300/#post-5150949)
 * Indeed this shouldn’t be marked as resolved as everything will stop working soon
   and pretending it doesn’t exist will not make it go away.
 *  [fdluk](https://wordpress.org/support/users/fdluk/)
 * (@fdluk)
 * [11 years, 4 months ago](https://wordpress.org/support/topic/sage-pay-protocol-version-300/#post-5150950)
 * This plugin hasn’t been supported for the last 6 months according to the plugin’s
   description.
 * For the plugin to use version 3 you can change line 133 in ds-sagepay-direct.
   php
 * from:
    `define('VPS_PROTOCOL', 2.23)`
 * to:
    `define('VPS_PROTOCOL', '3.0');` Don’t forget to include the quotes around
   the number.
 * It works fine for me.
 * NB simulator doesn’t work with version 3. You can only test in ‘Test’ mode

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Sage Pay Protocol (version 3.00)’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/sagepay-direct-for-woocommerce-payment-
   gateway_8284e5.svg)
 * [WooCommerce SagePay Direct Payment Gateway](https://wordpress.org/plugins/sagepay-direct-for-woocommerce-payment-gateway/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/sagepay-direct-for-woocommerce-payment-gateway/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/sagepay-direct-for-woocommerce-payment-gateway/)
 * [Active Topics](https://wordpress.org/support/plugin/sagepay-direct-for-woocommerce-payment-gateway/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/sagepay-direct-for-woocommerce-payment-gateway/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/sagepay-direct-for-woocommerce-payment-gateway/reviews/)

 * 5 replies
 * 5 participants
 * Last reply from: [fdluk](https://wordpress.org/support/users/fdluk/)
 * Last activity: [11 years, 4 months ago](https://wordpress.org/support/topic/sage-pay-protocol-version-300/#post-5150950)
 * Status: resolved