<p>My understanding of Stripe Checkout is that it doesn't actually charge the user's card. It simply authorises it, and returns a token which you can then use in a server-side script to capture the payment using the Stripe API.</p>

<p>As such, you'll need a server-side component, in the form of a plugin. <a href="http://squarebit.co.uk/software/craft/charge" rel="nofollow" title="Coded by hobbits">Charge</a> might provide a decent starting point for that.</p>

<p>I don't think Charge works with Stripe Checkout as standard, but it's probably worth having a chat with the developer (Joel Bradbury) about the costs of adding this functionality.</p>

CC BY-SA 3.0
2015-03-04T13:01:03.377Z
Added a separate comment in more details about a possible implementation with Charge : http://craftcms.stackexchange.com/questions/8418/how-can-i-record-sales-data-from-stripe-checkout-and-then-restrict-access-to-con/8496#8496
Joel Bradbury
CC BY-SA 3.0
2015-03-03T21:37:58.147Z
2015-03-03T21:37:58.147Z
Stephen Lewis
<p><em>Disclaimer : I'm the developer of <a href="http://squarebit.co.uk/software/craft/charge" rel="nofollow">Charge</a> so am obviously biased</em></p>

<p><a href="http://squarebit.co.uk/software/craft/charge" rel="nofollow">Charge</a> uses the Stripe API directly and doesn't support the Stripe Checkout modal method for payments. It is something I've looked into, but haven't had the opportunity to implement. </p>

<p>Stephen's comment is correct - while the front-end form implementation is simplified using Stripe Checkout, a server side component is still required and that's where the majority of the work is.</p>

<p>If you really require Stripe Checkout support it's certainly something that can be added. Get in touch <a href="http://squarebit.co.uk/contact" rel="nofollow">here</a> and we can discuss details/requirements</p>

<p>On the side of updating elements on success, that's a feature that's in the next release of Charge (2.0), which I'm prepping right now.</p>

CC BY-SA 3.0
2015-03-04T13:03:05.467Z
That is great Joel. I will watch for Charge 2.0 as that success updating feature is one we have been looking for.
Bryan Garrant
CC BY-SA 3.0
2015-03-04T13:00:27.223Z
2015-03-04T13:00:27.223Z
Joel Bradbury
<p>I have a client that is going to use Stripe Checkout (<a href="https://stripe.com/checkout" rel="nofollow">https://stripe.com/checkout</a>).  We are trying to figure out how we can simply record the sale data into Craft.  We know of other plugins that use Stripe, but we really want to use Stripe Checkout as it is great for mobile.</p>

<ol>
<li>How can we write data to an entry after the Stripe sale?  We would
need basic things like Customer Name, Item(s) purchased, Order
Total.  The items would all be entries in Craft already.</li>
<li>How can we restrict content viewing based on the items purchased? 
Basically if you buy Product X which is an entry page of content,
how can I secure that entry so only people who have a confirmed
purchased can view the template?  Since there will be about 10
products, we really can't use User Groups for this.  We need the
permission to be on the item purchased level.</li>
</ol>

<p>Any help is greatly appreciated.  If we need a custom plugin for this would anyone be interested in making one?  Should be pretty simple using the Stripe API I would imagine.</p>

<ecommerce>
How can I record sales data from Stripe Checkout and then restrict access to content based on the item purchased?
# How can I record sales data from Stripe Checkout and then restrict access to content based on the item purchased?

(Asked by: username_0 on 2015-02-27)

I have a client that is going to use Stripe Checkout (<https://stripe.com/checkout>). We are trying to figure out how we can simply record the sale data into Craft. We know of other plugins that use Stripe, but we really want to use Stripe Checkout as it is great for mobile.

1. How can we write data to an entry after the Stripe sale? We would
   need basic things like Customer Name, Item(s) purchased, Order
   Total. The items would all be entries in Craft already.
2. How can we restrict content viewing based on the items purchased?
   Basically if you buy Product X which is an entry page of content,
   how can I secure that entry so only people who have a confirmed
   purchased can view the template? Since there will be about 10
   products, we really can't use User Groups for this. We need the
   permission to be on the item purchased level.

Any help is greatly appreciated. If we need a custom plugin for this would anyone be interested in making one? Should be pretty simple using the Stripe API I would imagine.

**Tags:** ecommerce

---

## 2 answers

### Answer by username_1 on 2015-03-03. Score: 1

My understanding of Stripe Checkout is that it doesn't actually charge the user's card. It simply authorises it, and returns a token which you can then use in a server-side script to capture the payment using the Stripe API.

As such, you'll need a server-side component, in the form of a plugin. [Charge](http://squarebit.co.uk/software/craft/charge "Coded by hobbits") might provide a decent starting point for that.

I don't think Charge works with Stripe Checkout as standard, but it's probably worth having a chat with the developer (Joel Bradbury) about the costs of adding this functionality.

> **Comments:**
> **username_2**: Added a separate comment in more details about a possible implementation with Charge : http://craftcms.stackexchange.com/questions/8418/how-can-i-record-sales-data-from-stripe-checkout-and-then-restrict-access-to-con/8496#8496  

---

### Answer by username_2 on 2015-03-04. Score: 1

*Disclaimer : I'm the developer of [Charge](http://squarebit.co.uk/software/craft/charge) so am obviously biased*

[Charge](http://squarebit.co.uk/software/craft/charge) uses the Stripe API directly and doesn't support the Stripe Checkout modal method for payments. It is something I've looked into, but haven't had the opportunity to implement.

Stephen's comment is correct - while the front-end form implementation is simplified using Stripe Checkout, a server side component is still required and that's where the majority of the work is.

If you really require Stripe Checkout support it's certainly something that can be added. Get in touch [here](http://squarebit.co.uk/contact) and we can discuss details/requirements

On the side of updating elements on success, that's a feature that's in the next release of Charge (2.0), which I'm prepping right now.

> **Comments:**
> **username_0**: That is great Joel. I will watch for Charge 2.0 as that success updating feature is one we have been looking for.  

---

