Posted: September 9, 2020 at 12:32 pm
We are running EE3 with Paypal Standard payment gateway integration. A nagging problem we’re battling is that when user is directed to Paypal to process payment – the proper tax in Canada as setup inside Paypal settings is not calculating properly when user selects “Pay via Visa or Visa Debit” option.
After a lengthy support ticket with Paypal directly, they advised that the issue is that the COUNTRY value that the registrant populated inside the EE3 registration form isn’t coming through in the URL string to Paypal when redirected.
First though was to change the QUESTION field from a text-field where user can type anything to a drop-down to control the COUNTRY options which could be passed however this is a system field and is not editable inside EE3.
Why does EE3 not pass the COUNTRY value? Or how can I ensure it passes to Paypal so tax is calculated properly? This is really messing up accounting if it’s not calculated properly from the data which Paypal takes from registration form and passes over to payment steps.
Thanks for any support or insights the forum can provide.
Anybody have any insights to help us, please?
Likely because this wasn’t an option with the country field when EE3 was developed.
That’s though due to the fact that the country field is a text field, which means users can input whatever they want and then that is what would be sent to PayPal, yet I’m sure PayPal expects specific values (likely ISO Alpha 2 codes).
Are all of the purchases from Canada? As in would it work to just set the country to Canada for every registration sent to PayPal?
Thanks for the reply. Truly appreciated.
No, we accept registrations and payments from people worldwide. So the tax implications and calculations that need to be properly shown at Paypal during payment are only applicable to Canadian residents.
Let me know if you have other questions. We’ve been battling this issue for numerous months and after a long, exhaustive support ticket with Paypal (which basically told us the issue is on EE3 side) – we’re running out of options.