Recently, we've been working on a Solidus-based project that uses Solidus via an API. To enable Stripe payments within this setup, we needed to add additional API endpoints and logic for creating payment intents within Stripe. The intent information can later be used in combination with the Stripe Payment Element.
This PR aims to integrate these changes into the upstream solidus_stripe.
It adds the following API endpoints:
Create Setup Intent
Create Payment Intent
More details on these endpoints can be found in the README here.
The core logic of this change is encapsulated in service objects, making it easy to create these intents outside of the API as well (e.g., if you prefer a custom GraphQL mutation or need to create a payment intent outside of the regular checkout process for some reason).
Summary
Recently, we've been working on a Solidus-based project that uses Solidus via an API. To enable Stripe payments within this setup, we needed to add additional API endpoints and logic for creating payment intents within Stripe. The intent information can later be used in combination with the Stripe Payment Element.
This PR aims to integrate these changes into the upstream
solidus_stripe
.It adds the following API endpoints:
Create Setup Intent
Create Payment Intent
More details on these endpoints can be found in the README here.
The core logic of this change is encapsulated in service objects, making it easy to create these intents outside of the API as well (e.g., if you prefer a custom GraphQL mutation or need to create a payment intent outside of the regular checkout process for some reason).
Checklist
Check out our PR guidelines for more details.
The following are mandatory for all PRs:
The following are not always needed: