Replies: 2 comments 2 replies
-
looking at the clientSecret carefully, it looks like two parts concatenated together. seti_1QTdC2KKI1hVOxLkYg328iJV_secret_RMLtEVrhFMpLubyXLZgTa2zy6LMT7QY I am putting the clientSecret and the customerId into a java POJO object to send back via springboot.
|
Beta Was this translation helpful? Give feedback.
0 replies
-
Make sure that you use the clientsecret that you get from the backend for your setupintent. Do not use the stripe publishablekey for it |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Describe the bug
I have my java springboot server create the "create-setup-intent" and returns the clientSecret and customerId.
Here is a snippet of the logs:
I/flutter (19491): url :: http://MyserverIP:8080/payment/create-setup-intent ::
I/flutter (19491): value :: {clientSecret: seti_1QTdC2KKI1hVOxLkYg328iJV_secret_RMLtEVrhFMpLubyXLZgTa2zy6LMT7QY, customerId: cus_RMLtOk04Iyv2Ef}
When the flutter app get this, i was temporarily able to display the payment bottom sheet for a few times.
But now it stopped.
This is now the error that I see as a toast message.
I was using the code from the example "add_payment_method_button.dart" and the related files.
Since my flutter app is using BLOC, I fetch the clientSecret and customerId from the server and pass those two strings into AddPaymentMethodScreenLoader
Here is the mobile version
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I expect the payment method entry bottom sheet to appear consistently. Now it fails about 99% of the time.
Smartphone / tablet
Additional context
Add any other context about the problem here.
Beta Was this translation helpful? Give feedback.
All reactions