#vladtm23
1 messages · Page 1 of 1 (latest)
Can you share the value of the clientSecret or the PaymentIntent ID?
Sure, just give me a second to create a new payment intent. Will get back with both of those.
The existing one should work
https://support.stripe.com/questions/finding-the-id-for-an-api-request
Client token: eyJjbGllbnRfc2VjcmV0IjoicGlfM09YMzVPQWcySmhFeTh2WTBVandNSGo1X3NlY3JldF9MWWQxd29lejQ5cTNETXdFNUIxcnJFcm5wIiwicHVibGlzaGFibGVfa2V5IjoicGtfdGVzdF9EQUJLY0E2Vzh6OTc0cTdPSWY0YmJ2MVQwMEpwRmMyOUpWIn0=
Client secret: pi_3OX35OAg2JhEy8vY0UjwMHj5_secret_LYd1woez49q3DMwE5B1rrErnp
Typically when you see "No such payment_intent found error, it means the API keys are mismatched
like PaymentIntent was created using account A's Private API key but your client-side code uses Account B's Public API key
I've found a similar answer on SO and raised that with the BE team, but they said that they are only making a call towards the Duffel endpoint, with the Duffel API key, no Stripe key.
So potentially when Duffel is creating the payment intent on their end, they are using a different publishableKey?
If Duffel uses their own key for PaymentIntent creation then you'd need to use their Publishable API key in your mobile app.
They shared those here: https://duffel.notion.site/Duffel-Payments-React-Native-Guide-a7369b594bc241d2ade7ba5946fd935e, but those aren't working. So they either changed or something else is not working properly in this flow.
In my code, the AppConstants.publishableDevKey part is equal to the "test" key mentioned in their article.
Since its an integration through a third-party, you'd need to work with them to resolve this unfortunately. Nobody on our team would know anything about duffel integration pattern.
Sure, no worries and really appreciate the help. Was thinking that maybe I was doing something wrong with the StripeSDK integration or did not set enough keys.
Thank you very much! Already trying to reach out to them to get this sorted out, thanks @ruby birch , and have a great day. 😄