#simran-khosla_api

1 messages · Page 1 of 1 (latest)

severe hingeBOT
#

👋 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/1329519942978113576

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

molten junco
#

Hi 👋

I"m not sure what you mean by the "Stripe Portal". Are you referring to the Dashboard?

#

Do you have object IDs that get created when you initiate these returns?

severe hingeBOT
valid rivet
#

oh yes

#

yeah sorry i meant the dashboard -- so we haven't built this piece yet but essentialy this is the documentation we're looking at :

#

So we have our own Portal / UI on our side for our end users for ordering hardware -- we use the Terminal Hardware API for this.

#

Essentially what we're trying to do is allow them to submit a form on our side with all the relevent information for our Support Team to initial the return in the Stripe Dashboard as per the docs above

#

but where we're getting hungup is, we need some "feedback" into our UI to show us, has the order actually been returned? Are the Readers now unavailable for use because they've been returned?

#

So just curious if there's any sort of, way to get the status or updates on a return once it's initiated in the stripe dashboard?

#

This is all for connected accounts on our side. Since we purposely do not give our connected account clients do not get access to the Stripe Dashboard.

#

So I'm just trying to gauge how much we can actually know about a Hardware Return we initiate in the dashboard, outside of opening the dashboard and looking it up.

hidden goblet
#

Thanks for the info, I am not immediately finding a way to do this but am still looking. This may have to be a feature request if not unfortunately

#

Yeah unfortunately I am not seeing a way to check on the status of these orders in an automated way at the moment. The API doesn't have access to them, there isn't a field on the hardware order object, and I'm not seeing a daily report or anything that gives status updates on these. I am filing a feature request, but unfortunately we don't support this as far as I can tell.

valid rivet
#

Yeah i was worried this would be the answer. Thank you for filing the feature request -- is there a way for me to track that?

#

so to confirm we can only sorta, make them but there's no visibility into Returns / return status beyond looking it up int he dashboard right

#

One other question since the documentation doesn't explicitly say. When you DO look it up in the dashboard for a return, in my hypothetical scenario of 2 of 4 devices being returned on an other.

#

Is there visibility into a return? Like which devices actually made it there and the status there in the dashboard?

#

The docs don't really show me what that part of it looks like in the Dashboard and i'm not eager to test out a return of a test device just to see this bit 😂

hidden goblet
#

Good question on following it yourself. Looking in to that.
You can test returns on test mode hardware orders, that is exactly what I was about to suggest.

valid rivet
#

Yeah will try that ! Thank you!

hidden goblet
#

We do have a returns page that shows individual readers when I look at my test return now

image.png
valid rivet
#

So that Started status there

#

is there anyway to swap that to "done" or something

#

to see how it looks when recieved (mostly looking for if it can show me information about the device that was actually returned here)

#

There's no way to ping that Return ID right -- that's right nex tto RETURN in your screenshot. (through the API)

#

this is very helpful by the way thank you!

hidden goblet
#

Yeah unfortunately not, seeing that when testing this gave me hope for a moment, but I couldn't find a public endpoint that included it. I thought the hardware order object might have an expandable returns field or something but I wasn't able to find anything like that.

valid rivet
#

yeah was hopeful for the same. That it'd be on the Terminal Hardware object somehow

#

or that the Reader would be marked as returned or something, but there doesn't seem to be any sort of data

#

is there any way for me to track that feature request or -- is that just something internal on your side i wouldn't have access to.

#

And in the UI there, the dashboard in the test one. Is there any way that you know of to simulate that return to "Complete"

#

cause i'd at least like to see how one of these would look like in the dashboard if possible when returned, without sending a real kit back you know? So we can spec some workarounds out on our end at least?

#

Here's an id of one i made on our side in test omde if that helps: thrt_1QhzCaEgQAxJcOH46mPTtsOk

#

unsure if you can just update it in the backend or something for me?

hidden goblet
#

I can't update that myself unfortunately, though it looks like our support team may be able to help you with that. We can create a ticket with this thread, I can grab it, note that you want to 1) move that status to "returned" if possible and 2) follow the feature request, and pass it on to my colleagues that would know more about that.

#

I feel like "so close and yet so far" is the theme of this thread today 😅

severe hingeBOT
#

Hello @valid rivet, we have sent you a direct message, please check it at https://discord.com/channels/@me/1329541840248242267

  • 🔗The message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.
hidden goblet
#

Let me know when you've created a case with the above

valid rivet
#

truly!

#

okay so -- do i need to put all this stuff in again with stripe bot?

#

reexplain the situation?

#

okay i think i did it!

#

i don't know if i added the specific test order i wanted on there though so will see if i can add that

#

i have no idea where the case went though?

#

the bot just sort of made it and said goodbye?

#

and i got a generic "we've received your support message" email?

#

don't really have a link for that or anything?

#

It doesn't seem to have any information I figured it'd pull this entire convo in or something?

hidden goblet
#

I am not seeing the case where I would expect it to be. Can you DM me your email? I am looking with that sco_ ID but otherwise I can look this up by your email

#

Ah I found it!

valid rivet
#

yup!

#

also i have a follow up question somewhat erelated

#

so like i said we're using the Terminal Hardware Orders API to create these

severe hingeBOT
valid rivet
#

and we're making these orders for our connect accounts, we were under the impression that the only option for payment is a monthly invoice and we'd just have to use tranfers or other mechanism to charge our merchants the fee for the terminal.

#

But -- i see in the api documentation that there is a payment_type: payment_intent

#

but i can't find any explanation or documentation of how that woudl work?

#

if we wanted to use a Payment Intent so that one of our connected accounts would actually "pay" for the order and that would be the payment method on the order (so that when it'd returned it just goes right back to that connected account)

#

how would that work?

fluid gull
#

👋 stepping in

valid rivet
#

👋

#

yeah what we're trying to do basically is avoid having it so that our parent account is charged and then we have to make a transfer from teh Connected Account to our account to "reimburse" ourselves for the terminal order?

#

hoping there's just an easy way to charge their account with a PaymentIntent?

fluid gull
#

What type of Connected Accounts?

valid rivet
#

ah let me check

#

ACTUALLY this question doesn't really apply to us I forgot!

#

We may distribute them to various connected accounts and we're kinda the "device registry"

#

so i think that's why we set them up as payment_type: monthly

#

so feel free to ignore the question!

#

ie. technically our account / ourselves are the real "owners" here you know.

#

so wouldn't make sense to directly charge their accounts anyways.

#

sorry for the unnecessary q there

#

i think i have most of what i need with our support ticket now!

#

feel free to close the thread!