Error creating order with payment services paypal - select credit card

[matteorossi-thespacesm]

Preconditions and environment

• Magento 2.4.7-p4

Steps to reproduce

Configure adobe payment services and connect to paypal account
Configure payment services to use credit card
Create an order with payment services paypal, payment through credit card

Email not sent.
Backoffice order details page not working.

Expected result

Order email should be sent.
Order details should be visible in backoffice.

Actual result

Exception log and order details page report the following error:
Warning: Undefined array key "card" in vendor/magento/module-payment-services-paypal/Block/Info.php on line 55

Additional information

In module Magento_PaymentServicesPaypal, file etc/di.xml, beginning at line 659 a payment source item is named "cc". Unfortunately item info is saved as "card", so an array key is not found.

Release note

In module Magento_PaymentServicesPaypal, file etc/di.xml, beginning at line 659
either change:
<item name="cc" xsi:type="string" translatable="true">Credit Card</ite>
as:
<item name="card" xsi:type="string" translatable="true">Credit Card</item>
or add a row:
<item name="card" xsi:type="string" translatable="true">Credit Card</item>

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• 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]

Hi @matteorossi-thespacesm. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.

• 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.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 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.

[m2-assistant]

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: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - 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-November]

Hello @matteorossi-thespacesm ,

Thank you for your report and collaboration.

Are you still experiencing this issue?

We attempted to reproduce the behavior on the latest 2.4-develop branch but were unable to replicate it. Could you please verify if the issue persists on the latest version of Magento and let us know if there are any specific steps we might have missed?

In the meantime, we are marking this ticket as "Issue: Needs Update."

Thank you!

[m2-assistant]

Hi @engcom-November. 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: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - 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-November]

Hello @matteorossi-thespacesm ,

Just following up on the above comment. Please let us know if you have any updates or need further assistance.

Thank you!

[engcom-November]

Hello @matteorossi-thespacesm ,

This issue is being closed since it has not been updated in a long time.Please feel free to reopen or raise a new ticket if the issue still exists.

Thank You!