Would be nice to assgin a different Vendor Email for each form (rather than a global setting), as we have different staff members that manage their seperate payment items.

Please see details below from Elavon regarding the Sagepay url update to Opayo. We can see you have updated some other of your plugins bythe looks of it but not Opayo Form Gateway for Gravity Forms.

If you can please action before the deadline date of 31st March 2024 when it will stop working. Thank you.

Please see below:

Following the updates earlier this year with the Opayo gateway becoming a payment product under the Elavon brand; we wanted to let you know about further exciting changes.

Opayo has been a key member of the Elavon family for over three years now, and as we continue with the integration into Elavon we will soon make updates to the URLs you use for your transactions and reporting.

What does this mean?
The URLs you use to send transactions to Opayo will be changing to an Elavon domain and you need to make the changes to send your transactions to the updated URLs.

These changes must be made by 31st March 2024, this is when the SagePay URLs will cease to work.

We’ve already added these updated URL’s to our Developer Hub https://developer.elavon.com/ to help you make the changes, you can find the URLs specific to your integration below:

Pi integration
Direct integration
Form integration
Server integration
RAAPI
Shared API

If you’re using a shopping cart provider speak with them directly regarding this to make the relevant updates.

Important information
The HTTP standard of all headers is lower case with the new URLs, be aware of this if you have specific code to look for case sensitivity.
We recommend using domain names instead of hard code, if you have hard-coded an IP address in your website or shopping cart you’ll need to update this also.
Flush DNS cache (local) or Internet Service Provider (ISP) may cache DNS records. In this case, you will need to speak directly with your ISP to ensure you have the most up-to-date DNS records.
You will need to ensure the new URLs are whitelisted and any firewall rules you have in place have been updated.
If you have implemented a content security policy you will also need to update this.
As always, we recommend testing any changes you make in your testing environment before implementing them to production.

Upgrade your protocol version
When making these updates take this opportunity to upgrade to our latest protocol version.

Following previous communication on 31st January 2024 we are retiring protocol version 2.22 and 2.23, this would be a great opportunity to upgrade to our latest protocol version ensuring your transaction are processed compliantly and you have access to all the latest features that Opayo have introduced.

We’re here to help
For advice on making the relevant changes please contact your account manager, or contact support directly at [email protected] or 0191 313 0299.

Many thanks
Opayo by Elavon Team

• This topic was modified 9 months ago by Steven Stern (sterndata).

We have some instances where payments are not going through and have been advised by SagePay that there is a limit of 50 characters on the billing address 1 field which was being exceeded.

Can the plugin take care of enforcing this limit?

The error on the SagePay side when the address exceeds this limit.

5080 : Form transaction registration failed.

Hi there,

I have seen a few posts but no definitive answer to why we keep getting 5080 : Form transaction registration failed. Some say it’s the Country, and some say it’s encryption. Can you guys please give me some idea if both these issues are solved and if not how to solve them short term and a roadmap to solve them long term

Hello,

I seem to be having an issue with the plugin.

The error is;

Warning: openssl_encrypt(): IV passed is only 11 bytes long, cipher expects an IV of precisely 16 bytes, padding with \0 in /home/customer/www/charterhouseclaims.com/public_html/wp-content/plugins/sagepay-form-payment-gateway-for-gravity-forms/class-gf-sagepay-form.php on line 877

On sage pay

Error processing transaction
5080 : Form transaction registration failed.

Can you help?

Thanks, Stephen

The settings page is missing; I can see from the payments log that it is not including the details to crypt the payment so i need to enter these details so i am getting the 5080 error from sage pay.

Is there any reason the settings page is now missing and that the settings that were there before are no longer stored?

