@spree/docs 0.1.0

package/dist/developer/upgrades/5.3-to-5.4.md

@@ -0,0 +1,248 @@
+---
+title: Upgrading to Spree 5.4
+description: This guide covers upgrading a Spree 5.3 application to Spree 5.4.
+---
+
+> **INFO:** Before proceeding to upgrade, please ensure you're at [Spree 5.3](/developer/upgrades/5.2-to-5.3)
+
+## Upgrade steps
+
+### Remove `spree_sample` gem from your Gemfile
+
+Samples are now included in the `spree` gem. If you've added previously `spree_sample` to your Gemfile, remove it by running:
+
+  ```bash
+  bundle remove spree_sample
+  ```
+
+### Update gems
+
+  ```bash
+  bundle update
+  ```
+
+### Fetch and run missing migrations
+
+  ```bash
+  bin/rake spree:install:migrations && bin/rails db:migrate
+  ```
+
+### Backfill Image Thumbnail IDs
+
+Spree 5.4 adds a `thumbnail` association to both `Product` and `Variant` models. This greatly speeds up rendering Product lists everywhere (API, Admin Dashboard and `spree_storefront`), as previously we've had to load all images for each product.
+
+This can be done by running the following command:
+
+  ```bash
+  bin/rails spree:images:backfill_thumbnails
+  ```
+
+As above, this process can take a while depending on the size of your product catalog.
+
+### Prefixed IDs
+
+Spree 5.4 by default uses prefixed IDs for resources (eg. `prod_6VsgxZbenF`) instead of just IDs from the database. These IDs are now used in Admin Dashboard, API v3, Events system and Webhooks.
+
+#### Event Subscribers
+
+If you previously added Subscribers for Events, eg. `order.completed` with code such as:
+
+```ruby
+module MyApp
+  class OrderAuditSubscriber < Spree::Subscriber
+    subscribes_to 'order.complete'
+
+    on 'order.complete', :log_order_completed
+
+    private
+
+    def find_order(event)
+      Spree::Order.find(event.payload[:id])
+    end
+  end
+end
+```
+
+You will need to update your code to use the new prefixed IDs, from:
+
+```ruby
+Spree::Order.find(event.payload[:id])
+```
+
+to:
+
+```ruby
+Spree::Order.find_by_prefix_id!(event.payload[:id])
+```
+
+You can also use `find_by_prefix_id` without the bang (`!`) to gracefully handle cases where the record might not exist.
+
+#### Adding Prefixed IDs support to your custom models
+
+All models inheriting from `Spree::Base` (or `Spree.base_class`) can support Prefixed IDs by adding the following code to your model:
+
+```ruby
+class MyModel < Spree::Base
+  has_prefix_id :mm
+  
+  # ...
+end
+```
+
+Prefix length isn't limited by default, but we recommend to keep it short.
+
+### Migrate Checkout Zones to Markets
+
+Spree 5.4 introduces [Markets](/developer/core-concepts/markets) as the primary way to manage which countries are available for checkout, along with their currencies and locales. The legacy `checkout_zone` field on the Store model is now deprecated and will be removed in Spree 5.5.
+
+New stores automatically get a default market created from their `default_country` — no manual setup needed. For existing stores that used `checkout_zone`, run the migration rake task:
+
+  ```bash
+  bin/rake spree:markets:migrate_checkout_zones
+  ```
+
+This will:
+1. Read the `checkout_zone` countries from each store
+2. Create a default Market with those countries, currency, and locale
+3. Clear the `checkout_zone_id` column
+
+> **WARNING:** You will need to run this rake task locally and on your production environment. After running, verify your markets are set up correctly in the Admin Dashboard under **Settings → Markets**.
+
+#### Deprecated Store methods
+
+The following Store methods now emit deprecation warnings and will be removed in Spree 5.5:
+
+| Deprecated method | Replacement |
+|---|---|
+| `store.checkout_zone` | Use [Markets](/developer/core-concepts/markets) to manage countries |
+| `store.checkout_zone=` | Use [Markets](/developer/core-concepts/markets) to manage countries |
+
+The `store.default_country` reader now returns the first country (by name) from the store's default market. The `store.default_country_iso=` setter still works and is used to set the country when creating a store — a default market is automatically created from it.
+
+#### Code that references `checkout_zone` for tax
+
+If your application used `store.checkout_zone` as a tax zone fallback, update it to use `Spree::Zone.default_tax` instead:
+
+```ruby
+# Before
+zone = current_store.checkout_zone
+
+# After
+zone = Spree::Zone.default_tax
+```
+
+### ActiveMerchant removed from Spree Core
+
+Spree 5.4 no longer depends on the `activemerchant` gem. All internal usages have been replaced with lightweight Spree-native classes:
+
+| ActiveMerchant class | Spree replacement |
+|---|---|
+| `ActiveMerchant::Billing::Response` | `Spree::PaymentResponse` |
+| `ActiveMerchant::ConnectionError` | `Spree::PaymentConnectionError` |
+
+`Spree::PaymentResponse` is a drop-in replacement with the same constructor signature:
+
+```ruby
+Spree::PaymentResponse.new(success, message, params = {}, options = {})
+```
+
+It supports the same methods: `success?`, `message`, `params`, `authorization`, `avs_result`, `cvv_result`, `test?`, and YAML serialization (for log entries).
+
+#### Updating custom payment methods
+
+If you have a custom payment method (gateway) that returns `ActiveMerchant::Billing::Response`, update it to return `Spree::PaymentResponse` instead:
+
+```ruby
+# Before
+def authorize(money, source, options = {})
+  # ...
+  ActiveMerchant::Billing::Response.new(true, 'Success', {},
+    authorization: transaction_id, test: test?)
+end
+
+# After
+def authorize(money, source, options = {})
+  # ...
+  Spree::PaymentResponse.new(true, 'Success', {},
+    authorization: transaction_id, test: test?)
+end
+```
+
+If your gateway rescues `ActiveMerchant::ConnectionError`, update it to rescue `Spree::PaymentConnectionError`:
+
+```ruby
+# Before
+rescue ActiveMerchant::ConnectionError => e
+
+# After
+rescue Spree::PaymentConnectionError => e
+```
+
+#### Using `spree_gateway` or other ActiveMerchant-based extensions
+
+If you use the [`spree_gateway`](https://github.com/spree/spree_gateway) gem or another extension that depends on ActiveMerchant, add `activemerchant` directly to your application's `Gemfile`:
+
+```ruby
+gem 'activemerchant'
+```
+
+These extensions will continue to work — Spree's `LogEntry#parsed_details` still deserializes `ActiveMerchant::Billing::Response` objects when the gem is present.
+
+#### Address hash method renamed
+
+`Spree::Address#active_merchant_hash` has been renamed to `#gateway_hash`. A backwards-compatible alias is provided, so existing code continues to work without changes.
+
+### (Optional) Install API v2
+
+Spree 5.4 ships with API v3, which marks deprecation of API v2. API v2 is still available but you need to install it separately. If you currently use API v2, you can do this by running the following command:
+
+  ```bash
+  bundle add spree_legacy_api_v2
+  ```
+  
+If you have tests for API v2 endpoints in your application, you will need to include some files in your `rails_helper.rb`:
+
+  ```ruby
+  require 'jsonapi/rspec'
+  require 'spree_legacy_api_v2/testing_support/v2/base'
+  require 'spree_legacy_api_v2/testing_support/factories'
+  require 'spree_legacy_api_v2/testing_support/v2/current_order'
+  require 'spree_legacy_api_v2/testing_support/v2/platform_contexts'
+  require 'spree_legacy_api_v2/testing_support/v2/serializers_params'
+  
+  RSpec.configure do |config|
+    config.include JSONAPI::RSpec, type: :request # required for API v2 request specs
+  end
+  ```
+
+Also, add `jsonapi-rspec` gem to your `Gemfile`:
+
+  ```ruby
+  gem 'jsonapi-rspec', group: :test
+  ```
+  
+And run `bundle install`
+
+### (Optional) Install Spree Multi Store
+
+Multi-store features like multiple store management & custom domains were moved to a separate gem `spree_multi_store`.
+
+If you rely on these features please run:
+
+  ```bash
+  bundle add spree_multi_store
+  ```
+
+### (Optional) Install Legacy Product Properties
+
+Product Properties have been extracted from Spree core to a separate gem `spree_legacy_product_properties`. Product Properties were already deprecated in favor of [Metafields](/developer/core-concepts/metafields) and disabled by default since Spree 5.1.
+
+If you have `product_properties_enabled: true` in your Spree configuration or rely on Product Properties in any way, install the extension:
+
+  ```bash
+  bundle add spree_legacy_product_properties
+  ```
+
+No data migration is needed — the gem uses the same database tables. All existing product properties, property definitions, and associations will continue to work as before.
+
+> **WARNING:** If you skip this step and had Product Properties enabled, any code referencing `product.product_properties`, `product.property()`, `product.set_property()`, or the admin Properties page will stop working.

package/dist/developer/upgrades/quickstart.md

@@ -0,0 +1,36 @@
+---
+title: Quickstart
+description: Learn how to upgrade your Spree application
+---
+
+Keeping your Spree installation up-to-date is essential to keep it safe and secure. Each Spree version brings new features, enhancements and bug fixes so it's greatly beneficial for you and your clients to upgrade frequently.
+
+The upgrade process is fairly easy and well described. Of course, it all boils down to the level of customizations and the way you've customized your Spree applications.
+
+We strongly advise upgrading Spree incrementally, rather than in one big go.
+
+## Support
+
+If you're stuck and would want to get some professional help, you can [contact us directly](https://spreecommerce.org/contact/) and request a quote for our consulting services.
+
+## Release types
+
+Spree development follows a shifted version of [Semantic Versioning](https://semver.org/):
+
+**Patch Z, eg. 4.2.1**
+
+Only bug fixes, no API changes, no new features. Except as necessary for security fixes.
+
+**Minor Y, eg. 4.2.0**
+
+New features, may contain API changes Serve as major versions of Semver. Breaking changes are paired with deprecation notices in the previous minor or major release.
+
+**Major X, eg. 4.0.0**
+
+New features, will likely contain API changes. The difference between Spree minor and major releases is the magnitude of breaking changes and is usually reserved for special occasions.
+
+## Security
+
+Our Security policy is [described here](/developer/security).
+
+When a release series is no longer supported, it's your own responsibility to deal with bugs and security issues. We may provide backports of some critical security fixes.

package/dist/integrations/analytics/google-analytics.md

@@ -0,0 +1,64 @@
+---
+title: "Connect Google Analytics 4 to Spree Commerce"
+sidebarTitle: Google Analytics 4
+description: "Learn how to set up and manage Spree’s native Google Analytics 4 integration."
+---
+
+Spree Commerce comes with a native Google Analytics 4 integration that allows you to track user behavior, sales performance, and marketing effectiveness across your store. 
+
+With minimal setup required, you can gain valuable insights into how visitors interact with your site, which can help you make informed decisions to improve conversions, user experience, and overall business strategy.
+
+> **WARNING:** To set up the Google Analytics integration, you must have a Google Analytics account and an associated property.
+
+## Installation
+
+Before you can enable Google Analytics 4, it must be installed. To do so, you need to run the following command:
+
+```bash
+bundle add spree_google_analytics && bundle exec rails g spree_google_analytics:install
+```
+
+After that, make sure to restart your server if it was running.
+
+## Connect Google Analytics
+
+Sign in to your Spree admin dashboard and navigate to the **Integrations** tab.
+
+![](/images/integrations/google-analytics/1.get_started.png)
+
+Locate the Google Analytics tile under Analytics, and click **Connect Google Analytics**.
+
+This will redirect you to the setup page for Google Analytics integration.
+
+![](/images/integrations/google-analytics/2.setup_form.png)
+
+Simply enter the **Measurement ID** from your Google Analytics account into the field and click **Create** to finalize the integration.
+
+> **NOTE:** You can find the **Measurement ID** in the Home screen of your Google Analytics dashboard, if no data has been collected yet. Otherwise, it can be found by navigating to Admin settings \> Data Streams and then clicking on the property associated with your Spree site.
+
+![](/images/integrations/google-analytics/3.integration_added.png)
+
+## Event Tracking
+
+By default, the following events will be tracked in Google Analytics:
+
+- page_view
+- first_visit
+- session_start
+- user_engagement
+- search
+- add_payment_info
+- add_shipping_info
+- add_to_cart
+- add_to_wishlist
+- begin_checkout
+- purchase
+- remove_from_cart
+- view_cart
+- view_item
+
+## Manage Your Integration
+
+If you’d like to remove Google Analytics from your site, simply revisit the integration’s setup form and click **Delete** on the lower right hand side.
+
+You can also switch out the Measurement ID if you’d like to switch the Google Analytics property that your site is connected to.

package/dist/integrations/analytics/google-tag-manager.md

@@ -0,0 +1,78 @@
+---
+title: "Connect Google Tag Manager to Spree Commerce"
+sidebarTitle: Google Tag Manager
+description: "Learn how to set up and manage Spree’s native Google Tag Manager integration."
+---
+
+Google Tag Manager is a flexible tag management tool that lets you deploy and manage analytics, SEO, and marketing scripts across your store without editing code. You can connect services like Google Analytics 4, Google Ads, Meta Pixel, Microsoft Clarity, LinkedIn Insights, and Hotjar from one central workspace.
+
+Spree makes it easy to connect your store to GTM and uses its ecommerce dataLayer to automatically push rich event data to your GTM container - no custom code required.
+
+> **WARNING:** This integration allows you to use either Google Tag Manager or Google Analytics 4 - but not both at the same time. Only one key (GTM or GA4) should be active in the integration settings. If you plan to use GA4 with GTM, you must set up GA4 inside of your GTM workspace manually.
+
+## Requirements
+
+To use this integration, you’ll need:
+
+- An active Google Tag Manager account
+- A GTM container set up for your store
+- Any additional tools (e.g., Google Analytics 4, conversion tracking, custom tags) configured within GTM
+
+Spree will automatically push ecommerce events to the dataLayer, but it’s up to you to configure tags and triggers in your GTM workspace.
+
+## Installation
+
+Before you can enable Google Tag Manager, it must be installed. To do so, you need to run the following command:
+
+```bash
+bundle add spree_google_analytics && bundle exec rails g spree_google_analytics:install
+```
+
+After that, make sure to restart your server if it was running.
+
+## Connect Google Tag Manager
+
+Sign in to your Spree admin dashboard and navigate to the Integrations tab.
+
+![](/images/integrations/google-tag-manager/1.integrations_tab.png)
+
+Locate the Google Analytics tile under Analytics and click **Connect Google Analytics.**
+
+This will redirect you to the setup page for Google Tag Manager integration.
+
+![](/images/integrations/google-tag-manager/2.gtm_form.png)
+
+Select **Google Tag Manager** in the **Client Type** dropdown field, and paste your GTM Container ID (e.g., GTM-XXXXXXX) into the Google Tag Manager ID field.
+
+> **NOTE:** Ignore the GA4 Measurement ID field - simply leave it blank.
+
+![](/images/integrations/google-tag-manager/3.gtm_id.png)
+
+Finally, click **Create** to activate the integration.
+
+## Event Tracking
+
+Spree sends a full suite of ecommerce events to the GTM dataLayer. This allows you to create triggers and tags based on:
+
+- Product views
+- Cart actions (add/remove)
+- Checkout progress
+- Payment info added
+- Purchase confirmation
+- Search activity
+- Wishlist adds
+- Newsletter signups
+- User engagement (sessions, first visits, etc.)
+
+To make use of these events, you'll need to configure appropriate tags and triggers inside your GTM container.
+
+## Manage Your Integration
+
+To remove the integration or switch between GTM and GA4:
+
+Return to the integration setup page in Spree and either:
+
+- Clear the GTM field and enter a GA4 Measurement ID, or
+- Click Delete in the lower-right corner to remove the integration completely
+
+> **NOTE:** Only one analytics key should be set at a time (GA4 or GTM).

package/dist/integrations/integrations.md

@@ -0,0 +1,39 @@
+---
+title: "3rd party integrations"
+sidebarTitle: "All Integrations"
+description: "Learn how to connect your Spree application to third-party services and platforms."
+---
+
+## Payments
+
+
+  - [Stripe](/integrations/payments/stripe) — Stripe is a popular payment gateway that allows you to accept payments from your customers. Credit cards, wallets, buy-now-pay-later, installment payments and more.
+  - [Adyen](/integrations/payments/adyen) — Adyen is a global payment platform that enables businesses to accept payments across multiple channels and markets. Credit cards, digital wallets, BNPL, local payment methods, and more across 150+ currencies.
+  - [PayPal](/integrations/payments/paypal) — PayPal is an online payment system that allows you to send and receive money around the world. You can link your credit card, debit card, or bank account. You can also set up a PayPal Balance account.
+  - [RazorPay](/integrations/payments/razorpay) — Razorpay is a secure payment gateway that enables businesses to accept online payments via cards, UPI, net banking, and wallets. It also supports international transactions across multiple currencies.
+
+
+## Search
+
+
+  - [Meilisearch](/integrations/search/meilisearch) — One platform to build, scale, and unify search and AI retrieval. Search-as-you-type returns answers in less than 50 milliseconds. That's faster than the blink of an eye!
+
+
+## Analytics
+
+
+  - [Google Analytics 4](/integrations/analytics/google-analytics) — Google Analytics 4 is a powerful analytics tool that allows you to track user behavior, sales performance, and marketing effectiveness across your store.
+   - [Google Tag Manager](/integrations/analytics/google-tag-manager) — Google Tag Manager is a flexible tag management tool that lets you deploy and control marketing, analytics, and tracking scripts across your store.
+
+
+## Marketing
+
+
+  - [Klaviyo](/integrations/marketing/klaviyo) — Klaviyo is a marketing automation platform that allows you to send email campaigns to your customers.
+
+
+## SSO, MFA & Social Login
+
+
+  - [Admin Panel SSO & MFA](/integrations/sso-mfa-social-login/admin-dashboard) — Learn how to secure your Spree admin panel with SSO and MFA integration, using Microsoft Entra ID as an example.
+  - [Storefront SSO & Social Login](/integrations/sso-mfa-social-login/storefront) — Enable customer-facing SSO and social login on your Spree storefront, using Microsoft Entra External ID as an example.

package/dist/integrations/marketing/klaviyo.md

@@ -0,0 +1,99 @@
+---
+title: "Connect Klaviyo email marketing platform to Spree Commerce"
+sidebarTitle: Klaviyo
+description: "Learn how to set up and manage Spree's native Klaviyo integration."
+---
+
+Klaviyo is a powerful marketing automation platform used for email and SMS campaigns. By connecting your store to Klaviyo, you can automatically track user interactions, build audience profiles, and grow your newsletter subscriber base - all without manual setup.
+
+With Spree’s native integration, you can start collecting meaningful data for segmentation and automation with just a few clicks.
+
+> **INFO:** You must have an existing Klaviyo account to connect this integration.
+
+## Installation
+
+To install the Klaviyo integration, you need to run the following command:
+
+```bash
+bundle add spree_klaviyo && bundle exec rails g spree_klaviyo:install
+```
+
+After that, you need to make sure to restart the server.
+
+## Connect Klaviyo
+
+Sign in to your Spree admin dashboard and navigate to the Integrations tab. 
+
+![](/images/integrations/klaviyo/1.klaviyo.png)
+
+To connect Klaviyo, locate the Klaviyo tile under the Marketing section and click Connect Klaviyo to open the setup form.
+
+![](/images/integrations/klaviyo/2.creation_form.png)
+
+You’ll need to enter the following:
+
+- **Public API Key**: This key identifies your account to Klaviyo.
+- **Private API Key**: Used to authorize and securely send event and profile data.
+- **Newsletter List ID**: The ID of the Klaviyo list you want to use for newsletter signups.
+  - This list will be used as the default newsletter list for customers signing up from the storefront or checkout.
+
+Click **Create** to finalize the integration.
+
+> **INFO:** You must configure your Private API Key in Klaviyo before you can finalize the integration (see below).
+
+## Configure API Key Permissions in Klaviyo
+
+Before you can finalize the creation of your Klaviyo integration, you’ll need to create a Private API Key. To do so navigate to Settings → Account → API Keys in Klaviyo.
+
+![](/images/integrations/klaviyo/3.create_private_key.png)
+
+Click Create Private API Key to open the key creation form.
+
+![](/images/integrations/klaviyo/4.configure_private_key.png)
+
+When generating your Private API Key in Klaviyo, you must enable specific access scopes for the integration to function properly:
+
+- **Events** - Read/Write Access
+- **Lists** - Read/Write Access
+- **Profiles** - Read/Write Access
+- **Subscriptions** - Read/Write Access
+
+You can configure this by selecting Custom Key during key configuration, then selecting the required scopes as mentioned above.
+
+> **WARNING:** Without the appropriate access levels, some tracked events or newsletter subscriptions may fail to reach Klaviyo.
+
+## Event Tracking
+
+Once the integration is connected, Spree automatically tracks the following customer events and sends them to Klaviyo:
+
+- Product view
+- Product list view
+- Product search
+- Product added to cart
+- Product removed from cart
+- Checkout step view
+- Checkout step complete
+- Coupon entered/removed
+- Coupon applied/denied
+- Checkout email entered
+- Newsletter subscription
+- Unsubscribe from newsletter
+- Order Completed
+- Package Shipped
+- Cancelled Order
+
+> **NOTE:** When a user subscribes to the newsletter on the storefront, they’re automatically added to the list you configured in the integration settings.
+
+These events populate the Audience → Profiles section in Klaviyo, where you can view each user's tracked activity and properties. Lists used for newsletter subscriptions can be found in Audience → Lists & Segments.
+
+## Managing Your Integration
+
+![](/images/integrations/klaviyo/5.manage_integration.png)
+
+After setup, you can revisit the integration form at any time to:
+
+- **Edit keys** - useful if you want to swap out a list ID or rotate API keys.
+- **Update configuration** - simply adjust the values and click Update.
+- **Delete the integration** - click the Delete button in the bottom right of the form.
+
+> **NOTE:** Removing the integration stops data from being sent to Klaviyo, but it won’t affect historical data already collected.

package/dist/integrations/payments/adyen.md

@@ -0,0 +1,90 @@
+---
+title: "Connect Adyen payments to Spree Commerce"
+sidebarTitle: Adyen
+description: "Learn how to set up and manage Spree's native Adyen integration."
+---
+
+Adyen is a global payment platform that enables businesses to accept payments across multiple channels and markets. It supports a wide range of payment methods, provides advanced fraud protection, and offers seamless checkout experiences for customers worldwide.
+
+> **WARNING:** Adyen integration is currently in **private beta**. [Please contact us](https://spreecommerce.org/contact) to get access to the Adyen integration for your Spree store.
+
+## Installation
+
+Before you can enable Adyen, it must be installed. To do so, you need to run the following command:
+
+```bash
+bundle add spree_adyen --github spree/spree_adyen && bundle exec rails g spree_adyen:install
+```
+
+After that, you need to make sure to restart the server.
+
+## Connect Adyen
+
+Sign in to your Spree admin dashboard and navigate to **Settings → Payments**.
+
+![](/images/integrations/adyen/1.get_started.png)
+
+Find Adyen under Available Payment Methods and click **Add**.
+
+This will redirect you to the Adyen setup form.
+
+![](/images/integrations/adyen/2.setup_form.png)
+
+In order to retrieve your API keys:
+1. Make sure to be logged into your Adyen Merchant Account
+2. Navigate to **Developers → API credentials**
+3. Configure a new **API credential**
+4. Copy the generated **API Key** (you won't be able to see it later)
+5. Click **Save changes**
+6. Paste the **API Key** into its respective field in the Adyen setup form in Spree
+7. Click **Create** to enable Adyen as a payment method on your store
+
+![](/images/integrations/adyen/3.adyen_enabled.png)
+
+### Additional Settings
+
+![](/images/integrations/adyen/4.additional_settings.png)
+
+You can optionally configure the following settings for your Adyen payment method:
+
+- **Name**: Customize the display name shown for this payment method on the storefront.
+- **Display**: Choose where Adyen should be available:
+  - Storefront only
+  - Admin panel only
+  - Both (recommended)
+- **Auto Capture**: Decide whether payments should be automatically captured at the time of authorization (recommended), or manually captured later.
+- **Active Status**: Enable or disable the payment method. Inactive methods are hidden from checkout but not removed.
+
+### Test Mode
+
+If you want to test your checkout flow without processing real payments, Adyen's test mode is a safe and effective way to simulate transactions. To enable it, simply switch your Adyen Customer Area to **Test mode** and paste the corresponding **test API credentials** into the payment method settings in Spree.
+
+## Features
+
+Spree's native Adyen integration supports a comprehensive range of features and payment methods to help you offer a fast, secure, and flexible checkout experience:
+
+- Support for 3D Secure and other security standards
+- Support for off-session payments
+- Support for Storefront API integration (see the API docs [here](/api-reference/storefront/adyen/create-an-adyen-payment-session))
+- Accept payments in over 150 currencies
+- Accept Credit Cards, Debit Cards, and Digital Wallets
+- Accept Buy Now, Pay Later (BNPL) payments
+- Accept Bank transfers and Direct Debit
+- Accept Local payment methods (iDEAL, SOFORT, Bancontact, etc.)
+- Accept Mobile payments (Apple Pay, Google Pay, Samsung Pay)
+- Accept Cryptocurrency payments
+- Advanced fraud protection and risk management
+- Real-time payment status updates
+- Comprehensive reporting and analytics
+
+### Storefront Display
+
+Spree's Adyen integration enhances the customer experience with dynamic, context-aware payment options across the storefront:
+
+- Dynamic payment method selection based on customer location
+- Real-time payment method availability
+- Seamless checkout experience with Adyen's Drop-in component
+- Support for one-click payments and saved payment methods
+- Mobile-optimized payment flows
+
+Feel free to [reach out](https://spreecommerce.org/contact) to learn more.