John Carter

A `PaymentIntent.create()` classmethod is possible, though it seems like it would be a very thin wrapper around `stripe.PaymentIntent.create` (maybe just do a `cls.sync_from_stripe_data` on the result). I was initiallly thinking...

Removing this from 2.1.0 milestone because I don't think it's a blocker on release.

This might get bumped to 2.2

Yep, makes sense

Yeah a setting to enable stripe ids makes sense to avoid migration pain. Downside is of course it's another dimension of configuration to test, but seems like the less painful...

I don't know. What's the reasoning behind the Customer purge behaviour?

2 years later... I'm not sure if there's a better ticket for this, but I assume we're still thinking that moving towards storing all currencies as ints is the way...

I've added #955 to track this issue.

Something we might want to look at for 2.2 release. However it doesn't seem to support PaymentIntent/PaymentMethod yet (or other new objects like TaxIds), so maybe we should hold off...

Dropping for now unless someone wants to take this on.