• Resolved SethTurin

    (@sethturin)


    I’ve done some searching and it looks like there are a lot of issues with this, and none of them have clear resolutions. I’m using paypal for both paypal payments and credit cards. I have some subscriptions products. some of the subscriptions renew fine with no issue. others just say “Payment Pending” and give no other information.

    So I looked in the debug logs, and I saw this:
    Response Body: {“name”:”INVALID_REQUEST”,”message”:”Request is not well-formed, syntactically incorrect, or violates schema.”,”debug_id”:”xxxxxxxx”,”details”:[{“field”:”customer_id”,”value”:””,”location”:”query”,”issue”:”INVALID_STRING_LENGTH”,”description”:”the value of a field is either too short or too long.”},{“field”:”customer_id”,”value”:””,”location”:”query”,”issue”:”INVALID_PARAMETER_SYNTAX”,”description”:”the value of a field does not conform to the expected format.”}],”links”:[]}

    note: I removed the debug id because I don’t know what it is. the rest of the data is copied directly.

    so I did some sleuthing and I found that in the customers that aren’t getting charged subscription renewals, the _ppcp_target_customer_id?meta value isn’t getting recorded.

    There is already a github issue on this that someone posted 2 weeks ago, but there haven’t been any responses. since this is affecting our ability to take money, this is an urgent issue, and it sounds like it is affecting a lot of people.

    If there is any workaround, please let me know.

Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Support Krystian

    (@inpsydekrystian)

    Hi @sethturin

    Thank you for reaching out.

    The problem you’re describing is one we’re aware of, and it has already been patched. The issue stemmed from a bug in version 2.8.2 of our PayPal Payments plugin, which caused the customer_id to become corrupted for certain orders. This seems to be affecting your transaction, and unfortunately, it’s unlikely that the failed payment or the original order details can be recovered.

    The best option in this case is for the buyer to repurchase the subscription.

    We’ve already fixed this issue, and it should not occur again. While it hasn’t impacted a large number of users—so far, we’ve had 9 reported cases—it’s definitely something we take seriously.

    Let us know if you need any further assistance, and we’ll be happy to help.

    Kind Regards,

    Krystian

    Thread Starter SethTurin

    (@sethturin)

    Thanks for the quick response. Support here actually seems pretty good and I don’t know why you guys get so much grief from people.

    So just to clarify – is the patch already released? And if so, which version? I’m currently running 2.9.0.

    • This reply was modified 5 months, 2 weeks ago by SethTurin.
    Plugin Support Krystian

    (@inpsydekrystian)

    Hello @sethturin

    Thank you for the kind feedback. We really appreciate it!

    To clarify, 2.9.0 is bug-free, and 2.8.2 is the only affected version. Unfortunately, for any subscriptions that were affected before the update, there’s no way to retroactively fix them.

    Kind Regards,

    Krystian

    Thread Starter SethTurin

    (@sethturin)

    Ok, then I can sadly confirm that the issue is not fixed, since I had 2.9.0 when the faulty subscriptions were ordered.

    How can I help get this solved quickly?

    Plugin Support Krystian

    (@inpsydekrystian)

    Hello @sethturin

    I recommend contacting our support team directly. You can reach us by following this link.

    Our team will likely need to review the entire log to diagnose the issue, and I understand you may not want to share that information publicly here.

    Kind Regards,
    Krystian

    Thread Starter SethTurin

    (@sethturin)

    Hi again.

    I’ve found the cause of the issue. For me, this is happening because of the way woocommerce paypal payments (I’ll abbreviate WPP) interacts with another plugin – CartFlows. From what I can tell, the fix will have to come from the WPP side. Let me explain.

    For the credit card form, WPP has a checkbox that says “save to account”. When the product is a subscription, this checkbox is not clickable, and is checked by default for subscription products. Furthermore, this checkbox must be checked for it to save the info necessary for the subscription.

    The reason that last part matters is because cartflows has a feature that allows customers to choose between different products directly from the checkout page, and then dynamically updates the checkout page and the cart with the new product.

    When that dynamic update happens, the checkbox (which is rendered by the WPP plugin) does not update. So in the specific situation where a customer switches between a normal product and a subscription product, as is my situation, the necessary checked-and-unchangeable checkbox is never rendered. Because the necessary checkbox isn’t rendered, it doesn’t save the customer information, needed for the subscriptions to work.

    This fix must be on the WPP side, because cartflows has no knowledge of which payment plugin a site is using, but WPP can surely detect if there’s been dynamic updates to the products in the cart. Essentially, WPP just needs to update and re-render if there are any dynamic changes to the cart/checkout.

    Note: This issue also affects the rendering of the “Place order”, for which WPP and cartflows fight for control. I fixed this issue myself by writing some custom javascript to make them play nicely. but it’s potentially also worth looking into on your side. Again, it could be solved by re-rendering upon any dynamic changes.

    Please pass this on to the developers, and let me know if I can explain anything more clearly for them.

    Also, can you tell me any kind of timeline for when this could be fixed?

    Plugin Support Krystian

    (@inpsydekrystian)

    Hello @sethturin

    Thank you for providing such a detailed explanation.

    First, I’ll need to reproduce the issue on my end to ensure I fully understand how the behavior is occurring. Right now, I’m not fully convinced without taking a deeper look at it, but your description makes sense. I’ll go ahead and create an issue for this, and I will make it a priority to try reproducing the issue today.

    Once I have a better understanding of what’s going on, I’ll update you with my findings and provide any additional information regarding the next steps.

    As for the timeline typically, fixes depend on the complexity of the issue, but I’ll aim to keep you informed as things progress.

    Thank you again for your patience and for pointing this out.

    Kind Regards,

    Krystian

    Plugin Support Krystian

    (@inpsydekrystian)

    Hello @sethturin

    I haven’t been able to reproduce this issue myself, as CartFlows is a freemium plugin, which complicates testing on our end. That said, I will raise this with our product owner, but it’s important to note that since CartFlows is a freemium product, the fix will most likely need to come from their side. Our plugin is officially compatible with default WooCommerce themes and plugins, and typically, it’s the responsibility of third-party developers (especially for paid plugins) to ensure compatibility with our plugin, rather than the other way around.

    I will continue to research this further, including looking into reports from other users to see if they were also using CartFlows. If necessary, we can reach out directly to the CartFlows development team.

    Thank you again for bringing this to our attention, and I’ll keep you updated on any progress.

    Kind Regards,

    Krystian

    Hi @Krystian from Syde,

    Reporting this bug hit our client’s website hard ??. Due to the dynamic nature of the subscriptions on the website in question, there’s no simple way for the customer to simply ‘repurchase the subscription’.

    Is there really no way to recover the customer_id (using the paypal API for example)?

    If you truly “take this seriously”, please take some time to address the github issue, the silence over there speaks volumes.

    https://github.com/woocommerce/woocommerce-paypal-payments/issues/2587

    Plugin Support Krystian

    (@inpsydekrystian)

    Hello @perrelet

    We’ll be happy to help, but please open a new thread for your issue, as we prefer to support each case individually.

    Alternatively, feel free to contact us directly for further assistance. To open a ticket with our service desk, you can request support here: Request Support. Please include the URL of this thread in your ticket for reference.

    Kind Regards,

    Krystian

Viewing 10 replies - 1 through 10 (of 10 total)
  • You must be logged in to reply to this topic.