#Marc Andrew
wide juniper
nimble basin
Hello! Can you share your images in this thread please?
nimble basin
I'm not aware of anything changing in this area, but I can check. I will say that we typically don't allow metadata to be read with a publishable key, only a secret key; could that be the difference?
uncut dagger
Ah that might explain the difference. I will note that the metadata was returned in the past and we have been relying upon it in our production application since January of this year.
nimble basin
Hm. I'm not finding anything about this changing. Could be a bug. When did you first notice the issue?
Does the metadata show up after connecting to the reader, or is it still missing?
nimble basin
Oh, wait, I think I found something about this, hang on...
Is this on a new Stripe account by chance?
Also can you provide one of the Terminal Reader ID's that isn't showing metadata as expected?
Looks like this is an intentional change we made to improve security, but existing accounts that used this functionality should continue to have it. I'm wondering if an account that hasn't used this functionality prior to the change is being used now?
uncut dagger
That would probably explain it, this user has just purchased their first terminal and set it up recently.
We were wondering why some of our bigger existing users haven't noticed it yet.
nimble basin
Those accounts should have the legacy behavior, yeah.
I'm flagging this internally. The reader ID would help if you can provide it.
uncut dagger
Reader ID
tmr_FKsXOws30Irush
Do you also need the Stripe account ID? This is a Stripe Connect account by the way.
nimble basin
Nope, reader ID is all I need, thanks!
Okay, can you give this another try and see if you see the metadata now?
uncut dagger
Yep, can confirm I'm seeing the metadata now. Thanks for that.
Is it safe to assume though that we'll need to update our application so it isn't reliant on metadata?
nimble basin
Checking on that now...
Now that we fixed your platform account this should continue to work indefinetly, so you don't need to make any changes. Just be aware that the metadata on these Terminal objects is publicly visibile, so don't store anything sensitive there.
uncut dagger
Okay, thanks for your help. Just to confirm this will also apply to any Connect accounts that are onboarded in the future?
nimble basin
Yep, the change was made to your platform account, not this specific connected account, so you should to be good to go with future connected accounts.
uncut dagger
Perfect, thanks again.
nimble basin
Happy to help!
If you're still around, it would help if you could tell us about your use case for metadata in this scenario?
uncut dagger
Sure, we provide rental car management software and integrate with Stripe so our users can process booking payments.
Most of our users have multiple locations/depots, hence the need to group terminals into locations so that users only see the terminals at their location. We do provide an override so they can view all terminals if necessary.
By storing the location ID in the terminal metadata we don't need to maintain the relationship between terminals and locations on our end.
nimble basin
Thank you! This is very helpful.
Have you considered using the Reader's label property for this instead? Or are you using that for a different purpose? https://stripe.com/docs/api/terminal/readers/create#create_terminal_reader-label
uncut dagger
We let our users set the label. For those that have multiple terminals at a single location they can use labels to identify terminals. For example, they may have "Counter 1", "Counter 2" etc.
nimble basin
Makes sense. Thank you for answering those questions! 🙂
uncut dagger
No problem.