#sam-request-header
livid harness
Do you have a Request ID for the failed Refund request?
Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
stoic lark
sure!
here is one where i tried to add the connect id account: req_lY7F0eN1gFcrLG and here is one without: req_rocCZ3m38MQYP4
both of them are with payment ids crated in test mode (refund tried with the test api keys too)
livid harness
Is there a reason you're using the /v1/terminal/readers/tmr_FUHnNQ66j4jdPy/refund_payment endpoint instead of the regular /v1/refunds endpoint?
stoic lark
we need to for interac payments in canada
unless we are now able to process them without the terminal?
livid harness
I think you can. Have you tried?
stoic lark
this is what the dashboard says
livid harness
Ahhh, okay. Hmmm...
Ah, okay I think I know what's going on. The request is being made on the wrong account.
The PI was created on this account --> acct_1KRjYfIXJEsTqc6v
But you're trying to refund it to this account --> acct_1C5MJVHO1gULFck6
stoic lark
is that because of the terminal id used? i don't understand how you differentiate or specify the accounts?
livid harness
If the reader is tied to a specific Connect account, then it won't have access to other accounts' Payment Intents, so I think at some point the Terminal reader got switched or reconfigured for a different account between when the payment was made and when it was attempted to get refunded
stoic lark
hmmm that doesn't really make sense to me though because that account acct_1C5MJVHO1gULFck6 does not have any readers currently set up
so why would it try refunding there
livid harness
Is it possible the reader was added to this other account (acct_1KRjYfIXJEsTqc6v) at some point after you attempted the refund?
stoic lark
i don't believe so, i've been using it on the same account since i've begun my testing. I'll try creating a new PI now and refunding it immediately. but i believe that it what i did last time too. I'll let you know once I'm done!
livid harness
Sounds good!
stoic lark
okay so PI created with
connect account: acct_1KRjYfIXJEsTqc6v
terminal ID (associated with above account):
tmr_FUHnNQ66j4jdPy
payment_intent_id:
pi_3OH94NIXJEsTqc6v1iVQkKbu
refund request id req_eeJQHJ42Waoauy
and still getting the same error
livid harness
Hmmm... okay. One thing I noticed in the earlier request where you attempted to pass a Connect account id: it looks like it's coming through as a parameter to that request, rather than an HTTP request header.
Can you paste the code you were using to pass the stripe_account in that request?
stoic lark
i'm just doing it via postman right now so that i know how sending in the request will work. i am sending it in the body like this:
should it be sent in the headers?
i just tried it in the headers, but that didn't work either
livid harness
Do you have a request ID for the one where you passed it into the header?
Here are the docs on the header btw: https://stripe.com/docs/connect/authentication#stripe-account-header
arctic flareBOT
stoic lark
AH! i was sending it in the header as lower case. that worked for me!! 🥳 thank you for all your help, and for sending over the docs. i will say it's not the easiest thing to find.
livid harness
totally understand. Happy that it's working now though!