topic Re: OrderType is causing Unexpected error during Payment withour ordertype payment working successfu in Integration and Testing

OrderType is causing Unexpected error during Payment withour ordertype payment working successful

mvkotekar1983 — Mon, 10 Dec 2018 14:28:57 GMT

I would like to know if there are any dependencies or relationship exists with OrderType while creating CreateAnHostedPaymentPage.

Reason being, when I dont add OrderType with OrderId, payment is successful

When I add OrderType with OrderId, I get unexpected error when I click on Pay button of accept hosted form within IFrame

Re: OrderType is causing Unexpected error during Payment withour ordertype payment working successfu

ElaineM — Tue, 11 Dec 2018 05:59:39 GMT

Hi mvkotekar1983,

Accept Hosted doesn't use an orderId element. In fact, Authorize.Net does not currently use orderId. If you are including this with your getHostedPaymentPageRequest, I would expect that an error would occur.

You can review the accepted values within a getHostedPaymentPageRequest at: https://developer.authorize.net/api/reference/index.html#accept-suite-get-an-accept-payment-page

Can you elaborate on what you are attempting to accomplish so I can point you in the right direction?

Thank you,

Elaine

Re: OrderType is causing Unexpected error during Payment withour ordertype payment working successfu

mvkotekar1983 — Tue, 11 Dec 2018 14:24:44 GMT

I apologize for the confusion. The actual issue is around new orderType() where we define the invoiceNumber and Description details.

Issue is: When we define orderType with invoiceNumber and Description, the transaction would end up in unexpected error.

When we remove the orderType assignment same code works for successfull payment transaction.

Here are the setting details

settingType[] settings = new settingType[5];

settings[0] = new settingType();
settings[0].settingName = settingNameEnum.hostedPaymentButtonOptions.ToString();
settings[0].settingValue = Serializer.SerializeToJson(new { text = "Pay" });

settings[1] = new settingType();
settings[1].settingName = settingNameEnum.hostedPaymentOrderOptions.ToString();
settings[1].settingValue = Serializer.SerializeToJson(new { show = false });

settings[2] = new settingType();
settings[2].settingName = settingNameEnum.hostedPaymentReturnOptions.ToString();
settings[2].settingValue = Serializer.SerializeToJson(new { showReceipt = false, url = returnUrl, urlText = "Continue", cancelUrl = cancelUrl, cancelUrlText = "Cancel" });

settings[3] = new settingType();
settings[3].settingName = settingNameEnum.hostedPaymentPaymentOptions.ToString();
settings[3].settingValue = Serializer.SerializeToJson(new { cardCodeRequired = false, showCreditCard = true, showBankAccount = false });

settings[4] = new settingType();
settings[4].settingName = settingNameEnum.hostedPaymentIFrameCommunicatorUrl.ToString();
settings[4].settingValue = Serializer.SerializeToJson(new { url = commUrl });

Here is the code to generate transactionRequestType

return new transactionRequestType
{
transactionType = transactionTypeEnum.authCaptureTransaction.ToString(),
amount = amount,
order = new orderType() { invoiceNumber = paymentOrderId.ToString(), description = paymentDescription }
};

Below code is used to set the appropriate details to generate the token

var paymentPageSettings = CreatePaymentPageSettings();
var transactionRequest = CreateTransactionRequest(paymentOrderId, paymentDescription, amount);

var request = new getHostedPaymentPageRequest();
request.transactionRequest = transactionRequest;
request.hostedPaymentSettings = paymentPageSettings;

Re: OrderType is causing Unexpected error during Payment withour ordertype payment working successfu

Renaissance — Tue, 11 Dec 2018 18:38:31 GMT

Again with the disclaimer that I don’t know this language, it looks like you are declaring an instance of an object and setting property values of that object in one line. I think you would need to instantiate the ordertype object and assign it a variable, then in separate lines use method calls to set the properties.

Re: OrderType is causing Unexpected error during Payment withour ordertype payment working successfu

Renaissance — Tue, 11 Dec 2018 21:34:45 GMT

