#theddev_unexpected
1 messages ยท Page 1 of 1 (latest)
๐ 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/1349052591455338629
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- theddev_unexpected, 3 days ago, 63 messages
as per our previous discussion we thought that transfer is not geeting associated because the application fee being > than the amount.
but I tested a payment yesterday with same amount and it did have transafer
Hi! What's the request ID thta returned that error?
here is the one I tested yesterday: pi_3R19wgIJwkxnVmNV0bpPOq9D
and here is the one which doesn't have transfer: pi_3QwqyEDfcmTYbu9Y2WYPHdxC
this is one of the request id where the customer tried refunding req_TonQNVb057poZm
Right. Is there a reason you're using the py_ ID instead of the Payment Intent ID?
I dont remember now, but we are working to use pi as per our last conversation but we wanted to solve the mystery of why transfer was not created
so that we can make sure if there is anything from our side we can do to avoid that in future.
pi_3QwqyEDfcmTYbu9Y2WYPHdxC does have a transfer though.
that is strange because the error message says: Cannot reverse transfer on charge py_3QwqyEDfcmTYbu9Y2wvTe6f6 because it does not have an associated transfer.
but also there is no transfer mentioned on stripe also.
for the other one(pi_3R19wgIJwkxnVmNV0bpPOq9D), I can see the transfers:
and I was able to refund this paymen pi_3R19wgIJwkxnVmNV0bpPOq9D (test one) using the charge id (py) and not pi.
here is the request for that: req_5AAiJnR04XdBKk
That failed request to refund py_3QwqyEDfcmTYbu9Y2wvTe6f6 failed because that was associated with pi_3QwqyEDfcmTYbu9Y2WYPHdxC which is one where the application fee is higher than the charge amount so it has no transfer.
yes true but the other one also has same, the application fee is higher than the amount. and yet, we were able to refund.
This is related to the beta you're in, right? ๐
I am not sure about being in Beta.
where do i check that?
Or maybe it was and it isn't anymore, never mind. ๐
I don't know why one of those created a transfer and one did not.
yeah same my friend, same..
so what should be our conclusion on this one?
Share me your Chicken Wisdom sir ๐
Haha
The successful one had refund_application_fee: "true", and the failed one had refund_application_fee: "false",
true -> succeeded: https://dashboard.stripe.com/test/logs/req_5AAiJnR04XdBKk
false -> failed: https://dashboard.stripe.com/logs/req_c8NeHrynlT38XW
interesting.. let me try something
hello sir, tried refunding a new payment with "refund_application_fee": "false" and it worked.
here is the request Id: req_LbrRm0Rhas7FUa
fyi i'm taking over for timebox on this thread, catching up now
okay sir.
ok sorry about the delay, was wrapping some other threads up. focusing on this one now
it sounds like the core of your question is still "what happened with that specific payment intent pi_3QwqyEDfcmTYbu9Y2WYPHdxC to make the transfer not be associated with it"?
yes thats correct
k, digging in now. again, sorry about the delay, it's been a crazy day ๐
no problem sir/maam, I understand
Hello
Taking over here, can you give me a quick summary of your question while I catch up on the context?
Ah I see
sure, so basically there was a payment pi_3QwqyEDfcmTYbu9Y2WYPHdxC But for some reason it is not associated. while refunding this is the error we see in stripe and after seeing the error we got to know that transfer is not getting associated.
then pgskc said to use the payment intent which will work.
so, the question now is why was there no transfer associated to that payment.
so timebox came up with few reasons:
โข the application fee > amount, but I tested few payment (pi_3R19wgIJwkxnVmNV0bpPOq9D) with same application fee being more than amount and still transfer was associated and i was able to refund.
โข then he came up with another probable reason being the request for refund. successful one had refund_application_fee: "true", and the failed one had refund_application_fee: "false". But I tried refunding a new payment with "refund_application_fee": "false" and it worked. (request Id: req_LbrRm0Rhas7FUa).
then it was handed over to solanum
So the application fees you've provided are higher than the actual amount you're charging
yes, but that is not the cause of issue here. the issue here is why was transfer not associated to the pi_3QwqyEDfcmTYbu9Y2WYPHdxC
I have a feeling the amount mismatch is affecting the transfer
Do you have any other examples of where you've seen this occur?
we checked few but no, I havent seen any other. This one came up because someone tried to refund and got that error
but I created few payment with same amount and application fee and those worked fine.
โข pi_3R1WbPIJwkxnVmNV1C9XdtJn
โข pi_3R19wgIJwkxnVmNV0bpPOq9D
I see. Let me check something
I've flagged this with my team and we're investigating it
okay thanks.
We're still looking into this, thank you for your patience
sure no problem.
I have one question. Its getting too late here (1:30 am to be exact) If i dont reply in time, will that terminate this session? If so, how can I resume this again?
I can leave the answer/ next steps here. We will close this thread but you can always come back and summarize the issue on the ask.
Okay understood.
Thank you soo much sir/ma'am. ๐
Sure
We were able to identify what happened here. The issue was that this Connect Account lost transfer and payment capabilities. Since this is a delayed notification payment, https://docs.stripe.com/payments/payment-methods#payment-notification the transfer is not created until after the payment succeeds. However, since the transfer capability is disabled, we could not create the transfer later. in these cases, you should listen to the payment_intent.succeeded event to confirm the transfer: https://docs.stripe.com/api/payment_intents/object#payment_intent_object-transfer_data