JayP | Stripe Developers | Page 1

frail pierBOT Sep 13, 2022, 3:53 PM

#

bright relic Sep 13, 2022, 3:54 PM

#

Hi there

#

The Description will always be on the receipt

#

You can use multiple key value pairs for metadata, why is that not sufficient here?

undone spire Sep 13, 2022, 3:56 PM

#

It's an issue relating to GDPR and PII. Essentially we have some custom PII data which is recorded in metadata and some custom non-PII data which we would like to record separately so that we can load it into a non-GDPR server via Fivetran

#

If we store PII and non-PII data in metadata its challenging for us to transform without loading it into our data-warehouse

bright relic Sep 13, 2022, 3:57 PM

#

Hmmm are you using PaymentIntents?

#

Or just /v1/Charges

undone spire Sep 13, 2022, 3:59 PM

#

Both but we could look into storing PII in Intents metadata and non-PII in Charges metadata if that was your suggestion

bright relic Sep 13, 2022, 4:00 PM

#

Yeah was going to recommend something like that

#

Basically if you store metadata on a PaymentIntent before it is successfully confirmed, then that metadata will get carried down to the Charge

#

But after the PaymentIntent is confirmed and the Charge is created, you could update metadata on the objects individually and it will stay separate

undone spire Sep 13, 2022, 4:01 PM

#

I'll look into that. Thanks!

#JayP