How to fix multi-step form data not updating after Stripe Checkout in a signup flow? Answered
Hey there, my question is about multi-step form fields.
Right now, the current flow looks like the following:
Sign up -> Stripe Checkout -> add account details -> add account preferences
Unfortunately, although all data-attributes are set correctly, the two pages account details as well as account-preferences doesn't update any data related to the newly created customer.
Is it because of the stripe-checkout or can this have other reasons?
Comments
6 comments
Hi Sebastian,
Sorry to hear you're facing this issue.
It sounds like the problem may be due to the form attribute not being set to
data-ms-form="profile", or possibly other data attributes not being properly configured with the correct custom field IDs. If you're using our DOM APIs and the setup isn't fully aligned, that could also lead to the issue you're experiencing.I recommend double-checking that all necessary data attributes are correctly applied on both the account details and account preferences pages. These attributes are essential for Memberstack to know which data to update. If you'd like, feel free to share the link to your website, and I can take a look to ensure everything is set up properly, or identify any other potential causes for the issue.
🎯 Hey there, I've got a question regarding multi-step sign in forms.. I've splitted it into the following 'flow':
register -> information -> preferences -> Dashboard
Unfortunately, the additional steps (information & preferences) haven't any functionality. What I mean with that is that those steps aren't updating any data in memberstack, although I gave each form field the corresponding data-attribute. How can I fix this issue?
By mentioning data-attribute, I mean I have passed
data-ms-member="CUSTOM_FIELD_ID"for all the custom fields accordingly and also have updated the form attribute to bedata-ms-form="profile"?You can find the read-only-link here. You'll find the register-pages under pages -> registerLooking forward hearing from you!
I had a quick look and found that the highlighted attribute should have the value "profile" and not "login".
I can see the block_form element (the one above the highlighted element) has the profile attribute, but you can remove it from there, as the attribute must be placed in the highlighted place in the screenshot.
Can you make the changes on both details and preferences page forms and publish it? Test the form and let me know if you still face issues
Awesome! Now it works! Thank you very much A J! Just one question. Why does the attribute has to be on the wrapper inside the form-element and not on itself?
Great, welcome 😇
Actually the highlighted part is the form element and the block_form is gonna act as a wrapper on the front-end.
From what you’ve described, the issue usually isn’t Stripe itself — Stripe Checkout just handles payment and doesn’t interfere with Memberstack’s profile updates. The more common cause is that the form attributes aren’t set correctly for profile updates. For multi-step flows like yours, you’ll want to make sure each form on the account details and account preferences pages has the attribute
data-ms-form="profile"and that each input is mapped with the properdata-ms-member="CUSTOM_FIELD_ID". Without that, Memberstack doesn’t know to update the customer record.This is where Script #197 – Multi-step Form Submission Handling can help. It ensures that each step validates, saves, and progresses correctly, so you don’t lose data after checkout. By combining #197 with the correct
profileform attributes, you can reliably capture account details and preferences after Stripe Checkout.Please sign in to leave a comment.