Community Forum

Payment website has some serious problems

Xfinity Forum Archive
About the archive project

Xfinity Forum Archive...

This is an archived section of the community.

Content in this area has been identified as outdated or irrelevant.

This change was done in an effort to make the forum easier to use and to keep only the most helpful and recent content active.

Post your questions in the Xfinity Community

New Poster

Payment website has some serious problems

First, the auto-pay didn't work. Then I tried to submit the payment manually and nothing happened. Looking at the console I see the following:

 

Failed to load resource: the server responded with a status of 400 ()
components.ce480a32.js:2 TypeError: Cannot read property 'setAttribute' of null
at Object.d.scrollToSelector (https://customer.xfinity.com/assets/js/main.92b84573.js:5:17108)
at https://customer.xfinity.com/assets/js/main.92b84573.js:9:27939
at https://customer.xfinity.com/assets/js/components.ce480a32.js:3:14264
at i (https://customer.xfinity.com/assets/js/components.ce480a32.js:1:22195)
at https://customer.xfinity.com/assets/js/components.ce480a32.js:1:23646
at c (https://customer.xfinity.com/:24:16409) undefined
(anonymous) @ components.ce480a32.js:2
customer.xfinity.com/:24 POST https://customer.xfinity.com/apis/payments/one-time 400 ()
c @ customer.xfinity.com/:24
n.send @ components.ce480a32.js:22
(anonymous) @ components.ce480a32.js:2
v @ components.ce480a32.js:2
c @ components.ce480a32.js:2
u @ components.ce480a32.js:2
(anonymous) @ components.ce480a32.js:2
$eval @ components.ce480a32.js:3
$digest @ components.ce480a32.js:3
$apply @ components.ce480a32.js:3
(anonymous) @ components.ce480a32.js:5
We @ components.ce480a32.js:1
n @ components.ce480a32.js:1
c @ customer.xfinity.com/:24
components.ce480a32.js:2 TypeError: Cannot read property 'setAttribute' of null
at Object.d.scrollToSelector (https://customer.xfinity.com/assets/js/main.92b84573.js:5:17108)
at https://customer.xfinity.com/assets/js/main.92b84573.js:9:27939
at https://customer.xfinity.com/assets/js/components.ce480a32.js:3:14264
at i (https://customer.xfinity.com/assets/js/components.ce480a32.js:1:22195)
at https://customer.xfinity.com/assets/js/components.ce480a32.js:1:23646
at c (https://customer.xfinity.com/:24:16409) undefined
(anonymous) @ components.ce480a32.js:2
(anonymous) @ components.ce480a32.js:2
(anonymous) @ main.92b84573.js:1
(anonymous) @ components.ce480a32.js:3
i @ components.ce480a32.js:1
(anonymous) @ components.ce480a32.js:1
c @ customer.xfinity.com/:24
setTimeout (async)
c @ customer.xfinity.com/:24
f.defer @ components.ce480a32.js:1
a @ components.ce480a32.js:3
I.rejectSubmitPayment @ main.92b84573.js:9
u @ components.ce480a32.js:2
(anonymous) @ components.ce480a32.js:2
$eval @ components.ce480a32.js:3
$digest @ components.ce480a32.js:3
$apply @ components.ce480a32.js:3
a @ components.ce480a32.js:2
m @ components.ce480a32.js:2
w.onload @ components.ce480a32.js:2
c @ customer.xfinity.com/:24
load (async)
f @ customer.xfinity.com/:24
o @ customer.xfinity.com/:24
c @ customer.xfinity.com/:24
XMLHttpRequest.send (async)
c @ customer.xfinity.com/:24
n.send @ components.ce480a32.js:22
(anonymous) @ components.ce480a32.js:2
v @ components.ce480a32.js:2
c @ components.ce480a32.js:2
u @ components.ce480a32.js:2
(anonymous) @ components.ce480a32.js:2
$eval @ components.ce480a32.js:3
$digest @ components.ce480a32.js:3
$apply @ components.ce480a32.js:3
(anonymous) @ components.ce480a32.js:5
We @ components.ce480a32.js:1
n @ components.ce480a32.js:1
c @ customer.xfinity.com/:24

 

This happens in both Chrome and Edge. This is some seriously sloppy programming when an API call fails to even return why it failed and it just frustrates customers like myself. Now that I've looked in the console for you, please fix it.

Admin1

Re: Payment website has some serious problems

Hi johnsmith9 -- Thank you for sharing this experience. We have not received any reported issues with making payments via our web portal. Aside from using multiple browsers, as you've already done, you should also try clearing your cache & cookies from each browser to see if that resolves this issue for you. 


I am an Official Comcast Employee.
Official Employees are from multiple teams within Comcast: CARE, Product, Leadership. We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!