Spree Commerce documentation home page
Search...
⌘K
Community
Github
Getting started
Quickstart
Architecture
Stores
Orders
Users
Products
Inventory
Payments
Taxes
Promotions
Shipments
Calculators
Adjustments
Addresses
Internationalization
Customizing Spree
Quickstart
Configuration
Storefront
Admin Dashboard
Authentication
Checkout Flow
Permissions
Dependencies
Decorators
Model Preferences
Metadata
Routes
API
Custom Promotions
Extensions
Use Cases
Multi-Tenant
Deployment
Render
Docker
Environment Variables
Emails
Assets
CDN
Caching
Upgrading
Quickstart
Upgrade Guides
Contributing
Quickstart
Developing Spree
Creating an Extension
Security
Security policy
PCI Compliance
Advanced
Adding to an existing Rails app
Support
Get started
v5
Spree Commerce documentation home page
v5
Search...
⌘K
Ask AI
Support
Get started
Get started
Search...
Navigation
Security
PCI Compliance
Developer Docs
Ecommerce API
Integrations
User Docs
Use Cases
Developer Docs
Ecommerce API
Integrations
User Docs
Use Cases
Security
PCI Compliance
All store owners wishing to process credit card transactions should be familiar with
PCI Compliance
.
Spree Stripe
and
Spree Braintree vzero
are PCI-compliant.
Using payment tokens
We do not transmit or store Credit Card numbers. Instead we’re using payment processor tokens supplied by their SDKs to authorize and charge customer cards.
3-D Secure and Strong Customer Authentication support
Spree Stripe integration
supports
Strong Customer Authentication (SCA)
out of the box. We also use Stripe JavaScript SDK to render all payment forms.
Spree Braintree vzero
extension supports
3D Secure 2.0
.
Was this page helpful?
Yes
No
Suggest edits
Raise issue
Previous
Adding to an existing Rails app
This guide will show you how to add Spree to an existing Ruby on Rails application.
Next
On this page
Using payment tokens
3-D Secure and Strong Customer Authentication support
Assistant
Responses are generated using AI and may contain mistakes.