PayPal IPN Fails with Multiple Merchant Accounts

[0xMatt]

Preconditions (*)

1. CentOS 8
2. PHP 7.4
3. Magento 2.4.3-p1

Steps to reproduce (*)

1. Setup default PayPal Pro merchant account information used by primary store
2. Setup secondary PayPal Pro merchant account scoped to the secondary website config

Expected result (*)

1. IPN posts back successfully

Actual result (*)

1. Error occurs, IPN does not use the store ID from the order

 main.CRITICAL: The requested "merchant@example1.com" and the configured "merchant@example2.com" merchant emails don't match. {"exception":"[object] (Exception(code: 0): The requested \"merchant@example1.com\" and the configured \"merchant@example2.com\" merchant emails don't match. at /var/www/html/magento/vendor/magento/module-paypal/Model/Ipn.php:123)"} []

The IPN posts back to my website id 2, but it's comparing with the email from website id 0(admin).

This results in complete failures of postback notifications.

---

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

• [ ] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• [x] Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• [ ] Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• [ ] Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• [ ] Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant[bot]]

Hi @0xMatt. Thank you for your report. To speed up processing of this issue, make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, review the Magento Contributor Assistant documentation.

Add a comment to assign the issue: @magento I am working on this

To learn more about issue processing workflow, refer to the Code Contributions.

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

  :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

:clock10: You can find the schedule on the Magento Community Calendar page.

:telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

:movie_camera: You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

:pencil2: Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[0xMatt]

I cannot provide my PayPal credentials into a demo instance. How should I go about reproducing this? I can provide access to my server from a Magento staff member, but that's about it as far as giving any sort of access to our merchant information.

[engcom-Lima]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

Hi @engcom-Lima. Thank you for your request. I'm working on Magento instance for you.

[m2-assistant[bot]]

Hi @engcom-Lima. 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.

[magento-deployment-service[bot]]

Hi @engcom-Lima, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.

[engcom-Lima]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

Hi @engcom-Lima. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @engcom-Lima, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.

[engcom-Lima]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

Hi @engcom-Lima. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @engcom-Lima, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.

[engcom-Hotel]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

Hi @engcom-Hotel. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @engcom-Hotel, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.

[engcom-Lima]

Hi @0xMatt, I tried digging deep into the issue, from the code base and the log It seems that Magento is loading the proper store view i.e second store but the email we get in response from PayPal is different than what is configured for the second store scope.

File: \Magento\Paypal\Model\Ipn::_getConfig

// verify merchant email intended to receive notification
        $merchantEmail = $this->_config->getValue('businessAccount');
        if (!$merchantEmail) {
            return $this->_config;
        }
        $receiver = $this->getRequestData('business') ?: $this->getRequestData('receiver_email');
        if (strtolower($merchantEmail) != strtolower($receiver)) {
            // phpcs:ignore Magento2.Exceptions.DirectThrow
            throw new Exception(
                sprintf(
                    'The requested "%s" and the configured "%s" merchant emails don\'t match.',
                    $receiver,
                    $merchantEmail
                )
            );
        }

As you can see in the code base Magento tries to match the email configured in second store with the email received in Paypal response data. Proper data is loaded from Magento end e.g for Second Store View email merchant@example2.com is loaded correctly.

Can you please try to verify in your Paypal account the same email is configured as that in your Magento instance.

Thanks!

[engcom-Hotel]

Dear @0xMatt,

We have noticed that this issue has not been updated for a period of 14 Days. Hence we assume that this issue is fixed now, so we are closing it. Please raise a fresh ticket or reopen this ticket if you need more assistance on this.

Regards

[atty31]

I m still facing this on M2.4.6, any updates on this one ?