#ensignkaul_62656
keen remnant
sly oyster
metadata fields work that same way for all objects (as far as I know :), and you can clear them by sending in an empty string:
"metadata": {
"key": ""
}
proven silo
does this apply to metadata that is already stored in existing/past transactions?
sly oyster
Not sure what you mean. You can do this when you call the update method on most Stripe objects, e.g. https://stripe.com/docs/api/charges/update#update_charge-metadata
proven silo
ok I think I understand
so if we were to set a null value for all charges for a specific metadata field, would that remove it from the stripe reporting module?
that's the crux of the issue, need to make sure we're not hitting the reporting module cap for payment metadata fields
sly oyster
No, it specifically needs to be an empty string as I shown in a snippet above ☝️
Not a null/undefined/false.
proven silo
sorry, prob not the right term. If we set an empty string for all charges in a specific payment metadata field, will that result in that metadata field disappearing from the reporting module or will it still be there and just be empty/blank?
sly oyster
Oh, I see. I don't know much about reporting unfortunately. It would make sense if it disappeared, but I would suggest trying this out for yourself, to make sure.
proven silo
ok, is there another resource/dept I can go to for questions on the reporting end?
sly oyster
It's best to ask Stripe Support: https://support.stripe.com/?contact=true
But trying this out quickly is probably the easiest/fastest way to know for sure. I am quite positive that this is the case.
proven silo
ok, thanks
sly oyster
Happy to help.