Stripe Product Features are not synced to Firestore collection

[fetchhai]

Bug report

• Extension name: firestore-stripe-payments

Describe the bug

In Stripe, we have the option to add features list at the product level. But when syncing, its not carried over to the firestore db.

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

1. Go to Stripe
2. Search for a product
3. Add features list in "Additional Options"
4. Check in Firestore DB in the products collection
5. features is not updated in the collection

Expected behavior

Features list should be successfully synced in the Firestore products collection

Screenshots

N/A

System information

N/A

Additional context

Add any other context about the problem here.
N/A

[jsteele-stripe]

The product features list is currently a Dashboard only feature for use with the pricing table. They're not available via the API and as such this extension cannot currently support them.

[iKK001]

Do you plan in the future to sync the product's Features list with the Firebase-Stripe-Extension for Payments/Subscriptions ?

Currently my observation is that the webhook-event at product-creaton fills most of the product fields (including the prices subcollection). However, the product Feature list is currently missing.

I could really use those field on my client apps.

Workaround proposal 1:
Somewhat teedious, but at least a workaround: set up my own webook-backend method on a separate server that listens for the product-creation-event as well (next to the extension that does so already). And I would then have to update those Features list values to the firestore collection myself. I feel that this is a bit overkill but would work. Timings are an issue tough.

Workaround proposal 2:
Another approach I am choosing in the meantime: I use product metadata in addition to the Features-list. Those metadata are added by the extension and are available in the products-collection at least. The client then somehow "mimics" the Features-list with the metadata-key/values instead. Also teedious but less network-traffic going on than with proposal 1.

[jakehockey10]

Seems like it is part of the API according to this: https://stripe.com/docs/api/products/object#product_object-features

[maderesponsively]

@jakehockey10 Yes - i noticed this. Surely this is an easy update.

@jsteele-stripe can we add this now?

[jakehockey10]

@maderesponsively Here is the PR for it. Looks like it has been ready for a while now: #578

But I do believe Invertase will get to it soon. They've been doing good work on this project lately.