[VPSProtocol] => 3.00
[TxType] => AUTHENTICATE
[Vendor] =>
[Crypt] => @913c7f04ba24f0da3a919d648f9e515ef3c706d2d999265b3607a963cfc8341b7e91379f9a319b0330838b9a2fdf8bf84a285542c5ddf3a3f791c0b7d26e07f3b1f73e388f9ff701c7bb9b3bd49e74b06404504ec76f9d12cf06baadf47d305d3816f96354f08efeae3f4207c2b76c7b9c1dce9b8bc78da71bbb3f883ca5a97e52aff45c1e5bc6217a04ab9b17d8e6932d26185f2c246b4dd401ea34b9e0b71659de69f706aa4b2fa1fa5d42f5f0ec6d27792e5fe3eb8b9e3438417ea11b06e8bd6ed546771a738dbae7dc8f94bf1b7625a3e41809c73ff6ec1dc2ab6f0e46c2b9daf12f84ea9f79e83b886976adfabda6445caef901b4ae6ff81e8331bad566207b608bc17b023c22cceb46f054a8d25a7076829acd1ead31c8540c810e9aea251109319b7a41fba700d4dd9ec0c50e6f1ac7f2bd32266e8251568fdad73b07ae22104cafd7f2853a30cf0f9c2c33023dc98d63a5c035c5bd77c19478ac3adb62a8a493393738fd15dabc7f019e4cd808765eae0829774ea991c04d415e538a19b317fef1fb4e6756a84f548e36af1182cade537c05a8100d0ada7f275ac5314a8d524b928eb3ee8f9015d55832e81587e666db20418e28eee8868263f648867111a3b5ad5499a5a000c7a210510ba4179bcc654c8c2b0afcf80e24ec94411f2f0c632425f63f8fd80e4a1f7c00bb45dfaae7dc3b78b33177f1d4616fa604fc26b293925b19da3be461fb837e0ed1c9027fc86fef2243c66950d6d655283622d8ebe0c5c715233264b799a451ee7f5841467a105f97219c10abc91a8c9ae0e1cf57e627db0d9b0c25c823b4e961c40c58ae1bedfed06275005fe67bb37d5bdf25e3915c1809e63fbb9a57b7939c849362bbfaf22340277e735428a109b009b99cca943e1114988f1c3523d0b6b78caaa44731a1bb44f7550a83beeb6659956f1a2ad423e52691ca78a5d3736f21f8cfaae3d92281645684c5649b33e2b30820dd45c52718fecf0ab34cd58e823dd05c7ef1291b5ef59930c6f322412826fa60fba1bd4327e8ba041e1a23edb0470f023950ec513d6e8fee65144f0a2df3eee4f0cf0fc17d34c48c54516bd3b898e05f561fe0d869f086168a9a05a8090f53eef1f0160e56324a0111c4001cbad53fe3b5d221c09066dd61d6367943c73c873183ee3cd9d4a2c599d047bbc58b343eab61d54e5427715290440c8ad1e27c963fb1ee67aef0ff47164bc1d99eff29d237

This has only been in the last 2 months since the last update

The custom_field variable is created twice, once with the entry ID and a hashed entry ID and the other with the entry ID and the current timestamp.

Line 751 – $custom_field = $entry[‘id’] . ‘|’ . wp_hash( $entry[‘id’] );
Line 772 – $custom_field = $entry[‘id’] . ‘-‘ . $time_stamp;

In the get_entry function, there is a validation to ensure the entry ID has not been tampered with:

Line 1667 – list( $entry_id, $hash ) = explode( ‘|’, $custom_field );
Line 1668 – $hash_matches = wp_hash( $entry_id ) == $hash;

The second setting of $custom_field on line 772 is causing the issue. Is the line on 772 safe to remove?

We’ve been made aware of the upcoming introduction of Strong Customer Authentication (SCA) to SagePay (now Opayo): https://www.opayo.co.uk/strong-customer-authentication-hub

We were sent this link explaining how transactions now need to implement 3D secure authentication: https://developer-eu.elavon.com/docs/opayo/spec/api-reference-0#section/Transactions-without-3-D-Secure

What we’d like to check is whether there’s anything to worry about if we’re using this plugin, e.g. does the plugin need to be updated to be in compliance with the new regulations and protocols?

