In AC Gold, you could click a refund button on a transaction, it would reach out to the authorize.net (AN) gateway, and initiate a refund or partial refund for a transaction.

That same button exists in AC9 (.0.7), but doesn't appear to work.

We recently had to do a refund, and it failed. The status on the refund says:

Gateway instance is null or could not be loaded.

The error log for this time stamp says:

---
Could not create provider instance: CommerceBuilder.Payments.Providers.AuthorizeNet.AuthorizeNet, CommerceBuilder.AuthorizeNet
Exception: Value cannot be null. Parameter name: type Stack Trace: at System.Activator.CreateInstance(Type type, Boolean nonPublic) at System.Activator.CreateInstance(Type type) at CommerceBuilder.Payments.PaymentGateway.GetInstance()
---

There's another error entry 15 seconds later with the exact same data:

---
Could not create provider instance: CommerceBuilder.Payments.Providers.AuthorizeNet.AuthorizeNet, CommerceBuilder.AuthorizeNet
Exception: Value cannot be null. Parameter name: type Stack Trace: at System.Activator.CreateInstance(Type type, Boolean nonPublic) at System.Activator.CreateInstance(Type type) at CommerceBuilder.Payments.PaymentGateway.GetInstance()
---

Payments work fine, so we know the gateway is setup correctly.

Please advise.

Thanks,
Charles

Edited by user Thursday, March 2, 2023 5:34:38 PM(UTC)  | Reason: Not specified

Odd, my reply didn't show up. Maybe I didn't click Post.

Anyhow, thanks for the reply. There is no custom coding in here.

Looking at the config for the authorize.net plugin, there's a "Debug Mode", but I'm hesitant to turn it on without someone telling me exactly what it does. I don't see anything there for logging.

There are two different AuthNet gateways in Gold i.e. AuthNet and AuthNetCIM but in AC9, we have ONLY AuthNetCIM gateway that provides the whole functionality.
So we need to check few things here:

- Do you have the only AuthNet gateway configured in Gold or both?
- If it was only AuthNet, then have you installed and configured the AuthNetCIM gateway after upgrade in AC9? This should have been updated automatically on upgrade by the way.
- Check the payment gateways page in admin /Admin/Payments/Gateways to see if the configured gateways are listed.

Actually the difference in AuthNet and AuthNetCIM is the ClassId (i.e. ac_PaymentGateways.ClassId). For AuthNet it is CommerceBuilder.Payments.Providers.AuthorizeNet.AuthorizeNet, CommerceBuilder.AuthorizeNet and for AuthNetCIM it is CommerceBuilder.Payments.Providers.AuthorizeNetCIM.AuthNetCIMProvider, CommerceBuilder.AuthorizeNetCIM

From the error, it appears to me that the AuthNetCIM is not configured and the old AuthNet class id is in database which is causing mismatch. On upgrade, we do fix the ClassId's being updated in AC9 but it seems that this case wasn't handled.

If that is the case, you have two options:

1. Just update the AuthNet Name and ClassId in database. Name from Authorize.Net to Authorize.NET CIM (name change is optional) and ClassId from CommerceBuilder.Payments.Providers.AuthorizeNet.AuthorizeNet, CommerceBuilder.AuthorizeNet to CommerceBuilder.Payments.Providers.AuthorizeNetCIM.AuthNetCIMProvider, CommerceBuilder.AuthorizeNetCIM
2. Install/configure the AuthNetCIM plugin in AC9.

Option #1 is best moving forward.

Edited by user Friday, March 3, 2023 7:34:55 AM(UTC)  | Reason: Not specified

Is the order you are trying refund is placed using previous AuthNet gateway it is AuthNet CIM? You can check this from Order Payments tab in admin.

That's what I suspected. Since the old AuthNet gateway is no more available (in codes) that is why the Class ID is irrelevant now. The previous gateway will not work. You must have updated the ClassID to the one AuthNetCIM is using but I suspect it will give you the duplicate instance id error. Can you temporarily update the ClassId to CommerceBuilder.Payments.Providers.AuthorizeNetCIM.AuthNetCIMProvider, CommerceBuilder.AuthorizeNetCIM in database and do the refund?

Edited by user Friday, March 3, 2023 10:38:38 AM(UTC)  | Reason: Not specified

Great. I am sure any post order operations will work without any issue going forward using the new AuthNetCIM configured. So you should be all good.

Yes, you can remove it if the new installed plugin is working fine and you are doing post order processing for old orders outside the AbleCommerce. If you leave the entry in the DB, it won't hurt because there shouldn't be any payment method assigned to the old gateway.