David Parker

Hi Gary,

Yes, this should be possible by following these steps:

1. Create two separate products in Stripe: One with a default price recurring monthly and the other with a default price recurring yearly
2. When editing content that you would like to restrict, select the checkboxes for both of these products in the “Restrict With Stripe” panel
3. Save the content

When multiple products are checked, the user should be able to see restricted content when they have purchased either of those products. If the user has not purchased one of those products, then they should be given the option to choose which product they would like to purchase.

Please let me know if you have any questions while setting this up on your website.

Hi @dreadedhamish,

By default, Restrict With Stripe integrates with Block Editor and Classic Editor included in core WordPress. Other page builders may or may not be compatible with Restrict With Stripe depending on how they are coded.

Although native support may be added for some 3rd party page builders in the future, this is not something that is included in Restrict With Stripe at this time. If the page builder on your website is not compatible with Restrict With Stripe, custom development would be needed to add compatibility between these two plugins.

Hi @dreadedhamish,

That code looks like it should work, though it is important to thoroughly test on your website to ensure that it works as expected in practice.

One thing that I notice is that you are not checking whether the customer has already purchased the product before showing the restricted content message. This means that customers will see the purchase link even if they have already purchased the product.

Hi @dreadedhamish,

Although customizing the signup/purchase flow within the plugin is theoretically possible, it would require a significant amount of custom development and testing to implement.

When developing this plugin, one of our goals was to keep the plugin as streamlined as possible and require as few clicks as possible when users sign up on your website. Currently, the four times that we require user input are:

1. Creating a new user on the site if the user is not already logged in
2. Selecting a Stripe product to purchase if there are multiple purchase options available
3. Clicking the “Checkout” button to be redirected to Stripe
4. Completing payment in Stripe

If you have any suggestions for streamlining the signup flow further, please let us know as having a simple signup process is a priority for this plugin.

Hi @dreadedhamish, thank you for using Restrict With Stripe!

Can you please try adding the following code recipe to your website and letting me know if the restricted content message then filters correctly?

function my_rwstripe_restricted_content_message( $restricted_content_message ) {
	return str_replace( 'Purchase Access', 'Start your Subscription', $restricted_content_message );
}
add_filter( 'rwstripe_restricted_content_message', 'my_rwstripe_restricted_content_message' );

Hi @kristofferhb,

According to Stripe:

Users won’t be able to connect multiple platforms to the same account due to the single Platform connection policy. Instead, users that plan to use Stripe with multiple platforms can create individual accounts under the same Stripe user login to connect to different platforms.

https://support.stripe.com/questions/security-permissions-and-access-levels-when-connecting-your-stripe-account-to-a-third-party-platform

As a result, a new Stripe Account will be needed to use Restrict With Stripe. Can you please try:

1. Clicking the “Connect to Stripe” button on the Restrict With Stripe settings page
2. Scrolling to the bottom of the account connection page and clicking “Create a new account”
3. Following the account creation process

If you continue to see the “The Stripe account selected was created by another platform” error after following those steps, it may be necessary to contact Stripe Support as Stripe has control of the onboarding flow that is showing this error message. It is possible that they may be able to help you set up a new Stripe account that can then be used with Restrict With Stripe.

Please let me know if you have clarification questions about any of this.

Hi @smenaria2,

As we have not heard back from you, I am going to mark this support thread as resolved. If you would like to continue discussing this issue, please feel free to open a new support ticket and we can continue our discussion there.

Hi @smenaria2, thank you for that additional information.

We have been able to replicate this issue that you are experiencing by trying to create a new account with the country field set to “India”, but this is not a restriction that is being set by Restrict With Stripe.

To confirm this, we have also tested this behavior with a number of other WordPress plugins that use the same Stripe registration flow as our plugin (Stripe Connect for standard accounts) and can confirm that the same error message is shown when trying to connect with those plugins.

We were not able to find a plugin named “WP Simple Stripe”. Can you please link us to that plugin so that we can take a look at how they are performing Stripe authentication?

Hi @smenaria2,

Stripe does not allow a single Stripe account to be used with multiple platforms/plugins as per the “Using Stripe with multiple platforms” section of their “Security, permissions, and access levels when connecting your Stripe account to a third-party platform” support article.

Instead, can you please try creating a new account in Stripe when trying to connect your website to Stripe? You can have multiple Stripe accounts that are all accessible with the same Stripe login credentials.

Hi @markfulton,

After speaking with the Stripe development team, it does not sound like the “Free Trial” option on prices will ever have native support with Stripe Checkout. As a result, Restrict With Stripe will not be able to support that option.

As free trials are an important feature, we have just released Restrict With Stripe v1.0.9 which contains filters that developers can use to modify the behavior of this plugin. Using these new filters, I have put together a code recipe that you can use to add a 7-day trial when new customers purchase a subscription on your website:

