Backend Order creation Authorizenet: If invalid credit card number is entered the loader keeps spinning forever without any error message

[Jakhotiya]

Preconditions

1. Magento 2.2-develop branch
2. Enable Authorizenet payment gateway

Steps to reproduce

1. Go to Admin-> Sales -> Order->Create new Order
2. Add items to card and choose shipping method
3. Select Authorizenet Credit Card as payment method.
4. Input an invalid credit card number, like just enter 10 digits credit card number
5. Hit submit Order, loader shows up and keeps spinning forever

Expected result

1. If entered Credit card number is incorrect, it should propmt user to enter correct card number. The loader should stop.

Actual result

1. The loader keeps spinning forever. There are no javascript errors in console, or logs.
   

[magento-engcom-team]

Hi @Jakhotiya. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

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

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento-engcom-team give me {$VERSION} instance

where {$VERSION} is version tags (starting from 2.2.0+) or develop branches (2.2-develop +).
For more details, please, review the Magento Contributor Assistant documentation.

@Jakhotiya do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

[Jakhotiya]

@magento-engcom-team give me 2.2-develop instance

[magento-engcom-team]

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

[magento-engcom-team]

Hi @Jakhotiya, here is your Magento instance.
Admin access: https://i-17964-2-2-develop.engcom.dev.magento.com/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[Jakhotiya]

@magento-engcom-team Yes I was able to reproduce the issue.

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