#chris-g_api
vague jewelBOT
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.
- chris-g_support, 3 days ago, 8 messages
ivory charmBOT
đ 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/1272642665267204176
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
sand knot
Following the documentation at
https://docs.stripe.com/api/issuing/transactions/test_mode_create_unlinked_refund
Here's example JSON:
{
"amount": -14300,
"card": null,
"currency": "GBP",
"merchant_data": null,
"purchase_details": {
"flight": null,
"fuel": null,
"lodging": null,
"receipt": null,
"reference": "11155682"
},
"[card][number]": "4111111111111111",
"[card][exp_month]": "4",
"[card][exp_year]": "2028",
"[card][cvc]": null
}
Invalid string: {:number=>"411111******1111", :exp_month=>"4", :cvc=>"", :exp_year=>"2028"}
rich forum
That card propert is a string, it is expecting the ID of an existing issuing card object.
sand knot
Any issue with using card_1NGTaT2eZvKYlo2CZWSctn5n, the example says ic_1Gswa82eZvKYlo2CP2jveFil as if they are two different card object types
what about a pm_id
rich forum
Can you try in test mode with the card_ or pm_ ID and see if you get an error? I am looking but am not immediately familiar with that endpoint and running the code should at least tell us if that isn't allowed at all
sand knot
will try pm, customer may already have one stored. thanks.
No such issuing card: 'pm_1Pn4S8JJDNRAeF0IKq74mGcj'
rich forum
Gotcha, and in prod you are looking to do this for non-issuing cards?
sand knot
Not sure what the difference is, just noticed the docs on issuing cards and was reading it now. Since these are refunds against payments made in the old gateway we can't use any stored payment methods, we would be taking the card info over the phone since it needs to be added to the new system. I can create the new stored payment method at that time then reference it in the unlinked refund.
To clarify, these are customer refunds so not sure the issuing card type is correct for the use case.
rich forum
Gotcha, Issuing is our product that lets you issue your own credit cards, so a different use case. I think if you reach out to our support team they can help you with unlinked refunds for your case https://support.stripe.com/?contact=true
sand knot
what should I ask them?
"I need to do unlinked refunds to payment methods not issued cards" ?
rich forum
Yep, if you describe your usecase that should be helpful. I'm not sure on the process around this, but they will let you know if they need more info
sand knot
They sent us this link but it doesn't pull up any code samples or even mention unlinked at all
https://docs.stripe.com/refunds#unlinked-refunds
rich forum
That doc section is hidden unless unlinked refunds are enabled for your account internally. The support person may not have realized that you need to be enabled to even see the doc