Skip to content

[Issue] Added order_place_redirect_url to SelectedPaymentMethod and OrderPaymentMethod result #39909

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
2 of 5 tasks
m2-assistant bot opened this issue May 12, 2025 · 3 comments · May be fixed by #39896
Open
2 of 5 tasks

[Issue] Added order_place_redirect_url to SelectedPaymentMethod and OrderPaymentMethod result #39909

m2-assistant bot opened this issue May 12, 2025 · 3 comments · May be fixed by #39896
Assignees
@engcom-Bravo @engcom-November
Labels
feature request Progress: ready for grooming Reported on 2.4.x Indicates original Magento version for the Issue report.

Comments

@m2-assistant
Copy link

m2-assistant bot commented May 12, 2025

This issue is automatically created based on existing pull request: #39896: Added order_place_redirect_url to SelectedPaymentMethod and OrderPaymentMethod result

Description (*)

This PR allows GraphQL to return the order_place_redirect_url, this way paypal and other PSPs would be able to support orders being placed using GraphQL.

Manual testing scenarios (*)

  1. Set up the PayPal payment method (or another making use of the order_place_redirect_url)
  2. Add products to cart, perform regular checkout steps.
  3. Call the setPaymentMethodOnCart graphql mutation and check if order_place_redirect_url is available.
  4. Call the placeOrder graphql mutation and check if order_place_redirect_url is available.

Contribution checklist (*)

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests (if applicable)
  • README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
  • All automated tests passed successfully (all builds are green)
@m2-assistant m2-assistant bot linked a pull request May 12, 2025 that will close this issue
Open
6 tasks
@github-project-automation github-project-automation bot moved this to Ready for Confirmation in Issue Confirmation and Triage Board May 12, 2025
@engcom-Bravo engcom-Bravo added the Reported on 2.4.x Indicates original Magento version for the Issue report. label May 12, 2025
@engcom-Bravo engcom-Bravo self-assigned this May 12, 2025
@m2-assistant M2 Assistant
Copy link
Author

m2-assistant bot commented May 12, 2025

Hi @engcom-Bravo. 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 engcom-November self-assigned this May 20, 2025
@m2-assistant M2 Assistant
Copy link
Author

m2-assistant bot commented May 20, 2025

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
Copy link
Contributor

Hello @indykoning ,

Thank you for your report and collaboration.

After reviewing the description, we’ve identified this as a feature request. Therefore, we are categorizing it accordingly.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@engcom-Bravo engcom-Bravo

@engcom-November engcom-November

Labels
feature request Progress: ready for grooming Reported on 2.4.x Indicates original Magento version for the Issue report.
Projects
Feature Requests Backlog
Status: No status
Milestone
No milestone
2 participants
@engcom-Bravo @engcom-November