Came across a previous support thread here (https://www.ads-software.com/support/topic/the-billingcountry-value-is-missing-in-sagepay/) which has gone unanswered, and I had exactly the same issue earlier today.

I can’t reply to that topic, so for anyone that comes across the same issue – if you’re getting a 5080 Form transaction registration failed, and SagePay is telling you that the BillingCountry field is invalid, make sure that your form’s Country field is sending the full country name instead of the ISO code (i.e. United Kingdom instead of GB) as this plugin converts the country name *to* the ISO code to send to SagePay, and in my opinion doesn’t handle it at all correctly if it’s already receiving an ISO code.

So anyway, on to the main point of this topic – is this plugin still being developed? Because this is a big enough issue IMO that it should be fixed, but if the original developers aren’t still maintaining it, I don’t know whether to fork the plugin and put a fix up, or ask them if they want me to submit a patch.

Hi,

Is your plugin compatible with the latest WordPress and Gravity Form?

We are using the webhook addon to send data to a CRM, but the webook is triggered after the form submission before completing the payment.
We contacted Gravity forms support and below is their reply:

“The webhooks add-on does support the delayed payment feature but the payment add-on needs to support it as well.

You’ll need to contact the developer of the Sagepay add-on and ask them to update their add-on to support the GFPaymentAddOn::get_post_payment_actions_config() and GFPaymentAddOn::trigger_payment_delayed_feeds() methods which Gravity Forms added support for in version 2.4.13”

Can you please add that feature or is there any workaround?

Hi PatSaTECH

I have recently installed this plugin and when I’m testing I get a ‘3189 : The vendor data is invalid’ error message in Sagepay account

Looking at the data sent, I can’t see what’s wrong e.g.

‘vendordata=300|300 vendortxcode=10-200602153612 amount=300 currency=GBP description=Order #10 vspterminal= address= postcode=’

It looks quite simple formatting issue is this something you could help with?

Many thanks
nickstaw

Hello there,

I have enabled Send E-Mai Customer and Vendor but nothing is going to customer. Could you advice?

• This topic was modified 4 years, 9 months ago by Tanmay Kumar Das.

Does this plugin allow for ACH?

Is this plugin compliant with 3D Secure v2?

I’m trying to connect a Gravity Form to a SagePay test server but I’m not seeing any of my payments appearing within the MySagePay admin. I’m getting the following from the add-on log:

DEBUG --> GFFeedAddOn::maybe_process_feed(): Checking for feeds to process for entry #6 for gravityforms-sagepay-form. 
DEBUG --> GFFeedAddOn::maybe_process_feed(): No feeds to process for entry #6. 

Does this mean there is a problem connecting to Sage Pay?

• This topic was modified 5 years, 10 months ago by joffff. Reason: submitted in error
• This topic was modified 5 years, 10 months ago by joffff.

Hi

A client’s been having problems on one of their gravity form sites , it is a donation form which has worked fine in the past , but now the form is failing , we are seeing 5080 errors, so assume this was down to the encryption key being wrong.

The sagepay form payment gateway plugin was recently updated and the client noticed the encryption key , vendor details were blanked out. The incorrect key was added, this has been corrected, but we are still seeing the 5080 error and can only think it is related.

Is there anything that could be stopping that key from updating?

any assistance greatly appreciated
Thanks

On a couple of occasions now, the settings page for SagePay for Gravity Forms has cleared itself, removing all of the data.

Any idea what could be causing this?

Recently we’ve picked up a lot of these 3189 errors, stating “The vendor data is invalid”.

From looking at the detailed error messages in SagePay, I can see the things that connects all these recent errors is that the payer has used a non-alpha-numeric character in their name (such as “David Benton-Smith” or “Dara O’Brian”). These are the only transactions that are failing and returning this error, and this has only started since the last plugin update.

Is this something happening in the plugin, or something at SagePay’s end?

Hey,

Since the latest update, we are now getting this error on payments:
https://www.sagepay.co.uk/support/error-codes?keyword=3020

Can you please investigate?

Hi there
First of all thank you so much for creating the plugin
Unfortunately it doesn’t work with PHP 7.2
Can we expect an update please?

https://www.ads-software.com/plugins/sagepay-form-payment-gateway-for-gravity-forms/

• This topic was modified 6 years, 2 months ago by Tanmay Kumar Das.

You’re using PHP 7.2 and that PHP function no longer exists in PHP 7.2 as it has been deprecated: https://php.net/manual/en/function.mcrypt-encrypt.php

do you plan to do an update that supports php 7.2 it is very fast and works with all our plugins.

Regards

I have a text field in my form with GB within it, and sagepay settings are pointing at this for the billing country.

But when I submit the form, I am getting an error.
Looking at the error in sagepay test area shows the the billingcountry= is actually blank and not picking up the billing country field from my GF form.

Every other field works as expected.

Hello I am having issues with my gravity forms and the transaction failing with a 5080 error.
I have seen other threads in your support, (I did comment there but forum masters deleted my post as it was an old thread?) I have made sure that the currency is GBP and have looked in the sage account to see if it expands on the error but Sage does not even register the transactions – it is almost like it fails before getting through to Sage.
Looking through the Sage forums it says that a 5080 error could be an issue with encryption.

In certain circumstances the transaction will not show up in this screen, indicating a problem with the encryption used on your post.

This has been working on the site for well over a year with no problems but a few days ago it just stopped working. Have you any ideas of what is causing the issue?

Below is a copy of the debug from your plugin – unfortunately it doesn’t mean much to me:

2017-10-04 15:34:51.785710 - DEBUG --> GFFeedAddOn::maybe_process_feed(): Marking entry #4585 as fulfilled for gravityforms-sagepay-form 
2017-10-04 15:34:51.995661 - DEBUG --> Sending to SagePay Form: {pre>Array
(
    [VPSProtocol] => 3.00
    [TxType] => PAYMENT
    [Vendor] => VENDORNAMEWAS HERE
    [Crypt] => @9a1f5e7decd7bb7a23be288a7a1933010f1e0c04df90307bf5d63d4f2a9b59cca44100a2990cb572978dbbf5fa36ddd37b054477ef9c06094461c36d5f7ada9321e1f5390b80fd9bdec75eb791850c454181417b37c4042dd4e8dbd9815a76df435cd54ecd5e1c4dc77bdfdd3e74a5894fc9ab29cc5b2e15ac71be97f3c609629cd254933824f6b31ff9e8aa50b079af199c0c9c452c10822bbca9f6818e67dfed22f660d1d75a3cd2aaf4672693fb9c71ee2fbdc3cdc257245bc6d73b0fb7b3e4cb50b121a77a8c3f6245613c43f1cad3e7d87ba94032b64e76c05870758d1282cd8629307a8b6bb57babd97cad982ead236cb28b74f3f7ceccbbc851557d2a2fb39814dba694ad914140563d0fc12f812155eebca8424d72faed0e44310568eb19c8912cf5b3830dc0a4f8a6a91d64387a8fff4d45f594a4872d357ca8c476ffbc8709cab4e97f058c9864f433af909c75f09d948ec3c262e18c7d40598cf5bb82ee7d1d051b8ed86736e625f8705e8384e70985f50b14e147ff7b907c23eabc4c5651dd4f16b066c432a70f49625d6054bf2570f2f1008084d74a5e1c24e60c82dd493eb0b5da51a710fc5fc0169975f9d9785565542ab60eaca27b30f1c75d5af4d267695b5640873d2d9e02faa072b9be2075b3e97d9a20fe38c4315aad694ec09dc4cf42ccc044bb21277b8aab9934de9a84b2ccc7e0a9e2c32c2e6bd178668483727207181429159e83fe55976449ef9bfa2f7f78bd42cc9a5e1d6c4a9b6caf9398691feb56e2ddb3a888bb4f5e011746af04aa92ae561ed405dd3ef06d115d8d4a6b63496d7754e433e419d075059b3c48205250190295bf372eb77c7a3f87c6e353f1aa1218066fb56854b891c7aba7038e382aa41b670ade67569c336046d5cc7dac80d7bf5edcd749109324aa8d31a1341fa5c1f6ffe8964422bd9e93467d033076511990d4fff325c16266aebf48edb489bf2e8f28d0368000c9121a64add684974c55df87b2e42c4a4f3c98aa7605613d9fb6e4b38f5b412d92a62284027abbb1b4b579551843bcff49
)
/pre>} 
2017-10-04 15:34:56.738662 - DEBUG --> GFPaymentAddOn::maybe_process_callback(): Initializing callback processing for: gravityforms-sagepay-form 

All plugins on the site are at the latest version, any help would be greatly appreciated.

Hi

Hope you can advise.

A client has a form they want to accept donations from site visitors in either euro , pound sterling or US dollar.

Form can bew viewed here – https://beta.innovista.org/donate/

I am using the gform_currency filter to change this value in the form which seems to translate well , we sbmit between pages and the donation values updates OK , but when we submit to sagepay it only shows the donation value in GBP.

Is there a filter, a value , a form field we can use to tell sagepay we want to handle a Euro or dollar value?

Thanks

Hi – thanks for a great plugin which does just what I need it to!

However, when I submit the form, unfortunately I get an HTTP 414 error saying the URL is too long.

This isn’t your fault; it’s because SagePay’s system works by sending the whole encryption string through GET. In my own implementation, I put the following which effectively converted the GET string to a POST one which could then be sent through to SagePay without the 414 error:

<form method="POST" id="SagePayForm" action="https://live.sagepay.com/gateway/service/vspform-register.vsp" target="sagepay">
			<input type="hidden" name="VPSProtocol" value="3.00">
			<input type="hidden" name="TxType" value="PAYMENT">
			<input type="hidden" name="Vendor" value="merchantnamehere">
			<input type="hidden" name="Crypt" value="' . $sagePay->getCrypt() . '">
		</form>

		<script type="text/javascript">
			// Submit the above form automatically to load into the iframe below, or show the
			// "Go to SagePay" button instead if the screen is too small
			jQuery( document ).ready( function( $ ) {
				if ( $(document).width() < 600 ) {
					$( "#open-full-window" ).show();
				} else {
					$( "#open-full-window" ).hide();
					$( "#SagePayForm" ).submit();
				}
				$( document ).on( "click", "#open-full-window", function() {
					$( "#SagePayForm" ).attr( "target", "_self" ).submit();
				});							
			});
		</script>

Is there any chance you’d be able to enhance your plugin to allow it to send via POST instead of GET, using this or some other method?

I’ll leave it with you anyway. Thanks for your great work! ??

Tim

Hi there,

Through doing lots of testing on test mode I have found that the plugin does not support the “REJECTED” transaction response type.

Because of this, it redirects the callback to a blank page that says “Callback bypassed”.

To fix this:

1. Open plugins/sagepay-form-payment-gateway-for-gravity-forms/class-gf-sagepay-form.php
2. Above case “FAILED” :, add in case “REJECTED” :
3. Save the file and upload
4. All rejected Sage Pay payments will now redirect to your “Cancel URL” in the settings.

Please can you apply this fix ASAP as this will be affecting a lot of sites that use this plugin.

The way you can replicate this is by entering in invalid card details 3 times to trigger error 5025 (The number of authorisation attempts exceeds the limit.) link: Source

Thanks

I am using Gravity Forms 1.2.1 and SagePay Form Gateway for Gravity Forms 1.1.2 with WordPress 4.7.

I am managing two separate WordPress installations which live on the same domain. The first instance has been operational and integrated with Gravity/SagePay for a couple of years. Recently there was an attempt to set up a very similar form on the second instance.

This second (newer) instance was set up with the exact same SagePay information as the first instance. For example, it is configured in live mode and with the same encryption key (etc).

I’ve since taken over maintenance and am debugging an issue that is happening consistently. Even given the simplest form possible (first name, last name, email, address, hidden product), once redirected to SayPay there is a 5080 : Form transaction registration failed. The form submits fine, but the error is thrown by SagePay on page load and there is no way of progressing. It happens every time.

My understanding is that this is a generic error from SagePay, so the code itself doesn’t help in tracking the issue down.

Please let me know if you are aware of anything that may cause this. Failing that, please let me know how I can approach debugging the pre-encrypted request body.

Any help appreciated. Thank you.

Looking to do a recurring payment/monthly payment. Any way to do this with SagePay?

https://www.ads-software.com/plugins/sagepay-form-payment-gateway-for-gravity-forms/

Can I use this plugin for Sage Payments USA?

https://www.ads-software.com/plugins/sagepay-form-payment-gateway-for-gravity-forms/