Notice something different? Meet the new Solidus brand!

Use Cases

Use cases

Product

Developers

Resources

Big player with big needs? See what Solidus can do for you.

Enterprise

Solutions

The foundation to stand up. The flexibility to stand out.

Features

Don’t reinvent the wheel—use our built-in integrations.

Integrations

Pricing plans designed to accommodate your growth.

Pricing

Documentation

Policies

Insights and announcements from the Solidus team.

Blog

Need a bit of help? Engage our trusted partners!

Partners

Join us if you want to chat—we're a friendly bunch!

Community

## Introducing SolidusConf Speaker Peter Berkenbosch


We’re proud to announce that Peter Berkenbosch will be joining us as a presenter for **SolidusConf 2020**.

Peter has a Bachelor’s degree in computer science and got his start in the exciting world of ”Enterprise Java.” After discovering Ruby and Ruby on Rails in 2007, everything changed: he launched a Spree store, started actively contributing to the Spree community, and eventually, became a core team member at Spree. Since May 2015 Peter’s focus has shifted from Spree to Solidus.

Peter has a knack for producing high-quality code that is tried & tested, and can often be heard asking “are there any specs?” He usually works remotely from a small town in the Netherlands.

Currently Peter works as an independent e-commerce developer and consultant for a number of different agencies and stores, from troubleshooting (performance) challenges with large scale storefronts to development of (opensource) extensions and Saas storefront products and anything in between.

In his spare time, Peter loves hanging out with his children, fly-fishing, playing soccer, wine and dine, and cross-country runs with his adorable English Stafford.

### Building Payment Provider Integrations

Providing a detailed step by step technical insight on how to integrate payment service providers in your Solidus storefronts. Focused mostly on the Solidus Payment internals, but also touching the surface of development support tools and best practices.

### [See Peter speak at SolidusConf 2020](https://www.youtube.com/watch?v=pWznleqof8s&list=PLLD8ikQvfJqpscVZS3yJuftojeKcsjWeV&index=2&pp=iAQB)

We’re proud to announce that Peter Berkenbosch will be joining us as a presenter for SolidusConf 2020.

SolidusConf 2020 Presenter Peter Berkenbosch

## PayPal Made Easy

We're excited to announce that Solidus has a new payment method - [Solidus PayPal Commerce Platform](https://github.com/solidusio-contrib/solidus_paypal_commerce_platform)! This extension allows you to accept PayPal and credit/debit card payments directly to your business PayPal account, and adds some handy new features to Solidus.

###What new features does this extension add?

Well, dear reader, I'm glad you asked! In addition to adding an easy-to-use payment method, this extenion comes packed with three new features:

### Payment Setup Wizards

