We’re not using custom code – too scared 🙂

product does not have a commission override, neither does the vendor – they’re using the global rate of 100% (which is working for other vendors)

We used a WCV-Pro coupon on the sale, but I tested that on a different vendor too, and it worked fine there.

There’s absolutely no reason why it would send all the commission my way, but it did. Now I’m worried it’ll happen for every sale from this vendor, as multiple manual bank transfers are not on the top 10 of my favorite things 🙂

So, just confirming something here – if a vendor is using global commission rate – their commission dropdown field is supposed to be *empty*, right?

The admin side commission log says the commission is *paid*. Not to who or what split it made.
It also has the gross amount listed, without the coupon subtracted.

When I impersonate the vendor in question, the pro dashboard tells her the commission was paid to *her*
That’s lying and could get me into trouble 🙂
The amount listed in the Pro dashboard for the vendor is also just wrong by all counts. It’s not the full payment, it’s not the full payment minus the coupon, and it’s not minus stripe fees either. It’s kinda close to the right number.

The real data is as follows:
Received to my stripe account: 1497.00 DKK
Vendor’s Pro dashboard says: 1437.60 DKK (dashboard/)
Admin side commissions list says: 1737.00 DKK (wp-admin/admin.php?page=pv_admin_commissions)
Woocommerce order total says: 1497.00 DKK

Any more numbers that would be interesting? Do you calculate VAT manually for display in the pro dash for vendors or something, since it’s slightly off? And what about the admin side commissions list, that’s also off?

The main question is of course still the payment split that went 100% to the wrong person, but there are other things not adding up..

Actually… Even if we’d set the vendor commission to 0%

They should still be seeing the charge in their account but with an application fee of 100%. In this case, the transfer went *directly* to my own stripe account, the vendor account was not involved at all.. Why would the stripe gateway do that? Just post directly to the stripe-connect main account? It should *never* do that..?

Hey @jamie – more info from stripe support

Thanks for getting back to me with those details.

I’ve been looking over your account and the charge in question. From what I can see, it appears that when charge was created, the incorrect API keys were used, which is why the charge was created on your account.

You mentioned that you’ve been having trouble with your plugin recently. I can see that this charge was made using our PHP library and some of the older charges that were made on the connected account, were made using our Java library. This suggests to me that these charges were made using two different sources. If you’ve changed plugin recently, I’d recommend reaching out to them to check that they have the correct API keys configured for both your account and your connected accounts.

Hopefully this helps to shed some light on the situation. If there’s anything I can help you with regarding this or anything else Stripe related, shoot me a quick email and I’ll be happy to help.

Hopefully that’s useful information. Sounds very odd.

It would, except subsequent and previous purchases have worked without error.

Oh FFS…

So the issue is suddenly clear, thanks to you @fervous – you made me go back and check the basics.

For some reason, the plugin has “forgotten” that our accounts are connected.

In Stripe dashboard, the accounts are still connected (and I have full edit access), but in the plugin they somehow are not any longer.

Can I manually repair that in the DB @ben?

It’s not 1.2 – I’m waiting til it’s safe 🙂

I’ll try finding the user meta thing Ben, thanks! I’ll report back if I’m too nooby 🙂

Question – the keys are stored as plain text in the DB. Should they not be stored encrypted? I mean they do allow write access to someone’s Stripe account, right?

Aight, thanks for that useful bit of info 🙂

It looks like the issue is this:

The vendor already has a stripe account – the account is already connected to ours – the plugin doesn’t agree with that – and we can’t connect the vendor (in the plugin) using the connect button.

I’m not sure exactly where the process skips out – *but* this vendor had a stripe account prior to signing up with us, that might have something to do with all this, yeah? That’s the only difference between this vendor and others.

I understand that it’s hard to repro, truly, but I don’t know what the vendor *did* to have this happen. I have no idea if it was the vendor that created an error – or if the plugin coughed something up all by itself.

Whatever they did, they managed to connect our stripe accounts, but *only* in stripe. The plugin doesn’t have a client id for this vendor – there’s not even an entry in the DB for it (the token you get back from stripe).