TLN

Forum Replies Created

Viewing 15 posts - 31 through 45 (of 52 total)
  • Author
    Posts

  • TLN
    Buyer
    Post count: 131
    This reply has been marked as private.
    in reply to: Customer claims he's been billed twice #3053

    TLN
    Buyer
    Post count: 131
    This reply has been marked as private.

    TLN
    Buyer
    Post count: 131
    This reply has been marked as private.
    in reply to: Customer claims he's been billed twice #3050

    TLN
    Buyer
    Post count: 131

    Hi Patrik,

    Is there any documentation on how you guys use the Stripe Webhook? Do I need to listen for all events? (Stripe does not recommend this).

    Also, are you fully compatible with Stripe’s latest API (2019-03-14)) ? When I upgraded to it from 2017-12-14, all new signups who checked out were sent a paid “renewal” invoice after they paid for their invoice. In other words, they have the original invoice and a paid “renewal” invoice. This is causing them to think they made two payments, instead of just one. This has happened with all sign ups since we switched to the new API and added the webhook to Stripe settings. I’m trying to isolate the issue, but I assume the cause is one or the other (these were the only two changes we made, and then everyone started seeing a duplicate invoice).

    The reason I updated to the latest API version is because we were having trouble paying using discount codes, so I thought maybe it was a problem with the version of Stripe we were using. Instead, it turned out that there’s an issue when someone pays for a listing and they already have a paid listing under the same price plan (another issue, but probably unrelated).

    At this point, I’m assuming that the double-invoice issue has to do with either the API, or with the Webhooks. If you could provide more info on both of these I’d appreciate it.

    Thanks.


    TLN
    Buyer
    Post count: 131

    So upon checking, it looks like this only will affect the same user, if they try to buy another listing and choose the same paid plan, and use the same discount code. It does not affect first-time users, even if they use the same discount code.


    TLN
    Buyer
    Post count: 131

    Hi Patrik,

    Thank you very much for your reply. Here are the steps that can help you replicate the issue:

    1) Sign in as a front-end user and submit a paid listing
    2) Use a discount code at checkout
    3) Pay using Stripe (I have only tried this in Test Mode)
    [this should work fine]
    4) Try to create another paid listing (a new one)
    5) Use the same discount code that you used before

    If my theory is correct, then the first time you check out it will work just fine. However, if you decide to create another listing, it will fail with the error mentioned.

    Please note that I have not had any issues with anyone signing up and getting this error message. However, I have not started using discount codes yet (so I don’t know whether this will affect others). Perhaps the issue is related only to the test environment. Perhaps it only affects the SAME user trying to buy another listing with the same discount code, which will likely never happen so it’s not a big deal. In any case, I just need to be sure that it will not be a problem to use discount codes.

    Thanks very much guys!


    TLN
    Buyer
    Post count: 131

    Here’s an update on this issue.

    I thought this was resolved, since I had gone on Stripe and deleted all my test data. It seemed to have fixed it. However, I started testing the checkout process again and noticed that you can only pay successfully the first time you use a discount code. If you later on decide to buy another listing, and use a discount code again…. it will fail. Only once I delete the Stripe data does it work again.

    If this only happens in test mode fine, no problem. But how can I know that this won’t happen after the first person uses a coupon? Will every one else experience a problem after that?

    I’m including screenshot from Stripe with the log and error code. Apparently, the plugin keeps trying to create the same product/item even though it already exists? Do I have that right?

    Thanks for all the help guys.

    in reply to: Customer claims he's been billed twice #3037

    TLN
    Buyer
    Post count: 131

    Hi Paolo. Thanks for your reply.

    So we did a little digging on our end, and here’s what we found:

    Customers who navigate away from the checkout page (for example, to view the Terms and Conditions) and go back to the checkout page (from the listing form) are generating a new invoice. Then, when they pay for the invoice (a single payment) it looks like both the original invoice and the second “renewal” invoice are being marked as paid.

    I am unable to provide access to the site at the moment because we are getting ready to launch.

    Hope that helps.

    in reply to: Deleting a user does not delete their subscriptions #3032

    TLN
    Buyer
    Post count: 131

    Thanks Guust. I appreciate the reply.


    TLN
    Buyer
    Post count: 131

    This was due to the same item/product appearing twice in my Stripe account under test mode. I removed the additional product and it all works fine now. I’m able to use discounts without issue.

    in reply to: Hooking into invoice paid #3023

    TLN
    Buyer
    Post count: 131

    Here’s my code in case any one else needs to know when an invoice is first created. This will fire on creation:

    function on_invoice_created( $post_id, $post, $update ) {

    $author_id=$post->post_author;

    $updated = ($update) ? “updated” : “saved”;

    if ($post->post_type == ‘wpi_invoice’) {

    if ($updated==’saved’) {

    $invoice = wpinv_get_invoice($post_id);
    $invoice_total = $invoice->get_total();
    $invoice_id = $post_id

    // do some stuff here

    }

    }

    add_action( ‘save_post_wpi_invoice’, ‘on_invoice_created’, 10, 3 );

    in reply to: Hooking into invoice paid #3022

    TLN
    Buyer
    Post count: 131
    This reply has been marked as private.
    in reply to: Hooking into invoice paid #3020

    TLN
    Buyer
    Post count: 131

    Ok, so this mostly works, except that it does not get triggered when an invoice is created for the first time from the front end.

    How could i hook to a pending invoice that was just created for a user and is pending payment?

    I tried this but it does not work for me:

    function invoice_status_update($invoice_id, $new_status, $old_status ) {

    if ($new_status == ‘wpi-pending’ && $old_status != ‘wpi-pending’) {
    // nothing happens when the invoice is created from the front end and set to “Payment Pending”
    }

    }
    add_action( ‘wpinv_update_status’, ‘invoice_status_update’, 10, 3 );


    TLN
    Buyer
    Post count: 131

    Actually, it seems to be an issue whenever i use any discount code (even if there is a total left on the invoice).

    in reply to: Hooking into invoice paid #3015

    TLN
    Buyer
    Post count: 131

    Thank you! This works perfectly.

Viewing 15 posts - 31 through 45 (of 52 total)