Payment Sheets & Manually Confirmed Intents
See original GitHub issueHello! Thanks for the library! Apologies for opening an issue for a question - I would be happy to open a discussion instead but they are not enabled for the repo.
I am finally performing a migration to this lib from tipsi and I am taking advantage of the beautiful payment sheet integration.
I am however hitting a couple roadblocks with what I used to have and what I now have to have.
My previous flow was:
- User views checkout page
- User selects payment method (card/native)
- A payment method or payment method token is created
- User’s order is sent to server where a manual intent is created with appropriate fees etc
- Server attempts to confirm/charge the intent, and tells the app if further (SCA) auth is required
- If approved/not required then another request to the server is made to confirm the intent again
- The user’s order is considered “paid” at this point and out-of-scope things happen
Now with the payment sheets setup I am unable to replicate this behaviour and appear to have to rely on webhooks - but I’d like to keep the old behaviour if at all possible (if it ain’t broke, don’t fix it) as this means I can guarantee payment will be taken at the time of purchase and not have to handle sending events from the server back to the app to sync states.
After many hours of combing through code/documentation (some props do not match e.g. presentPaymentSheet does not say that it needs clientSecret
second code block L5) I found this PR https://github.com/stripe/stripe-react-native/pull/514 (which, to confuse matters more, removes clientSecret
from presentPaymentSheet
in the examples).
514 suggests that customFlow
must be used if one needs to manually confirm intents - however I cannot figure for the life of me how this can be done whilst retaining the UI journey from a customFlow: false
option. The confirmPayment
option would appear to do what I need!
I hope this makes sense and please ask if you need some code examples.
Issue Analytics
- State:
- Created 2 years ago
- Comments:11 (1 by maintainers)
Got it, I think if you (or someone else) is trying to do this in the future, they should follow this comment here, but lmk if you have issues or questions!
Hey @charliecruzan-stripe unfortunately the project ended up dying, and it was so long ago I find it hard to remember exactly what I did. I’m pretty sure it never went anywhere since my previous comment.
The ability to do this would be greatly beneficial still though. I appreciate you checking in on this!