Forum Replies Created

Viewing 12 posts - 1 through 12 (of 12 total)
  • Author
    Posts
  • Joe
    Participant

    @FERVOUS hi Anna, can you please advise how to upgrade the Stripe plugin without deactivating & deleting, and then uploading the new v1.05. Plugins normally appear with “There is a new version available of [plugin]” and an “Update” button to upgrade the existing version. The Stripe plugin can’t be deleted and replaced because this will disconnect all the Vendors from their dashboard.

    Please advise how to upgrade the existing version?

    Joe
    Participant

    @Fervous I fixed the CSS for the Stripe payment display above.

    Joe
    Participant

    @Fervous Hi Anna, I appreciate this. I have been a lot of work on my site over the past few months to get it ready for the next phase. And if I can just get the Stripe payments working then everything will be perfect.

    I wanted to let you know that currently the live site is down: https://www.veopolis.com

    But the new dev site is almost ready, and hugely optimised: http://dev.veopolis.com/

    I will let you know when the live site is back up for you to have a look to see if you can identify the bug / conflict that is affecting multiple vendors checkout payments to go missing.

    Thanks
    Joe

    Joe
    Participant

    Have switched to Enable Test Mode in WooCommerce, and trying a test payment with multiple vendor products (all of whom were setup and connected in Live mode).

    Receive this error: “No such customer: #######; a similar object exists in live mode, but a test mode key was used to make this request.. ”

    Is there a way to test payments, or troubleshooting this.

    I’ll wait for your response to my post earlier today #67265

    Joe

    Joe
    Participant

    To update, I wondered if this Api update from Stripe would require a tweak in the plugin (screen attached)*. Api upgrades details here: https://stripe.com/docs/upgrades?since=2016-07-06#api-changelog

    Also I understand that for the redirect uris we have been told to omit ‘www.’ and use https only… which I already do… but that the Stripe Plugin documentation page needs updating as it shows an out of date screenshot. Not just the dashboard interface, but the instruction for redirect uri: https://www.wcvendors.com/wp-content/uploads/2015/07/stripe8.png

    * this has been updated but will not be responsible for the errors I have, as my errors predate this update. See first thread post above.

    Joe
    Participant

    Hi @fervous,

    further to my message above if the team has no time to dedicate to fixing the Stripe Commissions & Gateway Plugin* , and cannot/will not create a Custom Development job for my Install, then perhaps you could advise a suitable place to locate a freelancer who could troubleshoot test and fix these particular issues ? (PeoplePerhour, Guru.com, Codeable, etc).

    Please appreciate that I urgently require full functionality of this plugin… PAYMENTS are the single most critical of any marketplace or ecommerce store, and currently I have Orders failing to capture payment, either missing some products, or failing to capture the whole order! It is excruciating whilst I am trying to develop a startup marketplace venture.

    * As the Plugin authors of a $49 plugin I believe the team should be committed to maintenance upkeep and debugging of all their commercial products. So my request is not unjustified.

    Please advise at your earliest convenience.

    Cheers,
    Joe

    Joe
    Participant

    Hi @fervous,

    I have been waiting a while (over 3 months) for the Stripe issues to be looked at.

    I now am experiencing a new issue it seems, where when customers go to checkout and purchase from at least TWO vendors, then the payment just goes to Pending… there is no way to resolve.

    I have seen the Custom Development product on the WCvendors shop and wondered if I can pay for someone to custom fix this for me ? –> https://www.wcvendors.com/product/wc-vendors-custom-development/

    I would like to get this sorted once and for all. I look forward to your response

    Many thanks,
    Joe

    Joe
    Participant

    @Fervous I’ve tried above to provide as much information about these issues as possible. Looking back at the first post it seems that the WordPress and WooCommerce updates, plus WC Vendors v1.39 had something to do with Stripe going awry.

    I can confirm the below:
    • sometimes (50% of the time) orders go through without any issues… with correct commissions paid, and correct charges to customer cards
    • sometimes when a site wide Admin coupon is used this causes huge problems with admin commission rate, meaning admin receives little or no commission on sale
    • orders with 2 or more vendors are prone to more errors, including customers card being inexplicably overcharged by WC Stripe Gateway (resulting in Vendors receiving higher payments, with no consistency of amount overcharged = customer complains)
    • orders with just 1 vendor 1 product, and no coupons, seem to be 100% ok

    That’s a summary of the issues from my side. There are times when there are no problems, but a great deal of orders contain errors which is critical to the newly launched marketplace, as customers and vendors raise complaints, and lose trust in the platform. Retention is KEY to any business, especially online marketplaces where we need to prevent disintermediation from customers and vendors.

    I would like this to be addressed with urgency. A staging environment with a Test Admin, and 3 Test Vendors should be straightforward enough to setup, and make a number of different Test Sales (with & w/o coupons, single vendor, multi vendors), to recreate errors, debug and see what is happening with each transaction- mapping endpoints from WooCom, to WC Vendors, to WC Stripe Gateway.

    If time and resource is an issue perhaps this is something that could be outsourced? Get a cheap but comprehensive debug report (e.g. from Peopleperhour). They have v talented programmers around the world working for just $12-15 an hour who could get to the bottom of this within a day rate.

    Just an idea, because I believe this is a relatively straightforward issue to solve, to get the Stripe Gateway cleaned up and fixed- but from the above thread it doesn’t look like it is getting properly looked at yet. Hence the advantage of outsourcing the menial time-consuming tasks to produce a debug report, to see what needs fixing, patch up the bugs and release new fixed update.

    Joe

    Joe
    Participant

    @PIPCAMBERS if you’re in USA then you can just use Paypal to receive payments to Admin. Then pay vendors via Mass Payments. This is the easiest workaround whilst Stripe is not working (*Mass Payments doesn’t work outside of USA as Mass Pay does not come enabled for Paypal accounts).

    @Ben I understand that you do not test 3rd party plugins for compatibility with WCV but Pip only asked about other payment options because ‘Stripe Commissions & Gateway’ is not working as sold. A paid plugin should have regular updates and bug fixes- but I notice that in the latest update 1.03 from 22nd March that (* Fixed: Commissions Paid to Admin wrong #12 ) is still not the case.

    Additionally, traditional user Debug testing cannot take place with ‘Stripe Commissions & Gateway’ plugin, as it requires minimum of 2 live vendor accounts plus Admin to recreate the same test environment. I’ve reported this issue for over 3 months now and nothing has been resolved, hence the frustration from myself and others.

    Joe
    Participant

    Hi @Fervous,

    yes I can confirm that the Stripe are still inaccurate, continuing to overcharge customers (as compared to the actual total in WooCommerce), and it is very difficult to see why it behaves the way it does as it changes each time… ** it ONLY occurs when there are 2 or more vendors in the Order! It does NOT occur with single vendor orders! **

    To illustrate, I have documented a recent order, using a 10% coupon –

    1. The order as seen in WOOCOMMERCE (what the CUSTOMER sees and expects to pay)

    ORDER for 5 items from 2 vendors, with a 10% coupon:
    • Vendor 1: 1 item = £15 (minus 10%) = £13.50
    • Vendor 2: 4 items = £13.80 (minus 10%) = £12.44 (+ shipping: £11.80) = £24.24
    ________________
    CUSTOMER TOTAL: £37.72

    >>

    2. The order as seen in STRIPE CONNECT (what the VENDOR sees and receives, and what customer actually pays)

    • Vendor 1: correctly received = £10.84
    Sale of 1 item = £15, less fees:
    – minus 15% commission (£2.25)
    – minus 10% coupon (£1.50)
    – minus Stripe fees (£0.41)
    = £10.86

    Customer charged to card / vendor received = £10.86 ** correct **
    _________

    • Vendor 2: INCORRECTLY received = £28.64 [customer overcharged by £4.40 to the order]
    Sale of 4 items = £13.80, less fees:
    – minus 15% commission (SHOULD BE £2.07, but Stripe only charged £0.57 = 4% commission!)
    – minus 10% coupon (£1.38)
    + shipping (13.80)
    – minus Stripe fees (£0.60)

    SHOULD BE = £24.24

    BUT customer overcharged £4.40 = £28.64

    Customer charged / vendor received = £28.64 ** incorrect **

    ________________

    SUMMARY

    If all that looks confusing, it’s because it is! This is why the Stripe Gateway plugin is supposed to do it all for us, by correctly communicating between WooCommerce, WC Vendors and Stripe Gateway for correct payments and commissions.

    ________________

    To summarise the above for clarity:

    1. A shopper being overcharged by £4.40 (where is this extra superfluous charge coming from?!)

    2. Marketplace not receiving proper commissions (receiving 4% from Vendor 2, rather than 15% as set in WC Vendors Pro)

    3. Complaints raised by customer and Vendor for why the payments are wrong

    ________________

    I included full details and breakdown of how the Order appeared, on both WooCommerce and in Stripe, so to give the full picture in hope to resolve.

    The concern here is whether the issue is with WCV Pro or the Stripe Gateway plugin?

    Somewhere in the chain (WooCommerce > WCV Pro > Stripe Connect) the payment charges and commissions are getting horribly mixed up.

    Please advise.

    Joe

    in reply to: 1.4 Update Notification #57838
    Joe
    Participant

    hi @MAXX I’d have to reiterate the accurate point made by @NOFSKI . V1.4 was originally proposed to arrive before Christmas, and has been continuously pushed back. As of Anna’s update (found just 4 posts above this one) there is no expected release date, or Beta versions available and we are now in March – so I wouldn’t hold your breath. Currently there are 2 projects being worked on that we know of:

    – “Jamie is working hard to make sure we are all set for the new WooCommerce 2.7 at the moment so we are compatible and everyone’s site does not implode…”
    – and see the Stripe Gateway plugin support page, to see that the plugin has some critical errors that are also still yet to be addressed

    So there’s every likelihood that it will be summer before v1.4 emerges

    Joe
    Participant

    Hi @fervous

    It’s the same user Joe from above. I’ve had to create a new WC forums account.

    Further to the above from 2 weeks it seems the critical Stripe issue isn’t getting looked at.

    This is ongoing issue and has even created another more puzzling error today. An order of £32 (for 3 items from 2 Vendors), has been billed to the customer incorrectly.

    Order is: £32 with a 10% coupon = £28.80. Which is what showed in WooCommerce.

    Firstly, the coupon was not applied in the Stripe payment causing the customer to get charged without coupon % discount.

    Secondly, Stripe did not calculate the admin commission from the Vendor either, using 10% rather than the global set 15% (this is global in the admin dashboard, and there are no individual vendor commissions set).

    So the Customer is getting charged too much, and the Admin isn’t getting the set fee rate.

    At this stage I am only advising for your info, as I haven’t heard anything on the above.

    It was advised that lead programmer Jamie is working on the WooCom 2.7 update “to ensure everyone’s site doesn’t implode” so I’m not sure when this new issue can be looked at?

    As you can see it would appear that the Stripe Gateway plugin is not communicating the correct information from WooCommerce (or WCVendors commission rates), resulting in incorrect billing to customers.

    What can you advise at this stage?

    Regards
    Joe

Viewing 12 posts - 1 through 12 (of 12 total)