- This topic has 21 replies, 6 voices, and was last updated 5 years, 8 months ago by
.
-
Posts
-
The new version of the Stripe payments plugin (v2.x.x) has the SCA compliant API. You can enable the new API by going to the Advanced Settings menu of the plugin then unchecking the “Enable Legacy Checkout API” checkbox.
Over the next few days we will continue work on this new checkout API to make sure all reported bugs are addressed.
You can reply to this topic to report a bug. You can also contact us using the contact form to report a bug.
You can also download the legacy version of the plugin from the following page (just in case you want to continue to use that old one for now):
Addons
We are working on converting all the addons to be compatible with the new API. The following addons are already compatible with the new API.
- Subscription Payments
- AWeber Integration
- ConvertKit Integration
- MailChimp Integration
- Custom Messages
- Additional Custom Fields
- Additional Payment Methods (version 2.0.0; requires Stripe Payments version 2.0.8+).
- reCAPTCHA (version 2.0.0; requires Stripe Payments version 2.0.8+).
- Alipay (version 2.0.0; requires Stripe Payments version 2.0.10+).
- SOFORT (version 2.0.0; requires Stripe Payments version 2.0.10+).
List of Bugs for the New API
The following post has a list of bugs that we are currently aware of and working on it.
Reported Bugs
Currently we are aware of the following bugs and working on them:
#1) [Fixed] Getting the following error when Checking out with shipping address enabled for a product:
Received unknown parameter: shipping[email]
This error is triggered when the “Collect Both Billing And Shipping Addresses” is enabled.
#2) [Fixed] “customer_email” tag not working.
#3) [Fixed] The payment window not scrolling correctly in mobile devices.In the popup, the bottom is cut off. The top of what I assume to be the submit button shows, but that is all.
@nancywhite59, We have just released another version that should fix the issue you explained.
With the new API I’m getting an error message on payments, even though the payment has been processed correctly (Had to check in Stripe as no email confirmation was sent):
“The site is experiencing technical difficulties”
I’ve tried in test mode – original API works fine. Any idea’s!?
On the original API the Expiry date and CVC are on a different line – on my phone the credic ard number dissappears and only shows last four digits when i move to enter the expiry date. im sure this will cause confusion for payees. Is it possible for the Expiry and CVC to be on a new line underneath as before (I think it was clearer for customers on previous form)
Thanks!
Do you see any error in the error log file of the site?
That new form (where the CVC and expiry fields are) is controlled by Stripe. I also like the previous form but in this new API this is what they offer.
Hi,
Log below during the payment, The thing is, is does get processed – the payment earlier went through, but it’s sending them to an error page afterwards.
(I’ll get on to stripe about the form!)
[09/11/2019 3:42:32 PM] – [Sub] Received webhook type which doesn’t need to be processed: payment_intent.created
[09/11/2019 3:42:34 PM] – [Sub] Received webhook type which doesn’t need to be processed: charge.succeeded
[09/11/2019 3:42:34 PM] – [Sub] Received webhook type which doesn’t need to be processed: payment_intent.succeeded
[09/11/2019 3:42:34 PM] – Payment processing started.
[09/11/2019 3:42:34 PM] – Got product ID: 293030
[09/11/2019 3:42:34 PM] – Firing asp_ng_process_ipn_product_item_override filter.
[09/11/2019 3:42:34 PM] – Firing asp_ng_process_ipn_payment_data_item_override filter.
[09/11/2019 3:42:35 PM] – Coupon is invalid for the product.
[09/11/2019 3:42:35 PM] – Constructing checkout result and order data.
[09/11/2019 3:42:35 PM] – Firing asp_ng_payment_completed filter.
[09/11/2019 3:42:35 PM] – Firing asp_ng_handle_metadata filter.
[09/11/2019 3:42:35 PM] – Updating payment metadata.
[09/11/2019 3:42:35 PM] – Firing asp_ng_payment_completed_update_pi filter.
[09/11/2019 3:42:35 PM] – Updating payment intent data.“The site is experiencing technical difficulties”
clubvipplus, this means PHP fatal error has occurred. Can you have a look at your server error log to see if there’s any info available there? Also, which PHP version are you using?
When I enable the new api (disable “Enable Legacy Checkout API”) I get this error after making a payment:
I get a message saying “Websitet oplever tekniske problemer.” (danish) translates to “The site is experiencing technical problems.”
In the Log I see the following:
[09/13/2019 8:43:17 AM] – [Sub] Received webhook type which doesn’t need to be processed: payment_intent.created
[09/13/2019 8:43:19 AM] – Payment processing started.
[09/13/2019 8:43:19 AM] – Got product ID: 2382
[09/13/2019 8:43:19 AM] – Firing asp_ng_process_ipn_product_item_override filter.
[09/13/2019 8:43:19 AM] – Firing asp_ng_process_ipn_payment_data_item_override filter.
[09/13/2019 8:43:20 AM] – Coupon is invalid for the product.
[09/13/2019 8:43:20 AM] – Constructing checkout result and order data.
[09/13/2019 8:43:20 AM] – Firing asp_ng_payment_completed filter.
[09/13/2019 8:43:20 AM] – Firing asp_ng_handle_metadata filter.
[09/13/2019 8:43:20 AM] – Updating payment metadata.
[09/13/2019 8:43:20 AM] – Firing asp_ng_payment_completed_update_pi filter.
[09/13/2019 8:43:20 AM] – Updating payment intent data.
[09/13/2019 8:43:20 AM] – [Sub] Received webhook type which doesn’t need to be processed: payment_intent.succeeded
[09/13/2019 8:43:20 AM] – [Sub] Received webhook type which doesn’t need to be processed: charge.succeededApologies for delay on getting this – took a while to access the server logs! Ive edited out main folder name with ‘-‘
[11-Sep-2019 15:42:35 UTC] PHP Fatal error: Uncaught Error: Call to a member function get_year_permastruct() on null in /home3/-/public_html/wp-includes/link-template.php:475
Stack trace:
#0 /home3/-/public_html/wp-content/mu-plugins/endurance-page-cache.php(408): get_year_link(‘2019’)
#1 /home3/-/public_html/wp-includes/class-wp-hook.php(288): Endurance_Page_Cache->save_post(383640)
#2 /home3/-/public_html/wp-includes/class-wp-hook.php(310): WP_Hook->apply_filters(NULL, Array)
#3 /home3/-/public_html/wp-includes/plugin.php(465): WP_Hook->do_action(Array)
#4 /home3/-/public_html/wp-includes/post.php(3951): do_action(‘save_post’, 383640, Object(WP_Post), false)
#5 /home3/-/public_html/wp-content/plugins/stripe-payments/admin/includes/class-order.php(163): wp_insert_post(Array)
#6 /home3/-/public_html/wp-content/plugins/stripe-payments/includes/class-asp-process-ipn-ng.php(374): ASPOrder->insert(Array, Object(Stripe\Charge))
#7 /home3/-/public_html/wp-includes/class-wp-hook.php(286): ASP_Proc in /home3/-/public_html/wp-includes/link-template.php on line 475Thank you for PHP error log. Though I haven’t been able to reproduce the issue on my test server, I think I understand where it’s coming from.
I have just released new testing version (2.0.7t1) which should hopefully fix the issue. Please get it here https://s-plugins.com/testing-version/ and see if it resolves your issue.
@kristoffertrolle, please do the same as it seems that you’re having the same issue as @clubvipplus.
- You must be logged in to reply to this topic.