Forum Replies Created
-
Posts
-
In addition to what @ovidiubica said, check the individual product configuration and make sure you didn’t force enable test mode for that product.
If this is for a subscription product, then go through each of the following checklist items and check them one by one to make sure all the setup is correct. Then do a new test transaction after that.
Checklist #1) If you have changed between “live” and “test” mode, then make sure to create a new subscription plan in the mode that you are currently using and then use that plan to create a new subscription product.
Checklist #2) Go to the settings menu of the Stripe payments plugin and check the API key section. Make sure to copy and paste all the CORRECT API keys in those 4 API key fields. To be more specific, the following 4 fields must contain valid values:
– Live Stripe Publishable Key
– Live Stripe Secret Key
– Test Stripe Publishable Key
– Test Stripe Secret KeyChecklist #3) Go to the “Subscriptions” tab in the settings menu of the plugin. Check that the webhooks are setup correctly. Both the live and test webhooks should be setup. If in doubt, do the following steps to set them up correctly:
– Click the “Delete Webhooks” button.
– Click the “Clear Cache” button to clear any webhooks cache.
– Click the “Create Webhook” button in the “Live Webhook Status” section and wait for the addon to automatically create it for you.
– Do the same for “Test Webhook Status” section.
– Click “Save Changes”.The plugin supports 3D secure payment.
Go to the Advanced settings menu of the plugin and try enabling the following feature:
Disable 3D Secure IframeThis is be helpful on some server configurations.
Next, enable the following debug logging option and do a transaction. It can give additional clues about the issue:
Using the Debug Log to Solve Transaction Related Issues on a Site
Also, make sure the stripe subscription addon is updated to the latest.
Not at the moment since that is not the primary focus of this plugin. We will try to add some options for it in the future.
I understand. I would prefer to handle this using a filter hook potentially. We can add a new filter or action hook that you can use to add the desired no-index parameters to your site. This will ensure that there cannot be any unexpected result on a lot of other sites that doesn’t want it.
You can suggest a hook that will help you do this for your site. You can also create a pull request on the Stripe plugin’s repository:
https://github.com/Arsenal21/stripe-paymentsThere is nothing wrong with this. That is just HTML code of the button. If you have buttons on a page, it can be indexed (if that page is indexed). There is no harm in that. Trying to massage or play around with the indexing is not wise. Search engines are super smart and they figure out what is really true content and not.
If you don’t want certain pages to be indexed, then just edit the page or post and use the SEO plugin to specify the page to have no-indexing.
Generally, it is not wise for our plugin to mess with indexing since that is the job of a SEO plugin. You should have a SEO plugin that can allow you to customize the SEO properties of a page (including description).
Unfortunately no. Our Stripe plugin works the way we show in our demo video.
Our WP eStore plugin has the stripe checkout option that you are talking about. However, for our Stripe payments plugin we took feedback from our users and this is the checkout flow they wanted so we made a decision to go with this process.
By default the e-commerce tracking only works on the thank you page generated by our plugin. We will need to investigate and see if we can extend the function for custom thank you pages also.
No, it cannot do subscription. The addition payment methods can be used for one time normal payments only.
What version of the Subscription addon are you using? You can see the version number in the plugins menu of your site.
Looks like something maybe preventing the loading of that module. Do the following to see if there is a plugin conflict on this site:
Test for Plugin and Theme Conflict Before Posting an Issue or a Bug
Also, check the server’s error_log file. That file will contain more details as to what action is triggering the Error 500. That will be helpful to understand what could be going wrong on this site.
We have added a feature for this in the new version of the subscription addon. You can edit a subscription plan and specify a customized description for the plan terms.
That’s going to be hard to figure out and will need to be handled as a custom job. Instead try the following feature so you can hook the payment process to the button you are creating using your theme:
Post a URL where I can go and see this using my browser (to see if I can get any clues).
Also, do the following to see if there is additional info in the debug log file (that can be helpful to get some clues):
Using the Debug Log to Solve Transaction Related Issues on a Site
See if the following addon works:
If that doesn’t then you will need to create a customized language translation file for your site where that text can say what you want it to say.