https://gist.github.com/dparker1005/a36c083630a9d55aa23ec12bdc63ab01

An added benefit of this approach over Stripe’s legacy “Free Trial” option is that, as written, the code that I provided will only add free trials for new users, preventing a single users from claiming multiple free trials.

Regarding your “payment button” question, this plugin does not have a built-in payment button. The “purchase” form will currently only show on pages that are restricted by this plugin.

Our recommended approach here would be to create a new Page on your website with purchase confirmation text (ex. “Thank you for your purchase. etc”) and to restrict that page to one of your Stripe products. With that setup, when users on your site purchase your product from that page, they will see the confirmation text when they return to your website.

Once that new page is created, you can add a “Buy Now” button to your home page in any way that you would like, and that button just needs to be set up to link to the restricted “confirmation” page that you created.

The last thing that you would probably want to do with this flow is disable the “Show a content excerpt on restricted posts or pages” setting in the Restrict With Stripe Advanced settings so that users don’t see any confirmation text until they complete their purchase. With that setup, the user flow would be:

1. View your home page
2. Click the “Buy Now” button
3. Be sent to the restricted “confirmation” page that you created
4. Enter their email/password to create an account
5. Pay in Stripe
6. Return to the “confirmation” page, which will no longer be restricted

I hope this helps to give you the tools that you need to build your website with Restrict With Stripe. Please let me know if you have any futher questions about this.

Hi @markfulton, thank you for using Restrict With Stripe!

We have just released Restrict With Stripe v1.0.8 which adds compatibility with Elementor. Can you please try updating the plugin on your website and let us know if the content restrictions are then working as expected?

Regarding your question about how user creation works, Restrict With Stripe only creates users on your WordPress site when the user views restricted content and fills out their email address before being sent to the payment step. If a user pays in Stripe without being sent there by Restrict With Stripe, a user account will not be created for them.

If you already have users who have completed Stripe payments without having user accounts created, Restrict With Stripe does give administrators the option to provide a user’s Stripe Customer ID when creating a user from the WP Dashboard in order to link their new WP User to their existing Stripe Customer.

Finally, Restrict With Stripe does not support the legacy “Free Trial” option that is shown when creating a Price in Stripe. According to Stripe’s tooltip for that field, “setting a default trial period per price is no longer recommended and is incompatible with Checkout and quotes. Free trials can be set per subscription or quote instead”. As Restrict With Stripe processes payments with Stripe Checkout, this plugin will not support free trials there is native compatibility in Stripe between Stripe Checkout and free trials set for Stripe Prices.

I hope this information helps to get you started! Please let me know if you have further questions about any of this.

Hi Gary, thank you for that additional information.

We have just released version 1.0.6, which add support for restricting posts and pages in the classic editor.

I hope this helps! Please let me know if you still have any questions about restricting posts or pages on your website.

Hi Gary,

When editing a page or post in the WordPress Block Editor, there should be a “Restrict With Stripe” dropdown panel in the “Settings > Post” menu. In that panel, there will be a list of your Stripe Product that you can restrict by, similar to how restrictions are shown when restricting a category.

Please let me know if you have any further questions while setting up your page restrictions.

Hi Gary,

We have actually just released Restrict With Stripe v1.0.5 which adds the ability to include the Stripe Customer ID when creating a new user in WordPress and also allows for updating the Stripe Customer IDs for existing users when editing their profiles. This update should prevent the need to make changes directly to the site’s database.

Once you know the rws_customer_id_ key for your site (it contains your Stripe account ID which is why it varies from site to site), it should also be possible to import users in bulk using a WordPress user import plugin that allows for importing user metadata.

I hope this helps to get you started! Please let me know if you have any further questions about this.

• This reply was modified 1 year, 8 months ago by David Parker.

Hi Gary,

Restrict With Stripe links WordPress users to Stripe customers by storing the ID for the Stripe Customer as metadata on the WordPress user object. The WordPress user is then said to have purchased a Stripe product if their associated Stripe Customer has an active subscription for that product.

There is not currently a user-friendly way to set the Stripe Customer ID for a specific WordPress user, but I have just added this as a feature request on the Restrict With Stripe repository here:
https://github.com/strangerstudios/restrict-with-stripe/issues/17

In the meantime, if you would like to link a user to a specific Stripe account, this would need to be done directly in the wp_usermeta table of your database by finding the entry with the user_id of the user who you would like to link to Stripe and the meta_key beginning with rws_customer_id_. Updating the associated meta_value with the ID of the Stripe Customer should give the user the access that the Stripe Customer has purchased.

For your use case, you would need to create a WordPress user and then update its meta value for each Stripe Customer that you would like to import. We highly recommend backing up your database before making any manual changes so that those changes can be reverted if anything goes wrong.

Please let me know if this all makes sense or if you have any clarification questions about this.