topic Re: Create ARB Subscription via Opaque Data (from Accept.js) in Integration and Testing

Create ARB Subscription via Opaque Data (from Accept.js)

pmgower — Tue, 21 Mar 2017 16:19:03 GMT

So our application is a website that is built on ASP.NET.

The front end is JavaScript and the back end is C#.

We are using Accept.js on the front end to create two nonce tokens (1 for the ARB sub, 1 for the 1 time transaction). I realize this might not be the best way to do this with two separate transactions but it is what we have for now. This was actually working yesterday until after around 5pm. Then we started getting the E00114 Invalid OTS Token error message every time we tried to create the ARB sub. The 1 time transaction would work just fine.

So we tried flipping the nonce values in case the one we were trying to use for the ARB sub was wrong but even after swapping them to use the other one the 1 time transaction worked but the ARB sub did not. This validated that the nonce values appear to be working fine. We talked to Authorize.net support and they informed us that the error message E00114 could also be returned if the data sent to create the ARB sub was not valid even if the token was valid.

Can anyone help me diagnose or validate the ARB create transaction we are sending to Authorize.net? I have read some people reference the ability to capture the XML being sent to Authorize.net via the SDK but since I am using the nuget package (v1.9.1) I'm not sure how to turn this option on.

Any help would be greatly appreciated.

Re: Create ARB Subscription via Opaque Data (from Accept.js)

Aaron — Tue, 21 Mar 2017 17:22:44 GMT

Hi @pmgower,

Logging in the .NET SDK is done using the Microsoft's ETW system. More details in my reply on the other thread.

As far as troubleshooting the ARB request, hopefully you can get a log of exactly what's sent and we can see if there's a problem there. In the meantime, there's a couple of things to check.

Make absolutely sure that the same login ID is being used to make the ARB request as to get the nonce
Make sure that both places are going to the same environment (whether production or sandbox).
If you're seeing failures in production, what happens when you switch both the nonce generation and the ARB request to sandbox?

If you can get a log of the request, please post that here. In the meantime, if you want to post the section of your code that's doing the ARB request, maybe there's something to see there.

Re: Create ARB Subscription via Opaque Data (from Accept.js)

steve074 — Tue, 21 Mar 2017 17:45:40 GMT

Hello Aaron,

We are experiencing the same problem. Just started yesterday. We are using the Java SDK.

When we make our first charge, we set the duplicate window timeout to 0 seconds. The interesting thing is, we get the Invalid Token error when we execute our code in real time. However, if we step through the code in a debugger, enough time elapses between our 1 time charge and the ARB subscription set up that does not fail.

Again, this worked fine until yesterday. Also, it still works in the sandbox, but does not in production. We had been setting up subscriptions like this succesfully for several weeks now, I think there is a problem on your end.

Thanks,

Tim Stevens, University of Minnesota Foundation.

Re: Create ARB Subscription via Opaque Data (from Accept.js)

Aaron — Tue, 21 Mar 2017 18:08:36 GMT

Hi @steve074,

Ah, so the timing of the request is key for you. @pmgower, can you tell if yours is time-related? Like, can you induce a delay between retrieving the nonce and doing the ARB request?

If there's no one here currently investigating this internally, I'll make sure someone's on it.

Re: Create ARB Subscription via Opaque Data (from Accept.js)

steve074 — Tue, 21 Mar 2017 18:23:42 GMT

Yes, it seems to be possibly ignoring the duplicate window time out. I opened support ticket 1-406091561, you can link back to that one if you want.

Thanks,

Tim

Re: Create ARB Subscription via Opaque Data (from Accept.js)

Aaron — Tue, 21 Mar 2017 18:36:04 GMT

Hi Tim,

My hunch is that it's not related to the duplicate window, because if it wasn't respecting that timeout, you'd get a different error. However, there could be other checks employed that could prevent some sort of quick use, or other problems as well.

I'll try to escalate that ticket internally so they're not just asking the same things.

Re: Create ARB Subscription via Opaque Data (from Accept.js)

steve074 — Tue, 21 Mar 2017 18:41:40 GMT

Thanks, we appreciate quick action on this as it is causing trouble for our donors.

One other observation that may help is that when we run in real time, we are often gettting the same nonce value on our second nonce call. Not always, and that doesn't seem to be related to the error, as it fails either way.

Tim

Re: Create ARB Subscription via Opaque Data (from Accept.js)

pmgower — Wed, 22 Mar 2017 19:04:12 GMT

