Store 6 runs only on ExpressionEngine 7. A minimum of PHP 8.1 is required.
The templating for the publishable key should now no longer be hardcoded like Store 5 had.
Instead, you should first visit your Stripe settings in the Payment Gateway settings and set your Stripe publishable key here. Next,
{exp:store:settings setting="stripe_publishable_key"} should be used for the templating side of things instead of hardcoding your publishable key. Please see the example templates for full example usage on this, specifically, store_example/checkout3 shows how to use this tag to get the publishable key from your Stripe settings.
New in Store 6: You can use the {exp:store:stripe_js} tag to automatically load the Stripe JS library and output your publishable key to the page. The publishable_api_key parameter is now optional—if not provided, Store will use the key from your Stripe payment method settings if available. This makes it easier to keep your templates secure and up to date.
Important: If you are upgrading an existing site from an older version, you must ensure your Stripe integration is using Stripe.js V3. Store 6 requires Stripe.js V3 for all Stripe payment processing. Update your templates and any custom code to use the new Stripe Elements and Payment Intents API as shown in the example templates and documentation.
Major changes are now in place for these. Your settings must change to keep these working. Update to the new versions of the shipping and follow the documentation guide for setting them up located here:
In previous Store Versions, Order Fields were relying on Legacy Member Templates. If you used this in prior Store versions, you likely have $config['legacy_member_templates'] = 'y'; in your config file. This legacy setting is no longer needed for this flow. To update - you may turn that setting off. Then, map your new member fields to the order fields as shown above and save the settings page. Finally, you will switch to using the new templating described above and an example of that can also be found in the store template examples. The example specifically outlines order_custom9 but you will extend this to all of your specific order fields that are in use for your site.
For even more detail on how to set this up, please visit the Order Fields documentation.