akdj16

[gilded cobalt]

HI there 👋 can you share the ID of the request that returned the error you provided?

As you mentioned you're working to Setup Intents, SEPA, and React Native, is this the guide that you're following for the flow that you're building?
https://stripe.com/docs/payments/sepa-debit/set-up-payment?platform=react-native

[celest crest]

Thank you! Let me try 🙂

about the request ID, it is: req_UhQv464ATyTUlh

[gilded cobalt]

Thank you! That request seems to map to the request to create a Setup Intent, which completed successfully and did not error. I found the request that raised the error you referenced:
https://dashboard.stripe.com/test/logs/req_8imZg2PHKvMett

It looks like that error was encountered because you directly created the SEPA payment method by making a server-side request to create it:
https://dashboard.stripe.com/test/logs/req_B9YGURfFE6QdTf

Since the Payment Method was created without customer input, no Mandate was created for it. If you're working on building a new flow, then I would suggest leveraging the guide above as that approach should avoid the error you encountered.

[celest crest]

I checked our project code, in fact, we did the same steps of the documentation above, but we had added a createPaymentMethod between the createSetupIntent and confirmSetupIntent calls, because we used the pm id of createPaymentMethod in the confirmSetupIntent call and it thrown error

by removing the createPaymentMethod, it reworks fine

[gilded cobalt]

Yeah, creating the Payment Method directly from your end means we don't have a chance to collect mandate acceptance from your customer, so instead you would need to provide the details of the customer's mandate acceptance. When you don't provide a specific Payment Method to use, the confirmSetupIntent request will create a new Payment Method and log the associated mandate acceptance.

[celest crest]

ok! I see

Thanks again

[gilded cobalt]

Any time! Best of luck with the rest of your project!

[celest crest]

Thanks!