![](https://cdn.sanity.io/images/9g5nd6b4/production/a4bad7623d776130a530979ab5bd2da002bc4a8a-758x146.png?fit=clip&q=60)

We've added a system where any payment method can add a "payment setup wizard" - easing the onboarding process. For this extension, what that means is that you can hook your website to your PayPal account at the click of a button.

### Cart Payment Buttons

![](https://cdn.sanity.io/images/9g5nd6b4/production/d997d93bf10fc5b2fc3abd69604ee31843cb4fbb-1904x642.png?fit=clip&q=60)

Now your users can check out directly from your cart! This streamlined process will take the user to PayPal. During the checkout process, PayPal will collect the necessary shipping information and send it back to your server. Upon confirming the payment, the user will be taken to the order confirm page, where they can complete their order. 

### Product Payment Buttons

![](https://cdn.sanity.io/images/9g5nd6b4/production/a8b82efaa56ff68dd5ab7b6e6d0bffbfc5bbf3cf-584x530.png?fit=clip&q=60)

In addition to adding payment buttons to the cart, we've also added them to the product page! Unlike the cart button, product payment buttons act as an "instant checkout" feature - this will take the user to PayPal for payment, and the order will be created and populated will all necessary information. If your users just want the one item, they can skip almost the entire checkout process. Like the cart button, on payment, the user will be directed to the order confirmation page for final confirmation.

### What does "Default Payment Method" mean?

This extension is now the default payment method of Solidus. What that means is when you install new versions of Solidus, you'll see a prompt during installation asking you what payment method you'd like to install. Currently, those options will be "paypal" - installing this extension - and "none" - installing none. Any payment methods can be added to this list with no problems, but PayPal will be the default option.

### What should I know about the installation process?

The integration process is described in the extension README, but here are some common gotchas and possible surprises:

#### Phone Number Validation

Because addresses coming from PayPal do not require phone numbers, we've turned off phone number validation for addresses. You can override this, but you'll need to create a method for getting a phone number from your customers before or after returning from PayPal.

#### Order Completion

When your customer approves a payment on PayPal, they're taken to the checkout path - which should direct them to the order confirmation page. If you've removed the order confirmation step, you'll need to adjust the javascript method that redirects users to instead complete the order.

#### Order Totals

When a user clicks the PayPal button, Solidus sends line_item, adjustment, shipping and tax totals to PayPal. If these totals don't match, PayPal will not allow checkout. If you've done extensive modifications to anything involve the order total, you'll want to review the paypal_order model for accuracy.

#### Shipping Estimates

When a user logs in or changes their address on PayPal, PayPal sends a partial shipping address (missing only street address) and expects us to return an estimate for shipping. We simulate this change in the shipping rates controller, and return what the shipping would be for that address. Then, after the user confirms their payment, we get the finalized address from PayPal. This shouldn't cause you any issues unless you have a lot of customization around shipping rates, but you should keep it in mind just in case.

### Referral Fee

This extension has been sponsored by PayPal and implemented by [Nebulab](https://nebulab.com). PayPal will pay a commission fee to the maintainers for each order placed through the new payment gateway.

## What's Next?

This extension lays the groundwork for the future of Solidus payment methods. With the default payment system, you won't have to mess with your gemfile to install your payment extension. With the setup wizard, you'll be able to set up your payment provider at the click of a button. And with product payment buttons, installing an instant checkout feature is easier than ever.

## Final words

We've worked hard on this extension, and we hope it lives up to your expectations. If you find room for improvement, feel free to open an issue or PR!

And as always, make sure you stay up-to-date on the latest Solidus news by subscribing to the [Solidus newsletter](https://solidus.us13.list-manage.com/subscribe/post?u=679f4835b2683d59bc5762ec3&id=3ce07e9582).


Thanks, Solidus Community! You rock!

Learn about the new default Solidus payment method


Introducing Solidus PayPal Commerce Platform

## Introducing SolidusConf Speaker Taylor Scott


We’re proud to announce that Taylor Scott will be joining us as a presenter for **SolidusConf 2020**.

Taylor Scott is a Software Engineer at Sendoso. He has been working with Solidus for a few years, specializing in integrating Elasticsearch, custom payment methods, as well as building a physical and digital subscription service. On the line, you can find him playing games such as CoD, Elder Scrolls, and Hearts of Iron.

### The 5 W's of Application Logging

Often times when we write are logs we only include the “what” and “when”. Taylor would like to talk to us about getting the most of our application logging by discussing the importance of the “Who”, “Where”, and “why”. Having logs without context can be just as bad as no logs at all.

### [See Taylor speak at SolidusConf 2020](https://www.youtube.com/watch?v=Y0XAmRxkr3w&list=PLLD8ikQvfJqpscVZS3yJuftojeKcsjWeV&ab_channel=Solidus)

We’re proud to announce that Taylor Scott will be joining us as a presenter for SolidusConf 2020.

SolidusConf 2020 Presenter Taylor Scott

## Introducing SolidusConf Presenter Sean Denny


We’re proud to announce that Sean Denny will be joining us as a presenter for **SolidusConf 2020**.

Sean Denny is a developer at Nebulab and member of the Solidus Stakeholders - he's also the organizer for this and previous SolidusConfs! He got his start in web development at the age of 11, learning HTML to build a [Zelda fansite](https://web.archive.org/web/20010405002630/http://zeldacraziness.tripod.com/). His design skills have improved slightly since then. After work, Sean spends his time playing guitar, video games, and listening to the worst music imaginable.

### Don't Panic: The Solidus Guide to ReactJS

How do you bring the speed of ReactJS to the flexible and scalable Solidus ecosystem? The first step: Don't panic. Sean will take you through the basics - taking a vanilla Solidus store and adding ReactJS in step by step. Follow along as we take a look at how the Solidus API interacts with React, how React routing works, and some of the benefits of using ReactJS with Solidus. Just don't forget to bring your towel.

The workshop is a new addition to the SolidusConf lineup. These sessions will be longer than our traditional speaker spots, and more technically focused - be prepared to follow along as Sean shows you how to speed up your frontend!

### [See Sean speak at SolidusConf 2020](https://www.youtube.com/watch?v=AgHZLrhNAEo&list=PLLD8ikQvfJqpscVZS3yJuftojeKcsjWeV&index=4&pp=iAQB)

We’re proud to announce that Sean Denny will be joining us as a presenter for SolidusConf 2020.

SolidusConf 2020 Presenter Sean Denny

**Sparking community engagement and helping our open-source platform thrive, _Support Solidus_ is a _Call To Arms_ to contribute more to the platform we all love so much.**

_This article was originally posted on April 16th, 2020 to [Karma Creative](https://karmacreative.io/)'s website, you can read it here:
[Full Text of original Support Solidus Article](https://karmacreative.io/support-solidus)._


## Chapter 1: A Call To Arms

### The Movement, Its Origins, and What We Hope To Achieve

In an effort to demystify the team operating the open-source platform [Solidus](https://solidus.io/), and to rally support from members and participating stores, we’re updating the community today on the *“Support Solidus”* initiative.

The initiative is one that we at Karma Creative are proud to have spearheaded ourselves, but that doesn’t mean we did it alone. Far from it.

Rather, the idea arose out of a full year of biweekly meetings (hosted through virtual conferences on Zoom) between key members of the community. These ‘Solidus Stakeholder’ conference calls saw community members speaking out over their growing concerns and working together to solve problems and improve the platform. In need of support, these stakeholders found ways to help one another. And, just one year later, after working together as a team, we were thrilled to organize an incredible Solidus Conf 2019 in Salt Lake City, Utah. The atmosphere there was buzzing with new ideas and goals for the platform; we could tell that over that past year the community had become truly re-energized.

Needless to say, supporting Solidus has been at the front of our minds for a while. But ever since Hawthorn left the core team and Stembolt was acquired by JUUL, the community has realized it’s even more important to come up with innovative ways to maintain, fund, and support this amazing platform that we’ve grown to love.

Luckily, in the wake of Stembolt’s departure, Nebulab truly stepped up to the plate to fill their shoes, and has done an amazing job with Solidus.

After that pivotal Southeast SolidusConf in 2018, Nebulab almost immediately pledged to hire another open-source maintainer (using their own money), and have continued their strong dedication to the platform ever since. One fantastic initiative to highlight is that every Friday, their whole company spends the day working on open-source Solidus eCommerce. Incredibly, even by a conservative estimate, they still put several hundred thousand dollars a year worth of development time into the open-source platform. Not only have they taken on a ton of the maintenance, but they’ve also contributed some very welcome funding as the top contributing Ambassador on Open Collective.

But even so, in order for this effort to be sustainable, we knew we’d need to rally even more support and create a diverse group of volunteers who love the platform as much as we do,
and want to support it and shape its future.

That's why we at Karma Creative launched the Support Solidus Initiative: *to spark community engagement and to help our open-source platform thrive.*

![Support Solidus Logo](https://cdn.sanity.io/images/9g5nd6b4/production/31b06d29f65c18e68244db115c5d3f913f5d2c0f-800x592.jpg?fit=clip)

Wouldn't it be great to put some items from YOUR roadmap directly onto the Solidus Roadmap? That's our goal: To completely align with the community and implement items that are shared between individual retailers' roadmaps.

We printed these shirts at Solidus Conf 2019 to introduce the initiative:

![Mock Up of the Support Solidus T-Shirt that was printed for Solidus Conf 2019](https://cdn.sanity.io/images/9g5nd6b4/production/75c2ba4ba78c05ef5cb6fcbf8ac425e75e6ed650-600x352.jpg?fit=clip)

At Solidus, we want the goals of our stores and the goals of the platform to be totally aligned and symbiotic. But in order to have their own needs met and supported, stores need to support Solidus in return.

From our side, we know that doing so can create a ton of opportunity. It can open doors; streamline processes; enable community work on the features and benefits you want to see; and make your business earn more money with less effort. If you care about features and functionality, and if you want your own company roadmap to be a part of the equation, then supporting the platform is a necessary and prudent investment.

![Illustration of People in the Open Source Community Standing Together](https://cdn.sanity.io/images/9g5nd6b4/production/c0a6e06e9554cd5e4de2a61a846e36f9113b90dd-800x298.jpg?fit=clip)

### And It's in Your Best Interest Too

It might help the community (those on the fence about whether or not to join in) to be given a crystal-clear image of what open-source, Solidus, and donating to the platform will offer.

To start, just by choosing open-source, you open yourself to a world of opportunity. The community and the altruism built around it is palpable in long-running open-source projects like Ruby on Rails and Solidus. Instead of licensing fees, you have a veritable army of developers collaborating together with you, supporting you, providing regular maintenance on underlying dependencies, and so much more. Sure, sometimes you have to also give back to that project, platform, and community. But doing so multiples your *own* efforts and creates a positive feedback loop: one where we gain the ability to add more new features, improve our framework, and stay more secure. Open-source is congruent with success.

But why Solidus in particular?

- Complete control over your store.
- No licensing fees.
- Strong community.
- Solid core team.
- Support for high-volume stores with varied and complex needs, with many outlying use cases and features already included on the platform.
- And it scales.

‘Support Solidus’ means promoting access to future conferences, new features, hassle free maintenance, and better support. But moreover, it means peace of mind knowing that you’re securing the future of this platform as a leading open source e-commerce framework.

### How to Support Solidus: Money, Code, and Community Events

Now, it’s important to note that supporting Solidus can be done in different ways. It also depends on your own capacity as a store or developer.

We’ve touched on this in previous talks, but it might help to have a quick refresher on how to support Solidus. Basically, there are three crucial ways:

**Money:** If more agencies and stores commit to being Ambassadors (donating $750/month), we can support even more open-source development on the platform. This applies to everyone from big retailers to small agencies. But if this isn’t affordable, then we can all chip in something, even if it’s just $10/month. Everything counts.

**Code:** Take a look at any of the open issues on the repo or any of our core extensions. Provide some review on a PR. Or why not host an open-source Friday? It could be every Friday (like Nebulab), once a month, or even just once a quarter. If you cannot afford to donate funds, we hope you can give back to the community with your time and your code.

**Community Events:** Another awesome way to spread the word about Solidus, connect with the community, and to do your part in supporting the platform is to host a community event. We still need to put together an official guide for Solidus, but a good example of what to do is provided by Hacktoberfest. Here’s a link to their [Event Kit](https://hacktoberfest.digitalocean.com/eventkit/). Interested companies can look to them for a comprehensive list of what to do. Maybe you could commit to organizing and hosting a virtual event once a quarter. Our community would benefit in a myriad of ways from this type of engagement.

Finally, if you can’t commit to any one of these three things, perhaps you could at least join us in the Solidus Stakeholders Slack chat (solidus_stakeholders) and contribute your ideas at our weekly meetings. We would seriously love to have you.

The group is made up of different people who all have a significant stake in Solidus. Most members also contribute financially through Open Collective, where there are 3 tiers of support (Ambassadors, Supporters, and Enthusiasts), each contributing a different amount each month. At Karma Creative, we chose to be an Ambassador because it meant we could:

- Support the core team, community, and platform we love
- Actively shape the direction and strategy of Solidus
- Appear in the Community section on the Solidus site
- Get our logo out there on conference materials
- Be recognized in the readme and mentioned during conferences
- Have the option to join the partnership program as a Gold partner

And that brings us to our next point, which is to look at how far we’ve come as a platform since Stembolt broke the news they were leaving. Because we think a huge part of this is thanks to how we function as a community. People say that you go farther together, and that couldn’t have been more true for us.

Since Stembolt left, we’ve been busy. And creating a Slack channel was just the first step of many. From there, we set up organizational meetings, assigned roles, created streams of funding through recurring donations to the platform, supported and learned from each other, organized and attended conferences and, most importantly, built really solid relationships and trust within the community.

And as we touched on in our talk, trust and good relationships allow us to move forward together. Without it, there’s no real way to have an honest conversation about the roadmap, next steps, collaboration, or really anything.

In summary, the Support Solidus initiative was meant, first and foremost, as a *call to arms*. With your code, through becoming an Ambassador, or by donating your time, we want to remind everyone that, together, it can be done.

## [Click to Support Solidus](https://opencollective.com/solidus/contribute/)

Sparking community engagement and helping our open-source platform thrive, Support Solidus is a Call To Arms to contribute more to the platform we all love so much.


Support Solidus

## Introducing SolidusConf Presenter Thomas Sample

We’re proud to announce that Thomas Sample will be joining us as a presenter for **SolidusConf 2020**.

Focused on Spree and Solidus since 2013, Thomas founded [Karma Creative](https://karmacreative.io/) in 2017, a full-service custom digital agency focused on Solidus, eCommerce, and SEO. There he continues to work passionately on the platform he loves, committed to working with karma, and to providing real business value through close alignment and long-lasting relationships. Thomas also loves to play guitar, go hiking, and make hot sauce.

### The 10 Best Ways to SEO Audit Your Solidus Store for Free

A step-by-step walkthrough of an SEO Audit and a workshop to learn more about SEO. Find out what's new in 2020 and grab the low-hanging fruit for your Solidus Store. We'll focus in on the most important tips this time to make sure we see results by the end of the session.

The workshop is a new addition to the SolidusConf lineup. These sessions will be longer than our traditional speaker spots, and more technically focused - be prepared to follow along as Thomas shows up the SEO ropes!

### [See Thomas speak at SolidusConf 2020](https://www.youtube.com/watch?v=r_5HEJtA8I0&list=PLLD8ikQvfJqpscVZS3yJuftojeKcsjWeV&index=9&pp=iAQB)

We’re proud to announce that Thomas Sample will be joining us as a presenter for SolidusConf 2020.

SolidusConf 2020 Presenter Thomas Sample

## Introducing SolidusConf Speaker Edwin Cruz

We’re proud to announce that Edwin Cruz will be joining us as a speaker for **SolidusConf 2020**.

Edwin is co-founders and CTO at [MagmaLabs](https://www.magmalabs.io/), a company that specializes in Ruby on Rails and Solidus. When management tasks are over, it is time for some pair programming, find and fix performance issues, or improve open-source software. Edwin also attends conferences as an attendee or speaker, organize code retreats, and has one of the most demanding jobs, raising two kids with his wife.

### Marketplace on Solidus, Helping Local Businesses

Edwin will share how he leveraged existing open source projects such as Solidus and the Solidus Marketplace extension to create a portal where the main goal is to help local businesses to deal with the fact that they needed to sell their products and services online in order to have better chance to survive.

### [See Edwin speak at SolidusConf 2020](https://www.youtube.com/watch?v=WtZcxRQAskg)

We’re proud to announce that Edwin Cruz will be joining us as a presenter for SolidusConf 2020.

SolidusConf 2020 Speaker Edwin Cruz

## Introducing SolidusConf Speaker Jared Norman


We’re proud to announce that Jared Norman will be joining us as a speaker for **SolidusConf 2020**.

Jared Norman is an experienced Rubyist, bad hockey player, devoted metalhead, and the founder of [Super Good Software](https://supergood.software/), an agency specializing in Solidus/Spree, e-commerce, and Ruby on Rails.


### The Agile Fluency Model and eCommerce

Many Agile organizations are just going through the motions of their chosen process. Jared will walk us through how the Agile Fluency Model applies to eCommerce businesses and how they can use it to discover where they should focus to reap the real benefits of Agile methodologies.

### [See Jared speak at SolidusConf 2020](https://www.youtube.com/watch?v=9M0h2D4IvkE)

We’re proud to announce that Jared Norman will be joining us as a presenter for SolidusConf 2020.

SolidusConf 2020 Speaker Jared Norman

_This post was originally posted on the [Nebulab](https://nebulab.com/) website
[here](https://nebulab.com/blog/solidus-stripe/)._

[Strong Customer Authentication][SCA] (SCA) is a relatively new security
requirement that came in into force in Europe during September 2019.
In order to comply with the law, a store located in Europe must now accept
payments only through an SCA-ready payment method.

[Stripe][stripe], one of the major players in the online payment business, has
been offering a set of [modern API][stripe-api] that comply with these
requirements for a while and these API are now available also to Solidus' stores
via the gem [Solidus Stripe][solidus-stripe].

Currently, Solidus Stripe supports _Elements_, _Payment Intents_, and the _payment
request_ button API; let's briefly discuss the features offered by each of them.

### Stripe Elements

Elements was the first API provided with the third version (V3) of Stripe JS
library that got implemented in the gem.
Elements allows stores to build their payment pages by using pre-defined HTML
elements packed with JS functionality for a secure and easy payment flow:
everything is handled via javascript in the frontend without any need to
communicate with the store backend.

If you don't need SCA, this is by far the simplest and effective solution made
available by the gem: setup is very easy and your store will be ready to accept
credit card payments in a jiffy.

### Stripe Payment Intents

The Payment Intents API is based on Elements, so it maintains the very same
checkout UX and the ease of use when it comes to creating HTML elements, but
it includes the new SCA features that make it much more complex to implement in
regads to interactions with Stripe servers and the app backend:

> this API tracks a payment, from initial creation through the entire checkout
> process, and triggers additional authentication steps when required.

The good news is that the complexity has already been packed inside the
code of the gem, so you can relax and concentrate only on the setup procedure
described in the README.

Still, you may be interested in a general overview of what happens under the
hood when a __3D-Secure__ verification is required. The video shows the payment
process in the browser, a description follows below:

![](https://cdn.sanity.io/images/9g5nd6b4/production/18354dcae1d75d0d7db49ed24298bd0f0e208959-1920x1080.gif?fit=clip&q=40)

1. the Stripe Elements markup is added to the page by creating the card number,
card expire date and card CVC inputs;
2. after the customer enters the payment data and clicks the button, a new
payment method is created on Stripe servers for the given credit card number;
3. some data is added to the HTML form elements that will be used later at
submission time;
4. a JS asynchronous request sends the payment method token to the backend in
order to create a Payment Intents object that, depending on the credit card
type may require the customer to pass the additional SCA verification. The
payment intent has automatic confirmation method but requires manual capture and
can be used later for off session usage (in other words, the customer will be able
to reuse the card that they just entered in the system);
5. the frontend receives from the backend the payment intent client secret
token to be used for the 3D-Secure verification;
6. a 3D-Secure modal completely managed by Stripe pops up in the browser;
7. after successful code verification with the Stripe API, the store backend
tries to create the payment on the DB by using all the data provided by
the  frontend, including the customer address, credit card information and the
Payment Intent ID;
8. if all goes well, the frontend finalizes the payment and completes the form
submission, so Solidus can resume the usual checkout flow by taking the customer
to the last checkout step (confirmation).

You can take a look at the gem source code, especially the javascript part, if
you are interested in getting a deeper understanding of this process.

Be aware of an important _caveat_: the initial Payment Intents charge is created
_uncaptured_ on the payment step; it cannot be captured at that time, otherwise if
the customer leaves the checkout before confirming the purchase, it would not
be possible to revert the charge.
For this reason, capture must happen later in the Solidus backend, after the order
is finalized.

### Payment Request Button

The payment request button is based on Payment Intents and the official W3C
[payment request][payment-request] API. Just like Payment Intents, it's
SCA-ready so it can be safely used also on a European eCommerce.

Instead of leveraging the usual HTML elements, the payment is made in a
native environment specific for each browser.
This payment API is currently the only one from Stripe that supports
__Apple Pay__ and __Google Pay__.

The payment request button can be mounted directly on the cart page, allowing
customers to entirely skip the usual Solidus checkout process. This makes the
guest checkout easier, faster and more convenient, increasing conversions.

The most notable requirement for the button to work is that the store must
be on HTTPS, but setting up Apple Pay requires the extra step of creating a
verification file specific for the store domain and make it available at a
specific URL. Of course, more details can be found on the gem README and on
Stripe documentation.

Here's a video demonstrating the guest checkout with the payment button on the
cart page:

![](https://cdn.sanity.io/images/9g5nd6b4/production/c42dbdaaaf25507a758e6960ceceebe00e812a2d-1920x1080.gif?fit=clip&q=40)

When the customer clicks the button, the browser dialog window pops up
requesting them to choose the shipping address among the ones saved in the
browser, or enter a new one. After that, all the available shipping methods
with their costs are retrieved from the backend and the customer can pick their
preference.

The customer must have at least one credit card registered in their
browser, failing that the button will not show. If more than one card exists,
the customer will be able to choose among all of them.

![](https://cdn.sanity.io/images/9g5nd6b4/production/8fcba37be1986f990d9fcb6fcacd134e2ca10b24-1800x1724.png?fit=clip&q=60)

### Customizations

Customization is done by following the standard Rails/Solidus procedures when
it comes to ruby code (`Module#prepend` and [Deface](deface) are your friends)
while the JS can be customized easily by overriding the existing payment
method prototypes.

One frequent customization may consist in overriding the default locale
for Stripe Elements. If you want to switch from English to the Spanish
language, you can simply redefine the method `elementsBaseOptions` on the
prototype of the constructor `SolidusStripe.Payment` :

```js
SolidusStripe.Payment.prototype.elementsBaseOptions = function () {
  return {
    locale: 'es'
  };
```

Some level of visual customization can be achieved directly with CSS, but
sometimes, when using Elements and Payment Intents, your best option may
be to override the method `baseStyle` on `SolidusStripe.Elements.prototype`.


Enough talk, I hope this post helped in presenting all the possible
payment flows enabled by Solidus Stripe, it's now your turn to pick the
one more suitable for your store... happy coding!

[SCA]: https://en.wikipedia.org/wiki/Strong_customer_authentication
[stripe]: https://stripe.com/
[stripe-api]: https://stripe.com/docs/js
[solidus-stripe]: https://github.com/solidusio/solidus_stripe
[payment-request]: https://www.w3.org/TR/payment-request/
[deface]: https://github.com/spree/deface

Strong Customer Authentication (SCA) is a relatively new security
requirement that came into force in Europe during September 2019.

SCA payments with Solidus Stripe gem

## It’s time for SolidusConf 2020!

### Join us to discuss the past, present, and future of eCommerce
We’re proud to announce that SolidusConf 2020 will be a 100% completely digital experience held between September 23rd through 25th. In addition to bringing the excellent Solidus community together again, we’re also putting together an amazing list of speakers, and 3 unique workshops that you won’t want to miss. Plus, every attendee will receive a swag package in the mail, filled with Solidus-themed goodies. It’s going to be an exciting 3 days, and we can’t wait to see you there!



### Get Your Ticket to SolidusConf 2020
###### Learn, network, and share with the Solidus community
Ticket sales for SolidusConf 2020 are now OPEN. [You can find tickets here](https://opencollective.com/solidus/events/solidusconf-2020-c8147b09) - be sure to pick them up quickly to secure your spot! If you’re a student, reach out to [conf@solidus.io](mailto:conf@solidus.io) - we’ll have a certain number of free tickets to give out as well.


### Present at SolidusConf
###### Help make this the best SolidusConf yet
We want _you_ to present at SolidusConf this year. We need 6 speakers and 3 workshop presenters. The speaking sessions are traditional 30 to 45 minute spots, while the workshops are more involved - 2 to 3 hours of presentation & instruction, and you’ll have the opportunity to work hand-in-hand with conference attendees. If you’ve got an idea for a talk or a workshop, let us know on [PaperCall](https://www.papercall.io/solidusconf-2020)


### SolidusConf 2020 Sponsorship
###### Show your support for Solidus

These events are only possible with your support! If you’re interested in supporting Solidus, we’re interested in talking with you. Please reach out to [conf@solidus.io](mailto:conf@solidus.io) for more sponsorship information, and to take a look at our sponsorship prospectus. Or, if you're eager, you can go ahead and donate at the tier you want [here](https://opencollective.com/solidus/events/solidusconf-2020-c8147b09).

Announcing SolidusConf 2020

We've released Solidus
[2.10.2](https://github.com/solidusio/solidus/releases/tag/v2.10.2),
[2.9.6](https://github.com/solidusio/solidus/releases/tag/v2.9.6), and
[2.8.6](https://github.com/solidusio/solidus/releases/tag/v2.8.6)
to address a security vulnerability affecting all versions of Solidus.

The releases contain only one patch that addresses CVE-2020-15109.
You can read about CVE-2020-15109 on the [solidus mailing list](https://groups.google.com/forum/#!forum/solidus-security).

If you have any questions about how to secure your site please stop by our Slack [http://slack.solidus.io/](http://slack.solidus.io/).

Have a nice day!

New Solidus releases to address CVE-2020-15109. Please, update your store soon.

New Solidus releases to address a security vulnerability

Hello again, Solidus community! Here we are, with our usual roadmap update — this time, it's the Q2
2020 edition. We have tons of exciting news for you, so buckle your seat belts!

### Now available: data importer, content and GraphQL!

Last Friday marked the initial releases of three *huge* projects that we've been working on for the
last months:

- [solidus_importer](https://github.com/nebulab/solidus_importer): if you've ever worked on
  importing large amounts of data into Solidus (e.g. for a replatform), you know how repetitive and
  error-prone the process can be. Our shiny new data importer, compatible with most major eCommerce
  platforms, should make that much easier! Did we mention it's fully extensible?
- [solidus_content](https://github.com/nebulab/solidus_content): Solidus finally has an _omakase_
  solution for content management. If you need to integrate with Contentful, Prismic, Alchemy or
  any other content management solution, you can use solidus_content to streamline the process and
  create a nice backend UI to manage content. Check it out!
- [solidus\_graphql\_api](https://github.com/solidusio-contrib/solidus_graphql_api): the GraphQL API
  marks the beginning of a new era of headless eCommerce for Solidus. It's now feature-complete and
  ready to see some production traffic. If you're starting a new headless architecture with Solidus,
  you should definitely give it a try — and don't forget to leave feedback!

### Back in business: Klarna and solidus_subscriptions

In addition to releasing the new extensions, we also worked hard to bring home and polish some
popular community-maintained extensions:

- [solidus\_klarna\_payments](https://github.com/solidusio-contrib/solidus_klarna_payments):
  originally developed by [@josetonyp](https://github.com/josetonyp) and
  [@robinboening](https://github.com/robinboening), this extension adds support for
  [Klarna](https://www.klarna.com), a popular payment gateway in Europe. The authors were kind
  enough to let us move the code to solidusio-contrib, where the community gave it new life and made
  it compatible with the latest Solidus releases.
- [solidus_subscriptions](https://github.com/solidusio-contrib/solidus_subscriptions): originally
  developed by Stembolt for [Goby](https://goby.co), our subscriptions extension hadn't seen much
  love in a while. Things are much better now: the extension has been updated, tons of new features
  have been implemented and tons more are coming.

### To Q3 and beyond!

We have so much in store _(pun intended)_ for the next months.

In Q3, we will continue to iterate on the extensions we have released, based on community feedback
and any requirements and edgde cases that emerge from production usage.

However, we won't just rest on our laurels: the next quarter is also when we'll focus on our
omnichannel strategy, making it easier than ever to keep your Solidus catalog in sync with major
platforms such as Amazon, Facebook and Instagram.

We'll also continue working on extendability, improving Solidus' event-driven architecture, and on
enabling support for the latest frontend technologies through our Next.js starter kit.

Finally, we'll complete and publish our new [developer guides](https://guides.solidus.io), which
will not only lower the barrier of entry for becoming a Solidus developer, but also shine a new
light on many of Solidus' lesser-known features and capabilities.

### As always: thank you! 🙇‍

We can't stress this enough: thank you, thank you, thank you. To everyone who's helped with their
contributions, both technical and financial, to everyone who's given us feedback and to everyone
who's shared their appreciation for the community's work. You drive us forward and bring out the
best in us.

Stay tuned for updates via [our blog](/blog) and newsletter, and [reach out on
Slack](https://slack.solidus.io/) if you have any questions, want to help, or just feel the urge to
share some love!

Let's continue shaping the future of eCommerce — free, open-source and community-driven.

Check out the progress we've made towards our roadmap in Q2 2020!

The Solidus Blog