Forum Replies Created
-
Posts
-
Hi Marie, It’s a good idea to double check the following Apple Pay instructions to make sure the setup is correct so I will put the link here:
If you go to the “Additional Payment Methods” tab in the settings menu, do you see any error or warning there? The domain is verified with apple pay using the “Autoapprove Domain” button?
Is the product in question a subscription product by any chance?
Please make sure the custom fields addon is updated to v2.0.7
The following addon lets you auto update and stay up to date with the addons:
This particular hook is triggered by a Stripe hook. It runs early on the loading process so this code needs to be put into a place that is visible much earlier. If you are putting the code into a file that is loading AFTER the hook is being triggered, then you will see the behavior that you are seeing. Not all hooks are triggered at the same time. Different hooks have different conditions. You may need to get help from a WordPress coder for this.
You should probably make a small custom plugin and put this custom code in that plugin so it is visible when that hook is triggered. It’s generally a good idea to put all your customization code into a separate plugin. Otherwise in the future if you switch your theme, you will lose all the customization.
We are not familiar with that particular plugin you mentioned but yes there are some plugins out there which can create a conflict. So the best option is to do the following test:
Test for Plugin and Theme Conflict Before Posting an Issue or a Bug
Hi Matt, The custom fields addon needs to be upgraded to v2.0.7.
Please use the following add-on which will check fro updates and allow you to auto-update:
Alternatively, you can download the latest copy from the following page and you can upgrade it manually:
Hi, Enable the debug logging feature and try to do a test transaction. It will reveal clues as to what could be going wrong. That information will be very helpful:
Also, post the URL of the page containing the button so we can inspect it and see if there is any JavaScript or captcha error.
Did you enable captcha? If you did which one did you enable? Sometimes this type of issue happens from not having entered the correct captcha API keys.
Hi, I sent the following response to your email query also. I will give the response here as well (in case you don’t receive the email).
—
It looks like the Main stripe plugin’s settings were never saved on this site (or the main stripe plugin doesn’t even exist). The subscription addon requires the main Accept Stripe Payments plugin to be active and configured first.So let me check to make sure that has been done correctly.
Can you please show me a screenshot that shows that the “Accept Stripe Payments” plugin is active on your site? You can go to the plugins menu of your site to see all the plugins.
Next, go to the settings menu of that plugin and save the settings. Just hit save settings with the default values there (you can update them later). After that step, you can try to re-activate the subscriptions addon.
Can you please give an example so I can understand the question better? Do you have a page where I can go and see what you mean?
For subscription payments the charge is processed differently than one time payments. For subscriptions, that subscription object is the main object.
you can make API calls to Stripe API with the Subscription ID (example: sub_1LAY1vIypMs78IJNtxP5bPXt) and retrieve various details that is associated with that subscription.
Coding related customization is beyond the scope of this standard support forum. If you need to hire some developer time, you can contact us for a custom development job.
#1) The most common cause of this is incorrect API details for the captcha feature (if captcha was enabled). So double check the captcha documentation and verify that the correct information was entered.
#2) The 2nd most common cause is page caching. Please empty any caching on your site. You can try to exclude the page (containing the payment button) from caching.
#3) The next item to check is to make sure there is no conflict happening on this site:
Test for Plugin and Theme Conflict Before Posting an Issue or a Bug
Please post the URL of the page containing the payment button so I can see it in my browser. That can help me find some clues about the issue on your site.
This is only happening with Afterpay Clearpay payment option correct?
It is a conflict related issue. So I will need to check more setup specific data for that Afterpay addon to see if it can give me any clues as to what kind of conflict is happening on this site. I will send you an email.
Please go through the following checklist items and check them one by one to make sure all the setup is correct with the subscription related setup.
Checklist #1) Subscription plans cannot be interchanged between “live” and “test” mode.
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.
If you created a subscription plan in “test” mode, then later just changing the mode in the settings won’t be enough. The subscription plan is created in your Stripe account which doesn’t change automatically. So a NEW subscription plan needs to be created in “live” mode and then use that plan in the 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 set up. 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 the “Test Webhook Status” section.
– Click “Save Changes”.That will be due to JavaScript errors coming from another plugin or theme. Do the following test to identify the source:
Test for Plugin and Theme Conflict Before Posting an Issue or a Bug
If there is JavaScript error coming from another source, it will break the JavaScript in our plugin and cause unexpected behavior.
