I'm having some difficulties setting up Tea Commerce & Sagepay for orders from the U.S. I'm using the starter kit as a starting point for the site - but when the customer selects US as the country checkout process fails at the credit card payment step with :
Tea Commerce - SagePay - Error in GenerateForm - Status: MALFORMED - Status details: 3147 : The BillingState field is required.
It seems Sagepay requires a 'State' field - but is there an easy way to add that so that it's only visible when US is selected?
Having looked at this a little more - it looks like sagepay now require BillingState to be transmitted when US is selected as the country (since protocol 2.23) - but teacommerce doesn't seem to have an option to send this?
Any help would be gratefully received - it's installed on a live site so need to get it fixed asap.
There will be a new state property alias setting for your to configure at the payment provider. The only thing you have to do now is to implement a US state dropdown in your cart flow and parse the value of it and add it as an order property with the alias you specified earlier. Now it should be passed to SagePay - IF the country code of the order is "US".
Thanks so much for the quick response Anders - as we're looking to implement this asap on a live site - is there a way we can patch it without a completely new installation? Just a little nervous about a complete install on an otherwise working site :-)
Great to hear that you've got a fix in place already though!
The easiest way will be to upgrade. It should be pretty quick for you to make a copy of the site - setup a local/test site and then test the upgrade and fix. Its easy to upgrade - just install the new package like you normal do.
Hmmm maybe not - developer who worked on this project is away on holiday and I know there's been some modifications of the package to deal with this particular installation :-)
We can try a file diff though to try and trace through the changes I guess...
One last thing - having done some checks on the files now it looks like we've got an updated sagepay .dll and a modification to the en.xml to allow for the new configuration option. We noticed however that the original configuration option for ISO country code has disappeared - is this intentional? We were having problems previously with not sending this data to Sagepay - so wanted to check before proceeding...
The changes to the en.xml is just for localization. The ISO country code was a left over. The country code is coming from the order now and its relation to a country. This should not give you any problems.
Tea Commerce & Sagepay- The BillingState field is required.
I'm having some difficulties setting up Tea Commerce & Sagepay for orders from the U.S. I'm using the starter kit as a starting point for the site - but when the customer selects US as the country checkout process fails at the credit card payment step with :
Tea Commerce - SagePay - Error in GenerateForm - Status: MALFORMED - Status details: 3147 : The BillingState field is required.
It seems Sagepay requires a 'State' field - but is there an easy way to add that so that it's only visible when US is selected?
Thanks!
Andrew
Having looked at this a little more - it looks like sagepay now require BillingState to be transmitted when US is selected as the country (since protocol 2.23) - but teacommerce doesn't seem to have an option to send this?
Any help would be gratefully received - it's installed on a live site so need to get it fixed asap.
Thanks!
Hi Andrew
I have updated the sage pay provider to support US states. You will have to install the new 1.4.3.0 BETA 1 that I will upload later today here: http://our.umbraco.org/projects/website-utilities/tea-commerce
There will be a new state property alias setting for your to configure at the payment provider. The only thing you have to do now is to implement a US state dropdown in your cart flow and parse the value of it and add it as an order property with the alias you specified earlier. Now it should be passed to SagePay - IF the country code of the order is "US".
Kind regards
Anders
Thanks so much for the quick response Anders - as we're looking to implement this asap on a live site - is there a way we can patch it without a completely new installation? Just a little nervous about a complete install on an otherwise working site :-)
Great to hear that you've got a fix in place already though!
Andrew
The easiest way will be to upgrade. It should be pretty quick for you to make a copy of the site - setup a local/test site and then test the upgrade and fix. Its easy to upgrade - just install the new package like you normal do.
Kind regards
Anders
Hi Anders,
Hmmm maybe not - developer who worked on this project is away on holiday and I know there's been some modifications of the package to deal with this particular installation :-)
We can try a file diff though to try and trace through the changes I guess...
Thanks for the speedy update,
Andrew
Hi Anders,
One last thing - having done some checks on the files now it looks like we've got an updated sagepay .dll and a modification to the en.xml to allow for the new configuration option. We noticed however that the original configuration option for ISO country code has disappeared - is this intentional? We were having problems previously with not sending this data to Sagepay - so wanted to check before proceeding...
Thanks!
Andrew
Hi Andrew
The changes to the en.xml is just for localization. The ISO country code was a left over. The country code is coming from the order now and its relation to a country. This should not give you any problems.
Kind regards
Anders
Seems to be working for us - thanks for all your help Anders!
Great to hear - glad to help!
is working on a reply...