You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@DethonUSAL, a little late but I came across a similar issue today while using another gem. It seems that Spree uses is_risky? method on orders, which in turn checks if payments are risky (scope here), which in turn is verifying whether CVV was correct and address was verified. Since paypal has neither a CVV nor an address verification, they are marked as risky.
Thank you, I had this in the backburner for a while. As of now I'm marking all PayPal payments as not risky in my test deployment. I wonder if there is a better way to address this.
When I use PayPal as my payment method the order is marked as risky in the admin panel.
Is this expected? and if so, why?
Also, I don't know if it's related, but I'm using a sandbox Braintree account.
The text was updated successfully, but these errors were encountered: