payment[extension_attributes][consent_ids] key during the POST.
Now, I know what you might be thinking, that "It's probably just an issue with GDPR.", but we have another website where we are setting up Amazon Pay and it's causing issues with another module that tries to capture additional fields in the
This module adds a text box to capture a Delta SkyMiles account number and was built mostly following this stack answer. It's a pretty straight forward little module that does what it needs to do and like the GDPR, works on every payment method except Amazon Pay. And just like the GDPR, none of the mixins run, and the field ultimately is not added to the
payment[extension_attributes] key during the POST.
So, my hope here is that someone has some insight as to what might be happening here. Because I'm at a loss at this point. This does not seem like the behavior I would expect from a proper payment method.
I've learned after some testing that this only happens to JS mixins applied to the
payment_methods section of the checkout and are acting on
Magento_Checkout/js/action/place-order. We recently added a checkbox to the
shipping_methods section of checkout that acts on
Magento_Checkout/js/action/set-shipping-information and that one works fine when using Amazon Pay and the checkbox is properly captured for the order.