Do you mean to include the State value? If so can you give an example of what is required.
As it currently stands it looks as if the default SagePayPaymentMethodService doesn't support selling to the US?!
RE:Out of curiosity: Is this a setting in SagePay or a default?
Not sure what you meant by that but the error occurs prior to landing on the Sagepay site, and I have not changed anything in relation to what is passed through to SagePay.
I deliberately made the fix so it wouldn't include the billingState and deliveryState if no value is present. Should I take it that in some circumstances the field is actually required? The reason I ask is that I just ran a couple of transactions through the simulator and can't reproduce it so I assume that it might be caused by differences in our set up of the gateway account.
Yes, it was fine with our testing account. As soon as I moved to the client's credentials the error began to occur. I would assume there's something in their set up. I've not really had the time to look into why now it's working.
SagePay: The BillingState field is required
Have been going through the Sagepay itegration for uCommerce and get the following at the "checkout/submit" page.
Error: Malformed, Message: 3147 : The BillingState field is requiredWhat needs to be modified to supply this to SagePay?
Hi Simon,
You'll need to override the RequestPayment method on the default SagePayPaymentMethodService.
Out of curiosity: Is this a setting in SagePay or a default?
Hi Soren,
Do you mean to include the State value? If so can you give an example of what is required.
As it currently stands it looks as if the default SagePayPaymentMethodService doesn't support selling to the US?!
RE:Out of curiosity: Is this a setting in SagePay or a default?
Not sure what you meant by that but the error occurs prior to landing on the Sagepay site, and I have not changed anything in relation to what is passed through to SagePay.
Sorry I haven't seen SagePay used for sales outside the UK yet hence the confusion.
I went ahead and added the state field for you in the latest 2.1 prerelease.
Thanks Soren,
Most of our clients use SagePay and a few rely on US orders.
What do you suggest - do I upgrade to 2.1 prerelease or for the short term override my current copy?
Go with the upgrade.
Have upgraded to 2.1, and modified my checkout xslt e.g. UpdateAddressInformation[xslt], but I now get:
Error: Malformed, Message: 3148 : The DeliveryState field is required..Does this mean the SagePay service needs updating to include it also?
I forgot to add a field to the provider. It's there in the latest 2.1 package.
Has this gone beyond prerelease? I'm having the same issue
Has this gone beyond prerelease? I'm having the same issue
Has this gone beyond prerelease? I'm having the same issue
Has this gone beyond prerelease? I'm having the same issue. And, the link is dead
For others info (and hopefully posted just the once) the link is corrupted. Should be http://www.ucommerce.dk/releases/uCommerce-2.1.0.0.zip
FYI: This still throws up an error if no (or an empty) state is passed.
Hi Tony,
I deliberately made the fix so it wouldn't include the billingState and deliveryState if no value is present. Should I take it that in some circumstances the field is actually required? The reason I ask is that I just ran a couple of transactions through the simulator and can't reproduce it so I assume that it might be caused by differences in our set up of the gateway account.
Yes, it was fine with our testing account. As soon as I moved to the client's credentials the error began to occur. I would assume there's something in their set up. I've not really had the time to look into why now it's working.
I recently had a similar issue with the simulator behaving differently from the test environment. Maybe this is what you're seeing?
In the other case though it affected how voids were being handled for newly authorised transactions.
is working on a reply...