Thanks for the quick response @Aaron. As of yesterday I couldn't even get the create ARB subscription to work. However, this morning I tried it all from my local machine and it all works if I run it through the debugger to capture the trace/log information. The moment I run it outside of the Visual Studio debugger it doesn't work and returns the same E00114 error message.

I tried adding a 1 and then 5 second delay between when the front end sends the request to the backend to create the ARB subscription. I suppose I could try to add a delay between getting the two differente nonce values on the frontend but I haven't done that yet because the create ARB subscription is the first one that is using a nonce so IF they are the same create ARB subscription should work.

I am now going to work on writing the necessary code to log the trace values. Very discouraged at the fact that I can't easily turn on logging in your SDK and that I have to do it manually.

I will let you know once I get the XML from the trace information; however, when running it inside VS's debugger I didn't see where the request XML was being logged in the trace information. Any guidenance into how I can get the request XML would be greatly appreciated.

Here is the code I use to send create the ARB Subscription:

const short AUTHORIZE_NET_NO_END_DATE_TOTAL_OCCURRANCES = 9999;

bool worked = false;
transactionResponse = null;

var monthlyInterval = new paymentScheduleTypeInterval()
{
    length = 1,
    unit = ARBSubscriptionUnitEnum.months
};
var monthlySchedule = new paymentScheduleType()
{
    interval = monthlyInterval,
    startDate = DateTime.Now.AddDays(1),
    totalOccurrences = AUTHORIZE_NET_NO_END_DATE_TOTAL_OCCURRANCES,
    trialOccurrences = 0
};
var paymentType = new paymentType() { Item = model.NonceToOpaque(model.SubscriptionNonce) };

string subscriptionName = $"ProxBox Subscription for {model.FullName}";
ARBSubscriptionType subscriptionType = new ARBSubscriptionType()
{
    amountSpecified = true,
    name = subscriptionName,
    amount = model.MonthlySubscriptionSubtotal,
    paymentSchedule = monthlySchedule,
    billTo = model.nameAndAddressType,
    shipTo = model.nameAndAddressType,
    payment = paymentType,
    trialAmountSpecified = false,
};

var request = new ARBCreateSubscriptionRequest { subscription = subscriptionType };
var controller = new ARBCreateSubscriptionController(request);
controller.Execute();

//get the response which will contain errors (if any)
var response = controller.GetApiResponse();

//validate respose
if (response != null)
{
    if (response.messages.resultCode == messageTypeEnum.Ok)
    {
        if (response.messages.message != null)
        {
            worked = true;
            transactionResponse = response.ToTransactionResponseModel();
        }
        else
        {
            var errorMessage = $"Subscription Error (Subscriber: {model.FullName} - {model.EmailAddress}): No message was set (refId: {response.refId})";
            logger.Error(System.Reflection.MethodBase.GetCurrentMethod().DeclaringType, errorMessage, exception: null);
        }
    }
    else
    {
        var errorMessage = $"Subscription Error (Subscriber: {model.FullName} - {model.EmailAddress}): {response.messages.message[0].code} {response.messages.message[0].text}";
        logger.Error(System.Reflection.MethodBase.GetCurrentMethod().DeclaringType, errorMessage, exception: null);
    }
}
else
{
    var results = string.Join(", ", controller.GetResults().ToArray());
    var errorMessage = $"Subscription Error (Subscriber: {model.FullName} - {model.EmailAddress}): Reponse was null, ResultCode: {controller.GetResultCode()}, Result Messages: {results}";
    logger.Error(System.Reflection.MethodBase.GetCurrentMethod().DeclaringType, errorMessage, exception: null);
}

return worked;

Re: Create ARB Subscription via Opaque Data (from Accept.js)

pmgower — Wed, 22 Mar 2017 19:32:35 GMT

Actually, @Aaron, after further review. If I add a System.Threading.Thread.Sleep(5000) call before I try to create the request and send it to Authorize.net it in fact does allow it to succeed on my local machine. I will be testing this on the STAGE server very soon.

So back to your initial theory (which would explain how it stopped working with no code changes) is there seems to be a timing issue. Did your team enable any extra checks or something that would require a delay between getting the Accept.js nonce values and using them in an api call this week?

Also should we be concerned about doing two nonce requests to accept.js one after the other in the front end?

Re: Create ARB Subscription via Opaque Data (from Accept.js)

Aaron — Wed, 22 Mar 2017 20:14:18 GMT

@pmgower wrote:
Did your team enable any extra checks or something that would require a delay between getting the Accept.js nonce values and using them in an api call this week?

I'm not aware of anything, but that's what we're trying to find out. We (Authorize.Net) haven't made any changes, but the bits that create the nonce are part of a larger Visa effort, so we can't rule out the possibility of a change being made somewhere outside of Authorize.Net that's inadvertantly affecting us.

