kuro091

[ripe marsh]

Thanks for sharing the screenshot. It looks like the fixture of subscription.payment_succeeded event from CLI sends raw card number in payment method creation: https://github.com/stripe/stripe-cli/blob/master/pkg/fixtures/triggers/subscription.payment_succeeded.json

There is recent change that starts restricting sending raw card number in the test mode

Can I suggest you to:

1. Copy this feature and create the new one?https://stripe.com/docs/cli/fixtures
2. Remove the first payment method fixture of sending raw card data
3. Change ${payment_method:id} to pm_card_visa: https://stripe.com/docs/testing?testing-method=payment-methods#cards

[wise haven]

so something like this?

What do I run afterwards

stripe fixtures [thatfilepath] ?

which seems to give me an error

[ripe marsh]

Can you change line 29 to following?

invoice_settings: {
  default_payment_method: '${attach_payment_method:id}'
}

[wise haven]

hey that worked! omg

[ripe marsh]

Woohoo! That's great to hear

[wise haven]

so separate question but, does subscription.created not trigger subscription.updated ?

[ripe marsh]

It depends. If there is a change in the subscription from the created one, customer.subscription.updated will be sent

[wise haven]

I see ty ty that was really helpful