#r0ckii.

1 messages · Page 1 of 1 (latest)

faint oakBOT
#

Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

solar gyro
#

Hello! We don't reopen closed threads, can you summarize the context and provide your new question here?

tulip tulip
#

In short, CC information is not being passed when a user is checking out even though the payment info has been captured. It fills their email, name and country but not their credit card. This is the issue we're having

For context, we have two flows when users are onboarding

  1. THe first flow (Application Flow) users are applying to be members of our community. They fill out a form and at the end of the form, we are using elements to capture their payment information and a user is successfully created in our Stripe Dashboard. We use the 'client_secret' present on 'setupIntent' to access the elements form on the FE
 (first image). This is how the Elements form submits the cc info
 (second image), and this generates the checkout session for the subscription. We use the external_url present on session (last image)
#
  1. The second flow (Registration Flow) is when an applicant has been approved and can formally register. During this flow we use a hosted payment form. But when the user gets to this page, their CC info is missing and is not being auto-filled
#

We meet all the conditions that should be auto-filling the card stated in the docs

solar gyro
#

To clarify, you're using a Setup Intent with the Payment Element first, then sending them to a Checkout Session where you expect the Payment Method set up with the Setup Intent to show up?

tulip tulip
#

that's correct