|
By Tiggywiggler - Sun 24 Jul 2016
|
Is anyone else getting a problem with SagePay states?
If a user puts their state as "CA" there is no problem with SagePay, if the user puts "California" then SagePay throws an error. I have read a post from 2014 that says that SagePay only accepts two letter states but I am struggling to believe that such an old rule would only now be giving me problems.
Was this California to CA conversion handled in a DLL that I am missing? If not I will need to write myself a library, I would have thought that the SagePay DLL would handle this.
Some Info:
http://www.sagepay.co.uk/support/error-codes/3130-%C2%A0-billingstate-value-too-long
|
|
By Tiggywiggler - Wed 27 Jul 2016
|
|
I have now written a library and a method to convert from the full state name to the state code and I pass the XML through this when I detect an order with 'SagePay' as the target and 'USA' as the destination country.
|