# Having a "Payment Error" pop up before I get to a payment page

**URL:** <https://community.feathery.io/t/having-a-payment-error-pop-up-before-i-get-to-a-payment-page/667>\
**Category:** Support\
**Created:** [April 30, 2024, 6:35pm UTC](https://community.feathery.io/t/having-a-payment-error-pop-up-before-i-get-to-a-payment-page/667 "2024-04-30T18:35:00Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![mbrennan](https://avatars.discourse-cdn.com/v4/letter/m/96bed5/32.png) [@mbrennan](https://community.feathery.io/u/mbrennan)\
**Post date:** [April 30, 2024, 6:35pm UTC](https://community.feathery.io/t/having-a-payment-error-pop-up-before-i-get-to-a-payment-page/667/1 "2024-04-30T18:35:00Z")

</div>

I have put together a form that upon completion is being built to take me to a Stripe powered payment page.

Upon filling out the required fields on the form and clicking “Go to Payment” which should take me to the area to enter payment information, I am being met with an error message.

 ![Screenshot 2024-04-30 at 1.20.18 PM](https://canada1.discourse-cdn.com/flex030/uploads/feathery/original/1X/c4a6974e8f0cf9c49e1288180b46d2a1db6b7dc6.png)

Looking at the Inspect pages to see what is happening behind the scenes, I see the call for:

Request URL: https//api.feathery.io/api/stripe/checkout/  
Request Method: POST  
Status Code: 404 Not Found  
Remote Address: 52.53.84.134.443  
Referrer Poilcy: strict-origin-when-cross-origin

And the response error saying:

[{“message”:“Not found.”,“code”:“default-error”}]

Has anybody experienced this before? Any ideas what is going wrong?

---

<div class="post-metadata">

**Author:** ![peter](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.feathery.io/peter/32/7_2.png) [@peter](https://community.feathery.io/u/peter)\
**Post date:** [May 1, 2024, 6:53am UTC](https://community.feathery.io/t/having-a-payment-error-pop-up-before-i-get-to-a-payment-page/667/2 "2024-05-01T06:53:31Z")

</div>

you shoudl clear out the customer lookup field in your integrations etup. the stripe ID is an identiifer unique to stripe so the email will never correspond to it

---

<div class="post-metadata">

**Author:** ![cmcgoodwin](https://avatars.discourse-cdn.com/v4/letter/c/e480ec/32.png) [@cmcgoodwin](https://community.feathery.io/u/cmcgoodwin)\
**Post date:** [May 1, 2024, 1:40pm UTC](https://community.feathery.io/t/having-a-payment-error-pop-up-before-i-get-to-a-payment-page/667/3 "2024-05-01T13:40:52Z")

</div>

Hey Peter – we tried this and are still getting the error.

We’ve done the following:

- disconnected the Stripe connection and re-established it with new secret keys
- cleared out the customer lookup field
- tried creating a new Product in Stripe from Feathery (this worked so the connection between Feathery and Stripe is good).
- tried checking out with the new product we created (still getting the same error).

This is an odd error because it just started happening yesterday. Everything had been working fine until then.

Any assistance would be greatly appreciated, we are planning to go live with the form next week.

---

<div class="post-metadata">

**Author:** ![peter](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.feathery.io/peter/32/7_2.png) [@peter](https://community.feathery.io/u/peter)\
**Post date:** [May 2, 2024, 7:15am UTC](https://community.feathery.io/t/having-a-payment-error-pop-up-before-i-get-to-a-payment-page/667/4 "2024-05-02T07:15:48Z")

</div>

Including @jay here to take a look at this issue

---

<div class="post-metadata">

**Author:** ![peter](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.feathery.io/peter/32/7_2.png) [@peter](https://community.feathery.io/u/peter)\
**Post date:** [May 3, 2024, 5:09am UTC](https://community.feathery.io/t/having-a-payment-error-pop-up-before-i-get-to-a-payment-page/667/5 "2024-05-03T05:09:13Z")

</div>

should be resolved in half an hour or so

---

<div class="post-metadata">

**Author:** ![mbrennan](https://avatars.discourse-cdn.com/v4/letter/m/96bed5/32.png) [@mbrennan](https://community.feathery.io/u/mbrennan)\
**Post date:** [May 6, 2024, 3:16pm UTC](https://community.feathery.io/t/having-a-payment-error-pop-up-before-i-get-to-a-payment-page/667/6 "2024-05-06T15:16:07Z")

</div>

@peter Thanks for taking care of this issue. Can you give us some insight into what the root of the problem was and how it was addressed please?

---

<div class="post-metadata">

**Author:** ![peter](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.feathery.io/peter/32/7_2.png) [@peter](https://community.feathery.io/u/peter)\
**Post date:** [May 6, 2024, 3:32pm UTC](https://community.feathery.io/t/having-a-payment-error-pop-up-before-i-get-to-a-payment-page/667/7 "2024-05-06T15:32:59Z")

</div>

there was an internal refactor that triggered this bug, which we fixed

---

<div class="post-metadata">

**Author:** ![mbrennan](https://avatars.discourse-cdn.com/v4/letter/m/96bed5/32.png) [@mbrennan](https://community.feathery.io/u/mbrennan)\
**Post date:** [May 6, 2024, 3:55pm UTC](https://community.feathery.io/t/having-a-payment-error-pop-up-before-i-get-to-a-payment-page/667/8 "2024-05-06T15:55:05Z")

</div>

@peter Ok, is there risk of this being a continuing issue? We are evaluating this as a process that is business critical and want to make sure we understand the potential issues that may arise and how to address them.

---

<div class="post-metadata">

**Author:** ![peter](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.feathery.io/peter/32/7_2.png) [@peter](https://community.feathery.io/u/peter)\
**Post date:** [May 6, 2024, 3:56pm UTC](https://community.feathery.io/t/having-a-payment-error-pop-up-before-i-get-to-a-payment-page/667/9 "2024-05-06T15:56:12Z")

</div>

this was one-off from the refactor to allow embedding forms via form ID.
