Bill-to and Payment Method Not Being Set For Invoices

[performadigital]

Hi there,

We're having a bit of a strange issue where when using the Stripe payment method on our Magento 2.1.11 site the Bill-to and Payment Method fields are not being populated. When testing this with other payment methods the data is set correctly.

This occurs not only on the Invoice admin grid but also when viewing the individual invoice. The billing address does appear to be set.

These orders are for virtual products which might be causing part of the issue?

Also to note in our test environment our admin users are using the en_US locale with the frontend being en_GB, which possibly could cause currency issues but that shouldn't be an issue I'd of thought.

Any ideas?

[pmclain]

I'll take a look this weekend. Are you testing with 3d secure enabled or disabled?

[performadigital]

I'm currently using the commit prior to that branch being merged in the past 24 hours. This is due to a small fix I made to the pmclain_stripe.js when region isn't set (cannot be null). I'll fork and create a PR for that if you think it's worthwhile?

[pmclain]

Yes, please do.

[pmclain]

I was able to reproduce the missing bill-to on a clean version of 2.1.11. The payment method name appears. I suspect that's because I added a config default for method title in v1.2.0, because the method name displayed is the default and not the value I have configured in the admin.

[performadigital]

Interestingly, we actually do have the Payment Method being set correctly (still missing Bill-to) on our development site, our live site however is missing the data from this field.

[pmclain]

This is a core bug in Magento 2.0.x and 2.1.x with the Gateway Sale Command magento/magento2/issues/9309, magento/magento2/issues/6438. It was fixed in core starting with 2.2.0, magento/magento2@a276241

It looks like the fix was an after plugin on Magento\Sales\Model\ResourceModel\Order\Handler\Address::process.

[performadigital]

Wonderful thanks for taking the time to look into this as I'd got a bit lost in the mass of issue reports and apparent fixes over on the Mage repo!