Jerome Leclanche

I'm trying to get dj-stripe out this week.

I agree, if we do this it probably doesn't involve the Plan or Coupon models, at least immediately (cf what I said in the OP)

Yep. Ideally I'd want to figure out a way that ensures Coupon and Plan *can* be fkey'd like that. I am currently trying to figure out if it's a good...

Coming back to this with a clearer head: I implemented a custom StripeForeignKey class which replaces models.ForeignKey for everything except the Coupon and Plan special-cases. I subsequently am able to...

@therefromhere I have a set of commits which implements Stripe IDs as foreign keys as a setting, similar to how we handled USE_NATIVE_JSONFIELD. This kind of sidesteps implementing a migration,...

Coupons and plans used to be manual-only, it's only somewhat recently they started giving them (still-optional) autogenerated IDs. OTOH we haven't had dual live+test mode support for particularly long.

The reason that property isn't synced is because it updates out of band without broadcasting through a webhook (due to the `redeem_by` property). My plan was to add it as...

If you set a coupon to expire at a certain date, you won't receive a webhook at that date to update the `valid` property on the coupon itself. That's the...

I think we should move to storing currencies in an integer field just like Stripe does. It'll simplify synchronization. I also quite like the idea of making the field a...

Yeah, including the `livemode` parameter in get_or_create was my doing. The reasoning at the time was that I was adding live+test mode support to the Customer object and, to check...