It's complicated by the fact that the only reports of problems so far have been ARB related, which may be relevant or may be coincidental. We haven't seen any problems with just grabbing a nonce and immediately turning it around and doing a one-time charge, for example.

@pmgower wrote:

Also should we be concerned about doing two nonce requests to accept.js one after the other in the front end?

I don't know. It doesn't seem like there should be any problems, yet you're seeing some. Is that because of the nature of your setup where you're doing two nonce requests? Or could it possibly manifest itself on any nonce creation that's immediately followed by an ARB request using that nonce?

@steve074 reported that two quick nonce requests in a row can sometimes return the same nonce. In that scenario, I would expect that the second request would fail since the nonce has already been used.

So, there's no documented reason why you should expect the two nonce workflow to fail. However, given your current problems and the possibility of getting a duplicated nonce, I personally would want to steer clear of doing things that way.

The easiest smoothest way to do this would be this way:

1. Get a nonce

2. Send that nonce in to charge the card, with a flag set on the transaction to create a customer profile out of that transaction. There's not a great example of this in the API reference, but here's essentially what it would look like in the raw XML:

<?xml version="1.0" encoding="utf-8"?>
<createTransactionRequest xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="AnetApi/xml/v1/schema/AnetApiSchema.xsd">
  <merchantAuthentication>
    <name>login_id</name>
    <transactionKey>trans_key</transactionKey>
  </merchantAuthentication>
  <refId>123456</refId>
  <transactionRequest xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="AnetApi/xml/v1/schema/AnetApiSchema.xsd">
    <transactionType>authCaptureTransaction</transactionType>
    <amount>18.95</amount>
    <payment>
      <opaqueData>
        <dataDescriptor>COMMON.ACCEPT.INAPP.PAYMENT</dataDescriptor>
        <dataValue>eyJjb2RlIjoiNTBfMl8wNjAwMDUyRDg0N0NGOUQxQUEyNkZGRTJBQkMyM0VEQkE3OTRFRjk3QUYwMTU1OERFNEQ0M0JFQkY5QzJGMjZDQzc2RjQyRUI2NDk3QTc4QURENjFGOUI2MThERTI5RjQ5MTMxMEM1IiwidG9rZW4iOiI5NDkwMjEzNTE2MTQzOTY2OTA0NjAzIiwidiI6IjEuMSJ9</dataValue>
      </opaqueData>
    </payment>
    <profile>
      <createProfile>true</createProfile>
    </profile>
    <customer>
      <id>99999456654</id>
      <email>customer@example.com</email>
    </customer>
  </transactionRequest>
</createTransactionRequest>

Basically, the same as a regular charge with a nonce, just adding the createProfile=true, and adding either a customer id or an email to act as a key in the profile creation.

3. Send the profile ID and payment profile ID returned in step 2 in a request to create a subscription.

Re: Create ARB Subscription via Opaque Data (from Accept.js)

Aaron — Wed, 22 Mar 2017 20:16:36 GMT

Re: logging

I don't know for a fact that the built in logging in the .NET SDK even does log the full request XML. I'm just assuming it does based on the way the other SDKs work. I know we need to improve the logging in .NET specifically, but if it's not even logging the request, it needs more improvement than I thought.

Re: Create ARB Subscription via Opaque Data (from Accept.js)

steve074 — Wed, 22 Mar 2017 20:31:04 GMT

Hello @Aaron,

You describe setting up a customer profile as part of the transaction. When we did our initial development of Accept.js that was not a supported option. Has this changed recently? When I would send a request in like you describe it would either throw an unsupported error, or it would ignore the create customer flag.

No resolution to my ticket yet, but I will update this forum when I hear something from your support group.

Tim

Re: Create ARB Subscription via Opaque Data (from Accept.js)

steve074 — Wed, 22 Mar 2017 20:35:36 GMT

And to clarify my detail about the same nonce value for both nonces, the ARB subscription nonce still comes back invalid regardless if the nonce values match. Don't want that to get lost in all the confusion :)

Tim

Re: Create ARB Subscription via Opaque Data (from Accept.js)

Aaron — Wed, 22 Mar 2017 21:54:49 GMT

Thanks Tim, that was my understanding of your message. However, even if the ARB request was working correctly 100% of the time, it's never going to work for a nonce that has already been used.

Re: Create ARB Subscription via Opaque Data (from Accept.js)

Aaron — Wed, 22 Mar 2017 22:55:50 GMT

