vipera74

[timid depot]

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.

• viper-subscription-events, 1 hour ago, 18 messages

[fresh island]

Hello

There are no intentions currently to deprecate the plan property so yes it is safe. You would receive communication if that was going to be deprecated.

In terms of the name of the customer, can you show me an example Event that I can look at?

[marsh terrace]

Regarding the plan: I should however create new subscriptions using price and product, or should I use plan?
Regarding the name of the customer: I am listening to the customer.updated event, and I am setting it in "Cardholder name", but the "name" I get from the event is null

Note that this is Test Mode

[fresh island]

Yes we recommend migrating to using Prices and Products

That name is associated to the billing details for the PaymentMethod, not the Customer object.

[marsh terrace]

Hence it would be better and more forward-looking using that in the management of the subscription event, going back to my initial question? Even though it's not in deprecation

[fresh island]

You should see that stored here: https://stripe.com/docs/api/payment_methods/object#payment_method_object-billing_details-name

[fresh island]

Yes

[marsh terrace]

Great, thank you for your help, take care