Nope. You’re following C# syntax. I just looked it up. On second glance I think you may need to set the argument of the transaction request to Order instead of invoice and description. Order is a property of the transaction request, or order type is rather, which it appears you are assigning to a variable called order. It’s been fun helping you along. In addition to keeping me entertained while I wait for food you’ve gotten me interested in C#. Best of luck to you.

Re: OrderType is causing Unexpected error during Payment withour ordertype payment working successfu

mvkotekar1983 — Sat, 15 Dec 2018 15:42:19 GMT

Hi, Thanks for your finding. I apologize if I didn't follow your suggestion.

1. I am creating instance of OrderType filling InvoiceNumber and Description field

2. Assign it to TransactionRequestType

3. TransactionRequestType is assigned to the TransactionRequest

Let me know if above implementation is not appropriate. (Are you saying, we need to associate ordertype to the transactionRequest directly?)

Re: OrderType is causing Unexpected error during Payment withour ordertype payment working successfu

Renaissance — Sun, 16 Dec 2018 16:26:00 GMT

I think this line is the source of your problem-

var transactionRequest = CreateTransactionRequest(paymentOrderId, paymentDescription, amount);

what I'm not getting is why paymentOrderId and paymentDescription are in there. It looks like you are directly putting the properties of the orderType in the transaction request. Without knowing C#, I would think that you would either a) put it in there like this:

var transactionRequest = CreateTransactionRequest(order, amount);

or b)

something along the lines of-

var transactionRequestType = new transactionRequestType
{
transactionType = transactionTypeEnum.authCaptureTransaction.ToString(),

amount = amount,
order = new orderType() { invoiceNumber = paymentOrderId.ToString(), description = paymentDescription }
};

var transactionRequest = CreateTransactionRequest(transactionRequestType);

And the above code I just typed is probably halfway nonsense syntactically, but it just seems odd compared to how the php API works the way this logic is laid out.

It is like you are skipping one or more middlemen with this line-

var transactionRequest = CreateTransactionRequest(paymentOrderId, paymentDescription, amount);

because the orderType is a property of the transactionRequestType, and the invoiceNumber and description are properties of the orderType.

So if you wanted to access the invoiceNumber in a drill down fashion it would be:

transactionRequest->transactionRequestType->orderType->invoiceNumber

However, your logic to me appears to go like this:

transactionRequest->invoiceNumber.

So the API is kind of saying "you can't get there from here" in the response.

It would make sense that your code would run without these values, because all that is required is an amount to create a transaction request.

Maybe this will help. I messed around with C# for a little bit the other day after reading your posts. It is quite a different animal, but more of the same in other ways. Might not hurt to try.

Re: OrderType is causing Unexpected error during Payment withour ordertype payment working successfu

mvkotekar1983 — Tue, 18 Dec 2018 15:36:11 GMT

Thanks for your response, again, I apologize for the confusion. The code mentioned below is custom method I created to ensure I create the transaction type with all the details.

CreateTransactionRequest(paymentOrderId, paymentDescription, amount);

Below is the implementation of CreateTransactionRequest user defined function.

private static transactionRequestType CreateTransactionRequest(decimal paymentOrderId, string paymentDescription, decimal amount)
{
return new transactionRequestType
{
transactionType = transactionTypeEnum.authCaptureTransaction.ToString(),
amount = amount,
order = new orderType() { invoiceNumber = paymentOrderId.ToString(), description = paymentDescription }
};
}

As you can see one of the property order am creating a new orderType with invoice# and description. Honesty, this may not be relevant to the issue that we are facing.

The payment works successfully when I don't pass orderType.

The payment ends up with unexpected error when I pass orderType.

There is some link or dependency that we are unable to identify. Or the way we are making transaction request has more or less settings.

Re: OrderType is causing Unexpected error during Payment withour ordertype payment working successfu

Renaissance — Wed, 19 Dec 2018 19:14:33 GMT

Consolidating my 2 posts from yesterday. No worries about any confusion. The user defined function that matched an API method threw me off. I am not sure what the issue is, but my hunch is that there is some kind of noise introduced when you attempt to pass the parameters in that function to the orderType object.

I think it might be useful to try to do this without your custom function.

