#tomb_05414
winged phoenix
alpine silo
Hi there!
Have you read this page? https://stripe.com/docs/connect/manage-payout-schedule
clever sparrow
Yeah we have. Just asked one of our team but apparently doesn't work for us. Sorry just getting real time feedback from my team on this. Looks like someone on your side needs to make the change for us as it was manually approved we could have T+1 in place. Support aren't responding to our tickets so not sure how to fix
alpine silo
Just asked one of our team but apparently doesn't work for us.
Can you clarify why?
Looks like someone on your side needs to make the change for us as it was manually approved we could have T+1 in place.
Then you need to ask Stripe Support for this, here on Discord we can't help. https://support.stripe.com/contact
clever sparrow
You may be able to help with the bigger issue though. The above is actually a temp fix we want to put in place to resolve a wider problem. We have duplicate payments being accepted by Stripe which means our Customers are being charged twice and Connected accounts are being paid out twice. Our platform only allows 1 payment per unique transaction and we have checked our logs which absolutely make sure we don't allow a user to trigger payment multiple times. We have raised with support but no response. Definitely a tech issue but where to start?
Essentially we have 2 payment IDs so duplicate payment associated with the same unique purchase of a product on our platform.
alpine silo
Can you share two PaymentIntent ID (pi_xxx) that you think are duplicate of one another?
clever sparrow
hang on, will send as text
py_3NuD4SH2do8Xf8cz0i8SHKJ2
py_3NuBGxH2do8Xf8cz0TvuMuEp
Sorry the actual payment ID are ...
pi_3NuD4SH2do8Xf8cz0x9w50mU
pi_3NuBGxH2do8Xf8cz0MsPnL3V
alpine silo
py_3NuD4SH2do8Xf8cz0i8SHKJ2 was created by this request: https://dashboard.stripe.com/logs/req_N8nDkEfVvo7Zj2
py_3NuBGxH2do8Xf8cz0TvuMuEp was created by this request: https://dashboard.stripe.com/logs/req_bTd1tsQdPrxBln
As you can see, your code sent two request to Stripe, so Stripe created 2 PaymentIntents as expected.
So form Stripe's point of view everything worked as expected. If that's not expected, no need to check your integration to understand why you created two different PaymentIntents here.
clever sparrow
ok thanks