WPIntell

Source evidence

The website of this connection is not available

SumUp Payment Gateway For WooCommerce · support · 2026-02-04T14:57:00+00:00

complaintsentiment
highseverity
1.0relevance
4replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

6 / 28 rows with source links

21.4% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

22 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
tqfan unresolved
Hello, I have downloaded and activated the ‘ SumUp Payment Gateway For WooCommerce ‘ plugin. When I go to ‘connect account’, I get the error ‘The website of this connection is not available’. How do I fix it? Thanks. I’m also receiving the same message when trying to connect. Plus, this Warning is repeated twice when plugin is activated :- Warning : Trying to access array offset on false in /########/wp-content/plugins/sumup-payment-gateway-for-woocommerce/includes/class-wc-sumup-logger.php on line 25 Have tried disabling all plugins except woocommerce & Sumup. PHP Version 8.4 WordPress Version 6.9.1 Can we have some guidance please. I believe this issue was introduced in the latest release, it seems all wp-json/sumup_connection/v1 endpoints which are used on the connect flow now requires authentication and an user with admin permissions. This are the changesets: https://plugins.trac.wordpress.org/changeset/3454868 The problem is when SumUp need to execute callback for completing the configuration and validation process, these request are unauthenticated: 52.48.211.42 - - [11/Feb/2026:19:04:41 +0100] "GET /wp-json/sumup_connection/v1/validate HTTP/1.1" 401 116 "-" "Resteasy Reactive Client" 52.48.233.7 - - [11/Feb/2026:19:08:44 +0100] "GET /wp-json/sumup_connection/v1/validate HTTP/1.1" 401 116 "-" "Resteasy Reactive Client" 52.48.211.42 - - [11/Feb/2026:19:11:07 +0100] "GET /wp-json/sumup_connection/v1/validate HTTP/1.1" 401 116 "-" "Resteasy Reactive Client" 52.48.211.42 - - [11/Feb/2026:19:11:46 +0100] "GET /wp-json/sumup_connection/v1/validate HTTP/1.1" 401 116 "-" "Resteasy Reactive Client" Obviously, no bearer token or user creds are sent to SumUp servers on this flow and SumUp receives Unathorized Request when executing the callback to our wordpress, also SumUp UI is not so verbose so you cannot figure out what is really happening. I am also having this issue. Really frustrating! I am getting these errors which I think all relate to the same core problem. Hope this gets sorted soon! 2026-02-16T19:54:39+00:00 Debug ==== SumUp Version: 2.7.10 ==== Merchant ID: === Start Log === Error on get access token. Missing client_id === End Log === 2026-02-16T19:54:39+00:00 Debug ==== SumUp Version: 2.7.10 ==== Merchant ID: === Start Log === Error on settings to create access token. Merchant Id: === End Log === 2026-02-16T19:54:51+00:00 Debug ==== SumUp Version: 2.7.10 ==== Merchant ID: === Start Log === Error on get access token. Missing client_id === End Log === 2026-02-16T19:54:51+00:00 Debug ==== SumUp Version: 2.7.10 ==== Merchant ID: === Start Log === Error on settings to create access token. Merchant Id: === End Log === They emailed me to say they’d fixed the issue and to update the plugin. The problem is still there. Told them that and heard nothing back…

Comments

4 shown
jammerw 2026-02-10T00:07:00+00:00

I’m also receiving the same message when trying to connect. Plus, this Warning is repeated twice when plugin is activated :- Warning : Trying to access array offset on false in /########/wp-content/plugins/sumup-payment-gateway-for-woocommerce/includes/class-wc-sumup-logger.php on line 25 Have tried disabling all plugins except woocommerce & Sumup. PHP Version 8.4 WordPress Version 6.9.1 Can we have some guidance please.

jpescalona 2026-02-11T19:54:00+00:00

I believe this issue was introduced in the latest release, it seems all wp-json/sumup_connection/v1 endpoints which are used on the connect flow now requires authentication and an user with admin permissions. This are the changesets: https://plugins.trac.wordpress.org/changeset/3454868 The problem is when SumUp need to execute callback for completing the configuration and validation process, these request are unauthenticated: 52.48.211.42 - - [11/Feb/2026:19:04:41 +0100] "GET /wp-json/sumup_connection/v1/validate HTTP/1.1" 401 116 "-" "Resteasy Reactive Client" 52.48.233.7 - - [11/Feb/2026:19:08:44 +0100] "GET /wp-json/sumup_connection/v1/validate HTTP/1.1" 401 116 "-" "Resteasy Reactive Client" 52.48.211.42 - - [11/Feb/2026:19:11:07 +0100] "GET /wp-json/sumup_connection/v1/validate HTTP/1.1" 401 116 "-" "Resteasy Reactive Client" 52.48.211.42 - - [11/Feb/2026:19:11:46 +0100] "GET /wp-json/sumup_connection/v1/validate HTTP/1.1" 401 116 "-" "Resteasy Reactive Client" Obviously, no bearer token or user creds are sent to SumUp servers on this flow and SumUp receives Unathorized Request when executing the callback to our wordpress, also SumUp UI is not so verbose so you cannot figure out what is really happening.

willcaddy 2026-02-16T20:52:00+00:00

I am also having this issue. Really frustrating! I am getting these errors which I think all relate to the same core problem. Hope this gets sorted soon! 2026-02-16T19:54:39+00:00 Debug ==== SumUp Version: 2.7.10 ==== Merchant ID: === Start Log === Error on get access token. Missing client_id === End Log === 2026-02-16T19:54:39+00:00 Debug ==== SumUp Version: 2.7.10 ==== Merchant ID: === Start Log === Error on settings to create access token. Merchant Id: === End Log === 2026-02-16T19:54:51+00:00 Debug ==== SumUp Version: 2.7.10 ==== Merchant ID: === Start Log === Error on get access token. Missing client_id === End Log === 2026-02-16T19:54:51+00:00 Debug ==== SumUp Version: 2.7.10 ==== Merchant ID: === Start Log === Error on settings to create access token. Merchant Id: === End Log ===

tqfan 2026-03-12T18:43:00+00:00

They emailed me to say they’d fixed the issue and to update the plugin. The problem is still there. Told them that and heard nothing back…