PayPal Billing/Shipping missing on Virtual orders

[josephmcdermott]

This is a new ticket to re-open https://github.com/magento/magento2/issues/5873 since that ticket has been closed when there is still a major issue. Here are my consolidated comments from the previous ticket:

This is very easy to replicate with a clean Magento:

• install Magento 2.2.0 with sample data (or 2.2.1, but I happened to try with 2.2.0)
• add sandbox paypal credentials in the admin panel
• purchase product ID 51 (downloadable) using PayPal Express
• note that the order has no billing or shipping address data saved
• also note that when viewing the order in the admin panel, the billing address appears as the address template rather than the customer's address (which was not captured). This is the same in the printed invoice and in the customer account area.

I've been doing a bit of debugging of this, and I'm not actually sure its a bug per se. The fact that the billing address appears as {{depend prefix}}{{var prefix}} is a symptom of the issue for Magento to resolve, however the actual issue is perhaps that PayPal does not require, nor does it request, a billing address to complete an order.

The shipping and billing addresses associated to the quote are both empty during checkout with PayPal express, and you will notice that with other payment methods such as CheckMo you are asked for your billing address on the payment step, however with PayPal you are not asked any billing information. For virtual orders there is also no requirement for a shipping address, so neither are captured.

It's a bit annoying as we are left with a situation where we have zero address information about a customer for invoicing purposes, but perhaps this is by design...

Can @magento-engcom-team team comment on that? Was this a decision made by PayPal to restrict customer billing/shipping information visibility?

[giacmir]

I have the same issue. Every purchase of virtual quotes with paypal print the address template instead of the address information in admin order view page.

[aeu]

I am seeing this issue as well. I believe that it is by design, as it appears that when the product is Virtual, Magento does not capture any address information (because there is no product to ship).

Superficially this seems like a good idea, but as @josephmcdermott pointed out, this leaves us in a situation where we have no address information for billing / invoicing purposes.

[ghost]

I am seeing this issue for my virtual products everytime. How i can fix that?

Magento 2.2

[digitalredefned]

Out of curiosity - are these stores configured as stand alone stores? I'm currently migrating a handful of stores for a client and the only one I've ran into this with is set up as stand alone.

[czettnersandor]

Same problem here. This looks like a javascript bug as the address form is not showing at all when I fill the billing address and then refresh the page or apply a discount.

[magento-engcom-team]

Steps to reproduce this issue:

1. Configure PayPal Express.
2. Create downloadeble product.
3. Create customer without billing or shipping address and login in.
4. Add downloadable product to cart.
5. Proceed to checkout.
6. Choose PayPal Expres payment method.
7. Place order.
8. Open created order in backend.

Actual result: The billing address wrong appears as {{depend prefix}}{{var prefix}}.

[magento-engcom-team]

@josephmcdermott, thank you for your report. We've acknowledged the issue and added to our backlog.

[mikeschommer]

We are seeing same results even with Require Customer's Billing Address = Yes and PayPal billing address feature enabled in our merchant account. The only way we are able to get a billing address in there is if the customer clicks the "update" button before continuing the PayPal Checkout.

[hackronshins]

Is this bug fixed yet, Still I am also facing this issue for paypal orders in back-end on billing information it is displaying prefix variables as template. Replication steps:

1. Add product to the cart
2. Proceed to checkout
3. Using Paypal express payment method
4. Place the order
5. Lets check in backend in admin
6. Open Sales -> Orders
7. Open recent order with order id
8. See the billing information

Magento Version 2.3.1 Payment Method Paypal express (Card payment).

[m2-assistant[bot]]

Hi @engcom-Echo. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

• [ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• [ ] 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• [ ] 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• [ ] 5. Add label Issue: Confirmed once verification is complete.

• [ ] 6. Make sure that automatic system confirms that report has been added to the backlog.

[m2-assistant[bot]]

Hi @swathishs. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

• [ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• [ ] 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• [ ] 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• [ ] 5. Add label Issue: Confirmed once verification is complete.

• [ ] 6. Make sure that automatic system confirms that report has been added to the backlog.

[swathishs]

@magento give me 2.4-develop instance

[magento-engcom-team]

Hi @swathishs. Thank you for your request. I'm working on Magento 2.4-develop instance for you

[magento-engcom-team]

Hi @swathishs, here is your Magento instance. Admin access: https://i-12707-2-4-develop.instances.magento-community.engineering/admin_9743 Login: 824624c5 Password: 62b095d82f50 Instance will be terminated in up to 3 hours.

[swathishs]

@magento give me 2.3.5-p1 instance

[magento-engcom-team]

Hi @swathishs. Thank you for your request. I'm working on Magento 2.3.5-p1 instance for you

[magento-engcom-team]

Hi @swathishs, here is your Magento instance. Admin access: https://i-12707-2-3-5-p1.instances.magento-community.engineering/admin_0cc5 Login: 3f5dd38a Password: 2f94e78cc687 Instance will be terminated in up to 3 hours.

[m2-assistant[bot]]

Hi @engcom-Delta. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

• [ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• [ ] 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• [ ] 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• [ ] 5. Add label Issue: Confirmed once verification is complete.

• [ ] 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Delta]

@hackronshins , I'm not able to reproduce issue by steps you described on clean 2.4-develop. Was checked cases with virtual and downloadable products Manual testing scenario:

1. Create two products ( Virtual and downloadable )
2. Set up PayPal Express checkout
3. Navigate to storefront as a guest
4. Place order with virtual product using PayPal Express checkout
5. Login as a customer
6. Place order with downloadable product using PayPal Express checkout Result:
   • :heavy_check_mark: Billing information is displayed in My account->My Orders on storefront

• :heavy_check_mark: Bill-to Name is present for orders with Virtual and Downloadable products in admin panel

Please feel free to comment, reopen or create new ticket according to the Issue reporting guidelines if you are still facing this issue on the latest 2.4-develop branch. Thank you for collaboration.