steve074 wrote:
You describe setting up a customer profile as part of the transaction. When we did our initial development of Accept.js that was not a supported option. Has this changed recently? When I would send a request in like you describe it would either throw an unsupported error, or it would ignore the create customer flag.

I don't know when that might have changed, but I tested it myself earlier just to verify that I wasn't misremembering things.

One problem is that in our API Reference, there's not a specific section on "Charge a Card Using An Accept Nonce AND Make A Profile At The Same Time." You'd have to look at the relevant fields for the profile creation on the "Charge a Credit Card" section, and couple those with the relevant fields for the nonce from the "Create an Accept Payment Transaction" section. Both of those describe uses of the createTransactionRequest API call, but neither of them are the full list of every parameter that can be sent with that call. Even when you find all of the parameters from the two sections, you still have to get them in correct order to match the schema that we're checking against. That's harder when we never show an example of a complete request to do the thing that you want to do.

So, without having experienced it myself, I can't tell whether it was really unsupported at one time, or if we just didn't have clear enough help for you to get a request formatted correctly. Either way, it definitely works now.

(Of course, I'll work on getting this documented more specfically.)

Re: Create ARB Subscription via Opaque Data (from Accept.js)

steve074 — Thu, 23 Mar 2017 14:41:53 GMT

Hello @Aaron

I added the createCustomerProfile flag and set it to true. Against the sandbox, the transaction succeeds, but the profile creation does not. It returns error E00103, "Customer profile creation failed. This payment method does not support profile creation."

In other news, we did successfully add a three second band aid delay that allows the second nonce to work in production. I will leave our support ticket open until the real problem is fixed and I'll update this thread when it is.

Tim

Re: Create ARB Subscription via Opaque Data (from Accept.js)

steve074 — Thu, 23 Mar 2017 17:11:02 GMT

New update regarding nonce values. We changed our call center payment page to include the 3 second timeout and ran a donation through. Unfortunately, even with three seconds the nonce values returned were identical. We increased the value to 10 seconds, got unique nonces, and the subscription was set up successfully.

So, I may have been incorrect about non-unique values still failing, and the timeout period needs to be longer than three seconds.

Tim

Re: Create ARB Subscription via Opaque Data (from Accept.js)

steve074 — Thu, 23 Mar 2017 17:32:54 GMT

New update. We changed our timeout value to five seconds and still got the same nonce values. Our management has determined that any longer is too long for our donor experience, so we have removed our subscription functionality from production until this is resolved.

I am attempting to escalate my ticket to a production down status, but the link to managing existing tickets is returning an ERR_CONNECTION_RESET error.

This problem is now at a critical level and we would like an escalation.

Thank you,

Tim

Re: Create ARB Subscription via Opaque Data (from Accept.js)

Aaron — Thu, 23 Mar 2017 17:42:48 GMT

@steve074 wrote:

I added the createCustomerProfile flag and set it to true. Against the sandbox, the transaction succeeds, but the profile creation does not. It returns error E00103, "Customer profile creation failed. This payment method does not support profile creation."

Nooooo! I tested it myself! I talked about with teammates yesterday, and we all agreed that it should work. I made up a quick test and tried it. It worked. So, I went ahead and posted it. Looking back over the logs of my test system, I realize now that I didn't save my modifications to my test script at the right time, and I was running transactions with regular <creditCard> elements.

An embarrassing mistake, and I deeply apologize for any time wasted.

I ran some more tests, and verified that a couple of other scenarios do work. For example:

Get a nonce.
Run the one-time transaction using that nonce in place of the creditCard data.
Create a profile from that transaction.
Create a subscription from that profile.

Or, alternatively:

Get a nonce.
Create a customer profile using that nonce in place of the creditCard data.
Charge the customer profile for the one time transaction.
Create a subscription from the profile.

Both of these are just one more API call than what I previously suggested. This second one isn't ideal, though, because you create the profile before you've seen whether the first transaction is good or not, so you'd end up with extra profiles for customers that aren't proceeding to the subscription phase.

This doesn't explain why I can create a profile directly using a nonce, but can't create it at transaction time with the createCustomerProfile flag. We've got to fix that, because clearly the system can handle it.

Re: Create ARB Subscription via Opaque Data (from Accept.js)

Aaron — Thu, 23 Mar 2017 17:45:42 GMT

@steve074 wrote:
I am attempting to escalate my ticket to a production down status, but the link to managing existing tickets is returning an ERR_CONNECTION_RESET error.

This problem is now at a critical level and we would like an escalation.

I don't know what might be going on with the ticket management page. That's unfortunate. However, I reached out to the support specialist assigned to the case, and she's escalating it to the production team for investigation right now.