Phil Derksen

@hkpresent We’ve never tried that specifically but you can check out our reference for developers and code snippet library to see if anything would work.

https://docs.wpsimplepay.com/articles/code-snippet-library/

Note that it’s a combined reference and some snippets will only work in the Pro version.

@muypescado We’re currently working on it but don’t have a release date set yet. It’s one of the top features under development though!

https://docs.wpsimplepay.com/articles/new-stripe-checkout/

@plasmax These docs are for the Pro version but it covers what you need in terms of setting up the Lite version in the way you described.

https://docs.wpsimplepay.com/articles/first-payment-form/

Hi Bryan,

We are deprecating the old [stripe] shortcode in favor of the payment form designer that has been a part of WP Simple Pay for nearly 2 years.

However, if you were using your Stripe API keys in the plugin’s “Legacy Settings” and not authorized with Stripe in the non-legacy settings it still should’ve worked until the next release.

The easiest thing to do at this point is to create your forms using the plugin’s form designer and place the much simpler [simpay] shortcode on the page.

Please see https://docs.wpsimplepay.com/articles/first-payment-form/

Thanks,
Phil

@jamroller If you’ve ruled out specific web server settings, database settings or plugin conflicts that might be contributing, I’m not sure what else could be causing this.

We do have a task to take another look at our use of sessions in WP Simple Pay, so if there are improvements that can be made we’ll hopefully discover and implement them sooner rather than later.

Cheers,
Phil

@krzeslo12 From the looks of the URL querystring, I believe the issue is related to WooCommerce Stripe, which this plugin is not.

That said, coming soon page plugins usually block most traffic unless logged in, so you may need to make an exception in the coming soon plugin for the URLs your Stripe plugin needs.

Hope that helps.
-Phil

@jamroller A few things to check that I can think of if you haven’t already.

WP Simple Pay should clean up after itself, but it requires you to uncheck the “Save Settings” option in the WPSP General Settings.

You can also look for any entries in the wp_options table starting with “simpay_”, or if you had a really old version at one point, starting with “sc_”.

Finally, we’re using our own implementation of Eric Mann’s WP Session Manager, so if you have that plugin installed, or if another plugin is doing something similar to us, that may be causing conflicts.

Hope that helps!
-Phil

Answered here.

Hi @manuarmand,

WP Simple Pay doesn’t include an invoicing piece at the moment. However, I would recommend checking out Sprout Invoices, a full-featured invoicing WordPress plugin with a great Stripe integration.

Cheers,
Phil

@dominopark Thanks so much for the review!

@kawaiikawaii That’s a bug on our end. We’ll be allowing you to dismiss that notice in the next update.

Cheers,
Phil

Thanks so much for the review @nickrytlewski !

@richmandan Stripe Connect isn’t in this version of WP Simple Pay, so you must be referring to Pro, which in that case a recent update took care of this.

@perfectword7 Yes it does! If you’d like more details please contact us at https://wpsimplepay.com/ for further questions about the premium version.

Cheers,
Phil

@brianm523 You must be using a different plugin and not this one and/or you have some customizations outside the scope of our plugin.

Cheers,
Phil