#jdpy19_api
distant parcelBOT
👋 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/1363959886743994368
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
rancid condor
Hello
When you say subscribed to receive transactions, are you referring to a report of some kind?
ashen solstice
Hey, I am referring to this: https://docs.stripe.com/financial-connections/transactions#subscribe-to-transactions
transaction refreshes
distant parcelBOT
ocean granite
👋 stepping in here as hanzo needs to step away
Are you seeing this across all financial accounts?
ashen solstice
No, not all of them
ocean granite
Hmm okay and this is true of multiple transactions on the accounts that you are seeing this?
ashen solstice
The financial transaction account ID is fca_1Qnk6FITTk8cSwxgosF9Zr0w
I think this is the only one, but need to validate
ocean granite
If you could check on that that'd help narrow things down here
I think it is possilbe that the pending transaction just hasn't dropped off yet
Let me see if I can confirm that
ashen solstice
It is happening in a few other financial connections
fca_1Qnk4vITTk8cSwxgiM51J11d
fca_1Qnk6FITTk8cSwxgD5lmdXDV
fca_1Qnk6FITTk8cSwxgZxhEL0ai
fca_1Qnk6FITTk8cSwxgosF9Zr0w
``` other affected connectionsI haven't implemented any logic to deduplicate on my end yet, except for a unique index on the stripe id... I was kind of hoping that it would be taken care of on your end haha
ocean granite
I'm checking but my understanding is that this data comes straight from the banks and I don't think we de-dup on our end here as there is a concern about accidentally removing actual transactions.
When you see duplicates are all of them 1 pending and 1 active?
ashen solstice
Ahhhh bingo
Yes one is pending and one is posted
Any other statuses I should consider?
ocean granite
Not really -- the only statuses would be pending, posted or void. But I don't think you would see a duplicate with void though I guess I can't guarantee that 100%
ashen solstice
Is there a reason why these transactions do not have the same id?
IMO these are the same transaction at different stages in the lifecycle
ocean granite
Because we are just relaying what the bank provides us here.
So we don't actually know that these are the same transactions or not.
ashen solstice
Is there a webhook that I can listen to where fctxn_A is now fctxn_B?
ocean granite
No that's not how it works.
These are separate transactions on our end. Since the bank indicates there are 2 transactions.
So one never becomes the other.
If you refresh again in the future and the bank drops one of the transcations then it would no longer be present when you list transactions.
ashen solstice
Do they fall off?
ocean granite
But nothing on our end actually indicates these are duplicates.
My undestanding is that they should fall off, yes. But that is up to the bank.
ashen solstice
Okay, so I may have to change behavior to only fetch posted transactions.
Or handle logic to migrate transactions that have fallen off
ocean granite
You likely want to just refresh your transactions every so often right and update accordingly? And yeah you could either just show posted transactions or you could implement some de-duplication logic on your end (something like: if the transcations have the same amount and one is pending and one is posted within a certain timeframe (they likely should only be a few days apart) then remove one from what you show your user).