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
Describe the bug
I just recently published my extension to the Chrome Webstore and when I try to make a purchase the popup prompts the following error: "A network or server error occurred. Please try again." "Server error. Try your payment again."
To Reproduce
Steps to reproduce the behaviour:
Go to ExtPay popup
Enter email and bank data
Click the Subscribe button
See error
Expected behaviour
It should make the purchase. In my bank app a popup appears: 'Focus Ex Subscription - Validation of bank cards' but in the ExtPay popup on my desktop screen the following screen is shown and no purchase is made.
Screenshots
Desktop (please complete the following information):
I reconnected the extension profile in the ExtPay console to Stripe and now the purchase works properly. However, this way created a new Stripe account. Is it possible to reconnect to the previous Stripe account? Every time I connect to Stripe, it creates a new Stripe account for the extension.
Describe the bug
I just recently published my extension to the Chrome Webstore and when I try to make a purchase the popup prompts the following error: "A network or server error occurred. Please try again." "Server error. Try your payment again."
To Reproduce
Steps to reproduce the behaviour:
Expected behaviour
It should make the purchase. In my bank app a popup appears: 'Focus Ex Subscription - Validation of bank cards' but in the ExtPay popup on my desktop screen the following screen is shown and no purchase is made.
Screenshots
Desktop (please complete the following information):
Version 1.70.119 Chromium: 129.0.6668.70 (Official Build) (arm64)
Version 129.0.6668.60 (Official Build) (arm64)
Additional context
You can find and download and check my extension from:
https://chromewebstore.google.com/detail/focus-ex/dlchhkpnfagokiecakphcgilhgdimkkg
The text was updated successfully, but these errors were encountered: