#elBR

1 messages · Page 1 of 1 (latest)

gaunt jayBOT
toxic gorge
#

I don't think a recurring price will work on a one off invoice but let me test this.

#

Confirmed. You cannot use a recurring Price record with a one-off Invoice.

#

The best option is to create a one-off price for the same amount and store some information in metadata to link the two prices for your own record keeping

trail briar
#

ok but is it save to save informations in metadata?

#

if metadatas are updated by mistake I do not keep any track of that specific invoice

toxic gorge
#

That depends how often you update your records. Plenty of users use metadata fields to track information for their own reconciliation

rustic gyro
#

No I mean in comparison with a price object, even if I decide to update I must create a new price, just to keep track

#

with metadata is not the same

#

if I update the metadata do I have any chance to check the previous value

toxic gorge
#

I'm not clear on what you mean. You can always retrieve the current metadata before you make an update.

rustic gyro
#

I mean that Stripe never deletes prices but keep them for history purposes, correct?

#

I want the same to happen with metadata. Or give some restrictions that metadata cannot be updated once created for that invoice

toxic gorge
#

You can delete a Price record through the Dashboard. But Stripe won't do it

rustic gyro
#

just to be safe if some metadata gets updated and I cannot now for what that invoice was generated

toxic gorge
#

That is not possible. Metadata is something that can be changed or modified at any point

#

But by you or someone else with access to the API keys

#

So as long as you control access and don't modify it yourself then it should work fine

rustic gyro
#

ok thanks