nikhil_05327

[brisk goblet]

Hello! We'll be with you shortly. 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.

• nikhil_05327, 1 hour ago, 6 messages

[forest folio]

👋 happy to help

what exactly are you referring to?

[upbeat horizon]

hello , i want to store the refund id in the table having the max size 40 chars , will it be a issue if is it fine ?

@forest folio are you there ?

hello ?

[forest folio]

yes it might be

https://stripe.com/docs/upgrades#:~:text=Make sure that your integration can handle Stripe-generated object IDs%2C which can contain up to 255 characters. For example%2C if you’re using MySQL%2C store the IDs in a VARCHAR(255) COLLATE utf8_bin column (the COLLATE configuration provides case-sensitivity during lookups).

[upbeat horizon]

why is it not fine , as we are getting the ids of size 26 chars for now

[forest folio]

https://stripe.com/docs/upgrades#:~:text=Make sure that your integration can handle Stripe-generated object IDs%2C which can contain up to 255 characters

Make sure that your integration can handle Stripe-generated object IDs, which can contain up to 255 characters.

[upbeat horizon]

unable to find the constraint on refund id

[forest folio]

this is for all IDs

[upbeat horizon]

i am using 40 chars , will it we fine for now ?

i am using 40 chars , will it we fine for now ?
please help

[forest folio]

I already answered you but you're not fond of the answer

the recommended length is 255

whether you want to use 40 or not is up to you