#tomirons

1 messages · Page 1 of 1 (latest)

jade oysterBOT
junior sedge
#

Can you share some object IDs please

worn cairn
#

Sure!
Posted: fctxn_1MydvqA2s8WwMUPtDdS4lyTk
Void: fctxn_1MxYS6A2s8WwMUPtZNViMKUj

jade oysterBOT
open radish
#

to say it upfront, unfortunately we know very little about FC here, it never really comes up in this timezone so folks around right now have never really touched it.

I'm not completely following the question. What flow are you using with FC, which docs? When you say get this resolved, what is the problem exactly and what sort of resolution are you envisioning?

worn cairn
#

Ah, I hope someone who jumps on later might have some more insight.

I've used the docs related to FC transactions. When a user connects an account we subscribe said account to transactions which means every day Stripe will send us a webhook that indicated a refresh has happened. At that point we then fetch the newly created/updated transactions and store them in our database. However, this is where it gets funky. Since the object IDs from stripe are unique, I check if it already exists and will update it if so, or it creates the new transaction if it does not. For the resolution, I'd like to not have duplicate transactions (one posted, one void) for every transaction a user makes. This is going to fill up my database pretty quickly.

open radish
#

I hope someone who jumps on later might have some more insight.
I would suggest writing to https://support.stripe.com/?contact=true instead really, since you're asking a specific question about a livemode transaction and really our team barely interacts with this part of the API so I don't think you'll find a SME here
I've used the docs related to FC transactions
which docs exactly? do you have a link?
For the resolution, I'd like to not have duplicate transactions (one posted, one void) for every transaction a user makes
that sounds more like a feature request that we change how the system itself works? Better to raise that through support or your account manager etc if you have one.

I know very little about this but it's common in banking that merchants do things like authorise a transaction, and then release the authorisation immediately(that's what Stripe and other payment processors do when validating cards) so having a transaction->void seems, to me with my no context, like maybe reasonable

worn cairn
open radish
#

I see

#

but yeah like fundamentally, we're just giving you the transactions that we get from the end-user's bank account, right? I doubt we control the fact that there are cases of transactions being voided like this so I'm not clear what I can really suggest? Maybe I don't understand it, but you can connect with our support team to work on this and give feedback to the product team

worn cairn
#

I'll try to gather more data on when this started happening. If it started from the very beginning then maybe that's the way is supposed to work.

#

I appreciate you helping out!

jade oysterBOT