Place order with disabled Payment method working

[dimitriBouteille]

Preconditions and environment

• Magento Version: 2.4.5-p4
• PHP Version: 8.1

The bug is testable in graphQl with checkmo. However :

• In REST there must also be the bug because it is the same classes that are used
• Reproducible bug with all methods

Steps to reproduce

• Disable checkmo method
• Create quote in graphQl
• Set addresses and shipping method
• Load payment methods, at this stage the checkmo method is not available

{
    "data": {
        "cart": {
            "available_payment_methods": [
                {
                    "code": "adyen_cc",
                    "title": "Credit or Debit Card"
                },
                {
                    "code": "affirm_gateway",
                    "title": "Affirm"
                }
            ]
        }
    }
}

• Set payment method with setPaymentMethodOnCart mutation

this mutation return The requested Payment Method is not available. error, but quote_payment.method column is updated with checkmo.

• Place order with placeOrder mutation
• Order created 🎉

Expected result

When saving the payment method and placeOrder, the following error should be reported: The requested Payment Method is not available.

When the setPaymentMethodOnCart mutation is called, there is an error, the quote_payment table should not be updated.

\Magento\Quote\Model\Quote\Payment::importData()

Actual result

The order is created :(

Additional information

mutation setPaymentMethodAndPlaceOrder(
  $cartId: String!
  $paymentMethod: PaymentMethodInput!
) {
  setPaymentMethodOnCart(
    input: { cart_id: $cartId, payment_method: $paymentMethod }
  ) {
    cart {
      selected_payment_method {
        code
        title
      }
    }
  }

  placeOrder(input: { cart_id: $cartId }) {
    order {
      order_number
    }
  }
}

{
    "cartId": "CART_TOKEN",
    "paymentMethod": {
        "code": "checkmo"
    }
}

Release note

No response

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 @dimitriBouteille. 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. 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.
⚠️ 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-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

  - 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.

[dimitriBouteille]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @dimitriBouteille. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @dimitriBouteille, here is your Magento Instance: https://a1fe3ae8511747381cac27ce90793387.instances-prod.magento-community.engineering
Admin access: https://a1fe3ae8511747381cac27ce90793387.instances-prod.magento-community.engineering/admin_028a
Login: ef78aade
Password: a4c76a83165f

[engcom-Bravo]

Hi @dimitriBouteille,

Thank you for reporting and collaboration.

Verified the issue on Magento 2.4-develop instance and the issue is not reproducible.Kindly refer the screenshots.

Steps to reproduce

• Disable checkmo method
• Create quote in graphQl
• Set addresses and shipping method
• Load payment methods, at this stage the checkmo method is not available
• Set payment method with setPaymentMethodOnCart mutation

this mutation return The requested Payment Method is not available. error, but quote_payment.method column is updated with checkmo.

• Place order with placeOrder mutation
• Order created 🎉

We have disabled checkmo method and checkmo method is not available

While Set payment method with setPaymentMethodOnCart mutation we are getting error The requested Payment Method is not available

We are not able to place the order with the Place order with placeOrder mutation.

Kindly recheck the behaviour on Magento 2.4-develop instance and elaborate steps to reproduce if the issue is still reproducible.

Thanks.

[dimitriBouteille]

@magento give me 2.4-develop instance