Credit Card Expiration Date incorrect on review page

This is also happening on user/#/payment-methods/#/edit, where Authorize.net is returning (and Commerce is saving into the database) YY, but the select dropdown for year expects YYYY. The month displays fine, but the year will always be the "first item in the dropdown" (i.e., no selection whatsoever).

hm... Not sure I understand the change? Could it be that Auth.net isn't calling calculateExpirationTimestamp() so it isn't properly set?

@jsacksick, thanks for the pointer.

Does Commerce Core always expect YYYY for the payment expiration date?

I'm not sure calculateExpirationTimestamp() is the _only_ answer, at least, because that also expects a YYYY, but Authorize.net is only asking for (from the user, in Accept.js UI) a YY and also only returns a YY after all is said and done. That then gets saved into commerce_payment_method__card_exp_year.card_exp_year_value. The AcceptJs code DOES call calculateExpirationTimestamp(), but I'm guessing it's only passing in YY.

We'll be looking into this a little more closely in the next few weeks.

@Morbus Iff, The issue mentioned with comment #4 was belongs to the patch submitted with issue queue #3019539 ✨ Expand Accept.js to include Accept.js UI Needs review

Since, the patch was developed in context of Authorize.net (Accept.js UI) API, which accepts expiry_year in format of YY, while the Commerce Payment stores that value in YYYY format. which creates conflict on Payment Method edit, that the default year won't get select as expected.

The bug was fixed with the most recent patch update #38 ✨ Expand Accept.js to include Accept.js UI Needs review

we can close this issue now.