First define the orderType the exact same way you did in your function, and assign it to a variable. Then instead of a custom function to create the transactionRequestType you would have a variable that serves the same purposeSo you would have something like
var order = new orderType() { invoiceNumber = paymentOrderId.ToString(), description = paymentDescription }

var transactionRequest = new transactionRequestType
{
transactionType = transactionTypeEnum.authCaptureTransaction.ToString(),
amount = amount
order = order
};

My food just came out. Hope this helps.

Re: OrderType is causing Unexpected error during Payment withour ordertype payment working successfu

mwrightmcci — Fri, 21 Dec 2018 22:41:15 GMT

I started having the same problem with orderType when I recently tried to switch to using the dotnet core sdk in beta (https://github.com/AuthorizeNet/dotnet-core-sdk-beta). I had previously been using the dotnet sdk and did not experience the problem in version 1.9.6 and 1.9.7 (https://github.com/AuthorizeNet/sdk-dotnet). I’ve added an issue to the dotnet core sdk with some extra details (https://github.com/AuthorizeNet/dotnet-core-sdk-beta/issues/11).

To summarize, the problem I have seems to be caused by the members of the orderType class. In the dotnet core sdk the class has many fields that do not exist in the dotnet sdk, such as discountAmount and purchaseOrderDateUTC. These fields are not nullable and so they get sent along with default values even if you are only setting orderType invoiceNumber or description. I can only assume this causes a problem in Authorize.Net’s system because those fields are not part of the API (https://developer.authorize.net/api/reference/#accept-suite-get-an-accept-payment-page).

This is a blocking problem preventing us from using the dotnet core sdk. Can we get an idea of when this will be resolved? Also the sdk is still in beta, but the code repository has modifications in it from 2 years ago. Is there a reason it is still in beta, and when can we expect it will be available for use in production?

Re: OrderType is causing Unexpected error during Payment withour ordertype payment working successfu

mvkotekar1983 — Wed, 09 Jan 2019 15:28:55 GMT

Any updae on this would be of great help.

Re: OrderType is causing Unexpected error during Payment withour ordertype payment working successfu

mvkotekar1983 — Mon, 14 Jan 2019 16:03:21 GMT

Finally my senior spent a week of time and got it resolved for me :( .

New version: 1.9.7 Does not work. [Added more fields to OrderType]

Old Version: 1.9.6 Does work. [Existing fields were very few]

The problem could be rooted in the way how Authorize.net upgraded their version.

Authorize.Net might have broken existing API.

For now, we are building our project with an older version of Authorize.Net and releasing to the client.

CC: @Anurag <Please confirm if our investigation is correct or if we are missing something>

Re: OrderType is causing Unexpected error during Payment withour ordertype payment working successfu

Ansira2300 — Fri, 15 Feb 2019 17:27:06 GMT

We are having the same exact issue. We were also using v1.9.7 of the Authorize.Net nuget package and had to roll back to v1.9.6 to get around it. If we called without setting the order with the orderType the transaction would go through. When we added that it fails. The message in the Authorize.Net iframe just says an "unexpected error has occured" in red at the bottom. We are currently switching over from SIM to Accept. Something must have broken this in v1.9.7, hopefully a fix is coming. See our code snippet below. If we didn't set the order on the transactionRequest it worked. When we did it broke as described above and in this post.

//address information
var billAddress = new customerAddressType
{
firstName = currentBillingRecord.BillingFirstName,
lastName = currentBillingRecord.BillingLastName,
address = currentBillingRecord.BillingAddress.StreetAddress1,
city = currentBillingRecord.BillingAddress.City,
state = currentBillingRecord.BillingAddress.StateProvinceCode,
zip = currentBillingRecord.BillingAddress.PostalCode,
phoneNumber = phoneNumber
};

var order = new orderType
{
invoiceNumber = orderNumber,
};

var transactionRequest = new transactionRequestType
{
transactionType = transactionTypeEnum.authOnlyTransaction.ToString(), // authorize only
amount = amount,
billTo = billAddress,
order = order
};

Regards,
TC

Re: OrderType is causing Unexpected error during Payment withour ordertype payment working successfu

schernokov — Sat, 02 Mar 2019 18:13:05 GMT

Same issue here.

I am converting from SIM to Accept Hosted.

Downloaded SKD November 2018 release - 1.9.7. And was receiving "Unexpected Error" message when charging credit card. I was getting the token without any issues from getHostedPaymentPageRequest request. But was never able to charge the credit card.

I was able to narrow it down to orderType object, which is very important because it contains invoice number and transaction description; so, I could not afford not to pass it.

Thanks to this thread (specifically to mvkotekar1983 user), the problem was identified to the extra properties that orderType has in 1.9.7 release, which are not supported by API.

I modified 1.9.7 and recompiled and my Accept Hosted page works! I am not done with the migration. I will report back if there is anything that I needed to modify.

What I did, I modified orderType class implementation in 1.9.7 SDK and commented out the extra fields. orderType class is located in Api/Contracts/V1/AnetApiSchema.generated.cs file. I commented out everything except:

public string invoiceNumber;
public string description;
public event System.ComponentModel.PropertyChangedEventHandler PropertyChanged;

protected void RaisePropertyChanged(string propertyName) {

System.ComponentModel.PropertyChangedEventHandler propertyChanged =this.PropertyChanged;

if ((propertyChanged != null)) {

propertyChanged(this, new System.ComponentModel.PropertyChangedEventArgs(propertyName));

}

I also had to modify public static void orderType(orderType argument) method in requestFactoryWithSpecified.cs file. Just comment out everything in this method.

I then recompiled. And my Accept Hosted page worked!

Re: OrderType is causing Unexpected error during Payment withour ordertype payment working successfu

Ansira2300 — Tue, 12 Mar 2019 20:03:36 GMT

Disappointed that they put out another update that still seems to have the same issue. Tested with version 2.0.0 published Saturday, March 2, 2019 and it still has the same issues so we have to stick with version v1.9.6 still.

Re: OrderType is causing Unexpected error during Payment withour ordertype payment working successfu

TCCPGrimes01 — Tue, 02 Jul 2019 12:52:11 GMT

How do you putout a 2.0 and a 2.01 and still have this issue?

Are we missing something?

1.9.6 still works.

Re: OrderType is causing Unexpected error during Payment withour ordertype payment working successfu

Renaissance — Wed, 03 Jul 2019 09:15:34 GMT

@TCCPGrimes01

I was about to make a suggestion but the user a few posts above me beat me to it. You can manually remove or comment out a few lines of code in the class files. Remove the members and methods of the class that are not in the schema and your API call will work. The user above points you to the appropriate lines.

Re: OrderType is causing Unexpected error during Payment withour ordertype payment working successfu

Ansira2300 — Mon, 08 Jul 2019 19:59:21 GMT

We are still holding on 1.9.6 because of this issue. We could make code changes suggested and rebuild the binaries but that is not a smooth upgrade process by any means. I was hoping the next version would fix two versions ago...

Re: OrderType is causing Unexpected error during Payment withour ordertype payment working successfu

edealer07132017 — Mon, 22 Jul 2019 21:15:18 GMT

I am also having the issue as everyone in this thread has experienced in both SANDBOX and PRODUCTION when using OrderType.

I am using AuthorizeNet v2.0.1 in a C# environment.

 var transactionRequest = new transactionRequestType
            {
                transactionType = transactionTypeEnum.authCaptureTransaction.ToString(),
                amount = modelData.amount * modelData.numberOfPeople,
                customer = new customerDataType() { email = modelData.emailAddress },
                billTo = new customerAddressType() { company = modelData.companyName },

                order = new orderType()
                {
                    invoiceNumber = modelData.invoiceNumer,
                    description = "THIRD PARTY TRAINING INVOICE"
                },
            };

If I comment out the OrderType object, it goes through with no error.

Re: OrderType is causing Unexpected error during Payment withour ordertype payment working successfu

Ansira2300 — Wed, 06 May 2020 22:09:23 GMT

So this issue still persist in 2.0.1 and we are perpetually stuck on 1.9.6 where iit works. Again the fix being modify your files and build your own binaries seems like very poor version management. It doesn't appear from Nuget that this package has been updated in a year. It was last updated March 20, 2019 for version 2.0.1

Is there a replacement to this SDK that we should be using?

Regards,