#rahul_connect-fees

1 messages · Page 1 of 1 (latest)

weak flintBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1282847201759858731

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

foggy patrol
#

yeah if you can share some kind of id and what you see I can have a look

desert merlin
#

yep, just a sec

#

acct_1PTkQ2FYcIm94Dej/payments/pi_3Pj2gJFYcIm94Dej10Qdl8JS and acct_1PTkQ2FYcIm94Dej/payments/pi_3Pw4m2FYcIm94Dej080w0rPK

Both are transactions associated with the same connected account.

foggy patrol
#

okay so what's "weird" about it exactly

desert merlin
#

The first one has "Stripe processing fees" but the second one does not. Which changes the resulting net amount of the transaction

foggy patrol
#

those payments are more than a month apart. It looks like that specific connected account negotiated a different pricing with Stripe in between where fees are taken async instead.

#

Nothing you can do or control for this in your code but they (the owner of that account) should know about this since they must have negotiated it

#

rahul_connect-fees

desert merlin
#

Oh interesting, I didn't know this was possible

#

So the fees will still be deducted from the connected account at somepoint? The platform account is not responsible for them?

foggy patrol
#

correct

#

this is usually called IC+ pricing (for Interchange+) and it's where instead of a "blended pricing" like 2.9% + $0.30, we instead pass on the fees from the card network on each transaction. But some fees are based on other things than just one payment, so it's usually assessed daily/monthly with a lag

#

since we don't have a "pricing API" though it can be really surprising when this happens
I've always asked that we clearly surface this in the Dashboard, but in theory you don't need to know that since you have negotiated it for your account. It's more confusing for platforms like yours

desert merlin
#

Give me a second, I saw other transactions where they happened to some accounts just for a small period of time. Then they went back to normal fee structure. Is that common?

foggy patrol
#

no that should be uncommon though it is possible

desert merlin
#

It's odd because it was for a short period of time, like 1 hour, where multiple of our accounts experienced this same flow.

#

Let me get some of those charges

#

Sorry this will take me a few minutes

foggy patrol
desert merlin
#

I've tried several times with them but they didn't make any progress...

foggy patrol
#

Sure but that doesn't mean it's the relevant place to ask a question in that case. And conceptually your question is really simple (with access to our internal systems) and anyone on support should be able to answer it, I'm sorry it didn't happen 😦

desert merlin
#

Yea, we have made more progress here in the first few messages than I have been able to with support after multiple times. Do you have few minutes for this or best for me to move on?

weak flintBOT
desert merlin
#

Alright, found the payments where this happened intermittently across multiple accounts.

foggy patrol
#

I can look if you have one or two examples

#

I have to run soon (and river is taking over) but I'm around so I can do that part

desert merlin
#

This was back on May 22 11:30 AM PST. /acct_1Oyxc2FWmrHoOj7c/payments/pi_3PJJvmFWmrHoOj7c0x9idMUk and acct_1OQPUfFVLr9naiHD/payments/pi_3PJK0VFVLr9naiHD1djYgHmD

#

This happened with 10 more accounts at the same time. After these transactions, these accounts went back to having their fees charged immediately.

foggy patrol
#

those happened on May 22nd. That day we had a bug with collecting fees (and should have done comms at the time)

#

but yeah that one is a bit different and was our own bug internally

desert merlin
#

Wow lol

#

Ok that's great to hear because support was insisting that our integration was wrong...

#

There were other instances that this happened as well after May 22nd. Is this a bug that comes up time to time?

foggy patrol
#

I have been here many years, I think it only happened twice (that I know of)

#

so no it's really rare and something we take seriously

#

I'm a bit annoyed that no one on support made the connection though I'm not surprised, a lot of things happen every day and it's hard to connect the dots sometimes 😦

desert merlin
#

Yea I imagine it's difficult for everyone. Sorry I was all over the place with this thread. Thanks for helping me out! I have been curious about this for months.

#

Last question if this is something you know at the top of your head. You mentioned above that there was comms about this, we don't remember receiving any, is there a particular communication channel we should subscribe to?

foggy patrol
#

It's possible we sent comms to the individual merchants in that case since they have their own Stripe account

#

But I am not involved much in how we do comms sorry

desert merlin
#

All good, have a nice rest of your week!