#thomasst

1 messages · Page 1 of 1 (latest)

dire karmaBOT
granite basin
#

There aren't any plans for this that I know of, but I can definitely flag it as feedback to the team!

stone breach
#

Thank you

#

That would be great

#

Is the only way to achieve this by using Sigma?

#

I specifically want to do queries like these:

  • stripe.Invoice.search(query="status:'open' metadata['type']:'usage' created<ONE_HOUR_AGO")
  • stripe.Customer.search("-coupon:null") 
granite basin
#

For that first one your best bet would be to do stripe.Invoice.search(query="metadata['type']:'usage' created<ONE_HOUR_AGO") and then filter through all of them to just get the ones with status: open

#

For the second one, a better alternative would be to always set some of your own metadata on the Customer whenever a coupon is added and then you'd query for that metadata

stone breach
#

The idea is to warn if somebody adds a customer coupon by accident in the dashboard, since we don't want that to happen (they should all be on subscription).

#

I guess we could do a one time scan and then use a webhook.

granite basin
#

Yeah that would be what I suggest (if you don't want to rely on sigma)

stone breach
#

Can you please explain the customer_updated.address=auto setting in checkout? I can see there is "never" and "auto". But does "auto" mean "always"?

idle torrent
#

👋 stepping in as karbi needed to step away

#

If set to auto it means that whatever portion of the billing address is collected will be saved. But it won't force full collection.

stone breach
#

What if it was combined with billing_address_collection=required?

idle torrent
#

Then it would always force collection of the full billing address and then update the customer details accordingly