Non-Default Card May Have Been Charged for Stripe

Between August 8, and September 6th, 2019, if a customer had more than one card stored in Stripe, a card that was not the default may have been charged if the subscription renewed.

The last four digits of the card showing on the customer’s invoice or statement may not be the card that was actually charged. The discrepancy can be seen in the raw request vs raw response on the transaction.

Previously, Chargify used only the Stripe Customer ID and expected the customer’s default payment source to be charged. On August 8th, code was introduced that depended on the order cards were returned in the Stripe API. For some subscriptions, we may have selected an older card that was not the default.

We have now corrected this to restore the behavior of charging the customer’s default payment source, and sincerely apologize for any inconvenience this has caused.


Additionally, as of September 27th, we now support Stripe’s newer Payment Methods in addition to the older Sources.

Between September 6th and 27th, 2019, if you were using Stripe’s Payment Methods API, since the customer did not have a default_source, we could not create charges for them. We have now updated our integration to look for a default_payment_method in addition to a default_source.