Amex "Payments" tab buggy?

[wasCB14]

Have others been having problems with the Amex website, specifically the pay-from bank account info?

I want to close a checking account, and I've tried 4 times in the last week to delete it from the Amex website so it won't be my default autopay account. I keep encountering some bug or another every time.

[MrDisco99]

I occasionally have to pay through my phone app because the website doesn’t work. They still have some work to do.

[McNugget]

The site has been buggy for me in general for the past couple days.

[wasCB14]

I was able to delete the soon-to-be-closed checking account via the Amex app.

[ChargedUp]

I was having some issues with Amex and Discovers sites, but found out that my browsers privacy/ad blocker was the culprit.

[Anonymous]

Last month when paying all Amex Cards my payments timed out on the website ( using Safari ).  I picked up my phone paid all cards without an issue via the app.  

I tend to pay via app half the time anyway, but there's been various of website design layout changes lately with mixed impressions.

[FinStar]

---

@wasCB14 wrote:

I was able to delete the soon-to-be-closed checking account via the Amex app.

---

I was gonna say, when you experience any issues online, use the app.  Then again, you could always try different browsers since some features will work on some but not the others.

[wasCB14]

---

@FinStar wrote:

---

@wasCB14 wrote:

I was able to delete the soon-to-be-closed checking account via the Amex app.

---

I was gonna say, when you experience any issues online, use the app.  Then again, you could always try different browsers since some features will work on some but not the others.

---

Same problem with my Citi credit cards, same solution.

[staticvoidmain]

A lot of functions in some bank sites (Amex and Capital one comes to mine) will be blocked if you have an installed ad-blocker (e.g. uBlock),  and/or tracker blocker (e.g. Ghostery). You have to trust the site/s, and it should function just fine. You can check exactly what's happening with the dev console (f12 on Chrome).