Hi Matt.

Thanks for a quick reply. I will post more info or a solution when i know more :)

Hi Bjarne.

Thanks for a quick answer.

We are removing test-secret-key- and live-secret-key- from the keys and make sure its trimmed. Because we read on docs they should be removed. But we also tried with them on. (same error).

I tried to add the absolute path to the terms. But still the same error.

The portal is switched to live and the test mode check mark in Umbraco is off.

We got another solution like this, where it only differs from merchant id and keys and that works. (that makes it even more mystical) So i tried to campare everything (i think)..

Since we copy our dev database when we start a new one. The payment provider and store gets the same id. Do you think that could be an issue?

Hi Bo

Yes, you can remove the test-secret-key- and live-secret-key- if you want, but they are removed anyway in the payment provider ifself.

The checkout key isn't specific used yet as it is not required for HostedPaymentPage option, but used for embed checkout. https://github.com/vendrcontrib/vendr-payment-provider-nets/blob/v1/main/src/Vendr.Contrib.PaymentProviders.Nets/Easy/NetsEasyOneTimePaymentProvider.cs#L425

But in that case the full key need to be used.

I don't think it should be an issue with same store id and same payment method id.. at least not if the stores use two different Easy accounts.

I don't think that would be an issue. Does the payment request fail if this is requested from www.domain1.dk ?

I don't think either, but its really the only different from the 2 sites, where one is working and the other one is not.

all the request should come from www.domain1.dk since we redirect everything to that domain. But NETS is on the case, but we know that gonna take ages, but i can't really see anywhere else the error could be at.

Hi Bjarne.

Yes, /umbraco and /umbraco/vendr/ is not redirectet. I guessed NETS could tell me something and if its total amout that do not match. But still havent heard anything from them.

Here is the full log:

System.AggregateException: One or more errors occurred. ---> Flurl.Http.FlurlHttpException: Call failed with status code 401 (Unauthorized): POST https://api.dibspayment.eu/v1/payments/
   at Flurl.Http.FlurlRequest.<HandleExceptionAsync>d__23.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Flurl.Http.FlurlRequest.<SendAsync>d__19.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Flurl.Http.FlurlRequest.<SendAsync>d__19.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Flurl.Http.HttpResponseMessageExtensions.<ReceiveJson>d__0`1.MoveNext()
   --- End of inner exception stack trace ---
   at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification)
   at Vendr.Contrib.PaymentProviders.Api.NetsEasyClient.Request[TResult](String url, Func`2 func)
   at Vendr.Contrib.PaymentProviders.Api.NetsEasyClient.CreatePayment(NetsPaymentRequest data)
   at Vendr.Contrib.PaymentProviders.NetsEasyOneTimePaymentProvider.GenerateForm(OrderReadOnly order, String continueUrl, String cancelUrl, String callbackUrl, NetsEasyOneTimeSettings settings)
---> (Inner Exception #0) Flurl.Http.FlurlHttpException: Call failed with status code 401 (Unauthorized): POST https://api.dibspayment.eu/v1/payments/
   at Flurl.Http.FlurlRequest.<HandleExceptionAsync>d__23.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Flurl.Http.FlurlRequest.<SendAsync>d__19.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Flurl.Http.FlurlRequest.<SendAsync>d__19.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Flurl.Http.HttpResponseMessageExtensions.<ReceiveJson>d__0`1.MoveNext()<---

Hi Bjarne.

In DEBUG mode it gives us the exact same error's. So we tryed with POSTMAN using Interceptor, but we could not intercept the api call. So now we gonna try to replica the data and see if we get a more detailed error message.

I am just baffled that NETS/DIBS have no intention on tryin to solve this issue.

Hi Bjarne.

We found the issue.

We was able to intercept the api call with Fiddler and see the whole 401 (Unauthorized) reponse with headers and everything. The whole 401 (Unauthorized) response is exactly what is logged in the first place.

But we noticed that the Secret Key provided in the Authorization header was missing the first letter. We have then tried to replace the key and insert the live-checkout-key- infront of it. But it still removing the first letter from the Secret Key.

So i will create a bug report here https://github.com/vendrcontrib/vendr-payment-provider-nets/issues

Hi Bo

Great you was able to narrow down the problem. Does the secret key coincidentally contain any of the following charcters: live-secret-key-?

I think it may replace/trim one character at the time from start of the string.

It surprises me that Nets Easy doesn't allow you to generate new keys, which most other payment gateways do.

Yes, the key starts with 'c', so it will trim it away.

I made a issue on github :)

For some reason nuget does not show any available updates for Vendr.Contrib.PaymentProviders.Nets in my Visual Studio.

So for other's who might encounter this problem, use Update-Package Vendr.Contrib.PaymentProviders.Nets -Version 1.0.1 in your Package Manager Console.