DIYWebHosting Posted November 6, 2008 Share Posted November 6, 2008 I am currently testing out PayPal's Website Payments Pro Canada service and their Advanced Fraud Management Filters service and noticed that the WHMCS module is not passing the billing address/IP information to PayPal. While the transactions still go through fine, it renders PayPal's fraud filters useless since it has no data to work with. My WHMCS gateway log is reporting errors such as this for every transaction: ACK => SuccessWithWarning VERSION => 3.0 BUILD => 739997 L_ERRORCODE0 => 10751 L_SHORTMESSAGE0 => Invalid Data L_LONGMESSAGE0 => There's an error with this transaction. Please enter a valid state in the billing address. L_SEVERITYCODE0 => Warning L_ERRORPARAMID0 => ProcessorResponse L_ERRORPARAMVALUE0 => 0000 When viewing the transaction in PayPal it is also missing all of address information in the report. Would it be possible to have the module updated to pass along the billing address/IP info to PayPal so their fraud filters will be able to function? Note that I am using the just released Canadian version of this service. I am under the impression that it is identical to the US version, but perhaps there is small differences. Are people using the US version having this problem? Link to comment Share on other sites More sharing options...
apollo1 Posted November 6, 2008 Share Posted November 6, 2008 I am also using PayPal Pro and would like to see a fix for this issue. Thanks DIY for posting. Link to comment Share on other sites More sharing options...
magga Posted November 6, 2008 Share Posted November 6, 2008 I know this isn't possible for the UK version, possibly this is the case for the Canadian one too? Link to comment Share on other sites More sharing options...
DIYWebHosting Posted November 6, 2008 Author Share Posted November 6, 2008 Matt has checked on this and said the variables are still the same for the API so it's being sent, but is giving an invalid data error for some reason. Perhaps there are differences in the Canadian version, but their API docs just point to the US version's, so I would assume everything should be the same. Can anyone else confirm if this is happening to them and what version you are using (US, UK, Canada)? Link to comment Share on other sites More sharing options...
danami Posted November 6, 2008 Share Posted November 6, 2008 This is going to be hard to test out as the Paypal sandbox only supports the U.S. version of Paypal website payments pro (They don't have a Canadian version of the sandbox yet so you'll have to test it on a live system). Link to comment Share on other sites More sharing options...
danami Posted November 7, 2008 Share Posted November 7, 2008 (edited) Well with the US sandbox it seems to be passing the address right so I guess that only a problem with the Canadian version. I have discovered other problems though .. WHMCS allows you to enter anything for the state. So my client had "Alberta" instead of the abbreviation (which paypal expects) "AB" .. and the paypal website payment pro gateway log reports "success" with errors: AMT => 39.90 CURRENCYCODE => USD AVSCODE => X CVV2MATCH => M TRANSACTIONID => XXXXXXXXXXX TIMESTAMP => 2008-11-07T19:10:30Z CORRELATIONID => XXXXXXXXXXXXX ACK => SuccessWithWarning VERSION => 3.0 BUILD => 739997 L_ERRORCODE0 => 10751 L_SHORTMESSAGE0 => Invalid Data L_LONGMESSAGE0 => There's an error with this transaction. Please enter a valid state in the billing address. L_SEVERITYCODE0 => Warning L_ERRORPARAMID0 => ProcessorResponse L_ERRORPARAMVALUE0 => 0000 So even with the address being sent to paypal .. any type of address verification / fraud detection is going to fail anyway because Paypal expects ISO Region codes instead of the full region name. The only way I see to fix this is to have ajax country / region select lists .. anyone else have a better idea? Edited November 7, 2008 by danami Link to comment Share on other sites More sharing options...
DIYWebHosting Posted November 8, 2008 Author Share Posted November 8, 2008 You're right, when the abbreviation is passed it resolves this error even for the Canadian version. I'd really prefer a country/state select list over having customers type in this information to prevent against typos overriding the tax rules. Link to comment Share on other sites More sharing options...
Recommended Posts