authorizenet / dotnet-core-sdk-beta Goto Github PK

Can you push this package to NuGet with a preview tag so I can test it in my pipeline?

Is there a reason the sample code project was removed? Do you guys have plans to support this library in the near future for .net core?

When I try to use the sandbox MerchantId & TransactionKey (currently used for Soap call) for making the api call using it returns E00007. I am unable to understand why the values work for Soap based call but not for the api call.

I create a fresh sandbox and it worked with the new MerchantId & TransactionKey. Has anyone faced a similar issue and how can I fix this?

Thanks for your help!
Nazim

Hi
I got this exception while running a sample with ASP.Net Core 3.1

: Method not found: 'Microsoft.Extensions.Logging.ILoggerFactory Microsoft.Extensions.Logging.DebugLoggerFactoryExtensions.AddDebug(Microsoft.Extensions.Logging.ILoggerFactory, Microsoft.Extensions.Logging.LogLevel)'.

Is this SDK still being worked on?

When should we expect this to be released to NuGet as a Package?

When I use the Hosted Payment Page API integration and attempt to make a payment the form gives an error: "Unexpected error. Please try again".

Steps to reproduce:

1. Use the sdk library to create a getHostedPaymentPageRequest object and populate the transactionRequestType.order field (The error does not occur if this field is not populated):

var request = new getHostedPaymentPageRequest
{
	transactionRequest = new transactionRequestType
	{
		transactionType = transactionTypeEnum.authCaptureTransaction.ToString(),
		amount = paymentAmount,
		order = new orderType
		{
			invoiceNumber = invoiceNumber,
			description = description
		}
	},
	hostedPaymentSettings = new settingType[]
	{
		new settingType
		{
			settingName = settingNameEnum.hostedPaymentPaymentOptions.ToString(),
			settingValue = "{\"cardCodeRequired\": true, \"showCreditCard\": true, \"showBankAccount\": false}"
		},
		new settingType
		{
			settingName = settingNameEnum.hostedPaymentReturnOptions.ToString(),
			settingValue = "{\"showReceipt\": false, \"url\": \"" + continueReturnURL + "\", \"urlText\": \"Continue\", \"cancelUrl\": \"" + cancelReturnURL + "\", \"cancelUrlText\": \"Cancel\"}"
		},
		new settingType
		{
			settingName = settingNameEnum.hostedPaymentIFrameCommunicatorUrl.ToString(),
			settingValue = "{\"url\": \"" + communicatorURL + "\"}"
		},
		new settingType
		{
			settingName = settingNameEnum.hostedPaymentBillingAddressOptions.ToString(),
			settingValue = "{\"show\": true, \"required\": false}"
		}
	} 
};

2. Send the request and retrieve the token from the response.
3. Use the token to load the hosted payment form into an iframe.
4. Enter credit card information into the form and click the submit button.

Observed result:
The form will show an error message in red text, "Unexpected error. Please try again".

The response from Authorize.Net is:

{"resultCode":"Error","messageCode":"E00001","messageText":"Unexpected error. Please try again.","token":null,"transactionData":null,"userFields":null,"createPaymentProfileResponse":null}

Notes:
I had previously been using the dotnet sdk and did not experience this problem in version 1.9.6 or 1.9.7 (https://github.com/AuthorizeNet/sdk-dotnet). I did not change any code but switched to the dotnet core sdk DLL (https://github.com/AuthorizeNet/dotnet-core-sdk-beta/blob/master/ReleaseArtifact/AuthorizeNET.dll) and started seeing the problem.

If you inspect the requests being sent by the dotnet core sdk you'll see it has extra fields as part of the order information. It was sending discountAmount and purchaseOrderDateUTC with default values in addition to the invoiceNumber and description fields. 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).

The decompiled orderType class definition in the dotnet core sdk has many fields that do not exist in the dotnet sdk. And the new discountAmount and purchaseOrderDateUTC fields are not nullable so they get sent along with default values. I downloaded the dotnet core sdk code from github, removed the extra fields in the orderType class and rebuilt the code. When I used that DLL I was able to complete a payment without any problems.

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?

Looking at the project I see it is a netcoreapp2.0

Since AuthorizeNet is a library it should be a netstandard1.3 or netstandard2.0 and be the same code for .Net framework and .Net Core.

What is the reasoning for not making a NetStandard library that can be shared accross all .Net environment?

Thank you,

Frederic