You are viewing limited content. For full access, please sign in.

Question

Question

Forms: Authorize.Net - Enabling Transaction Details API

Forms
Updated July 18, 2019
asked on July 1, 2019

Hi all,

A client's Forms process is not receiving return values from Authorize.Net upon successfully completing a transaction. We can see the transaction when we log into Authorize.Net, but the fields to which we're defaulting Transaction ID and Amount (tokens from the payment gateway in Forms) are empty.

According to the Admin Guide:

Note: Before using an Authorize.Net payment gateway, enable the Transaction Details API. You can do this by signing in to your Authorize.Net account and enabling the API in Account > Settings > Transaction Details API.

But the client reports that this setting doesn't exist and isn't sure what it means for LF Forms.

Any suggestions for getting transaction details from Authorize.Net into Forms?

Thanks,

Rob

0 0

Replies

replied on July 2, 2019

The user interface of Authorize. Net was changed recently, I can't find the settings as well. It was documented from https://account.authorize.net/help/Account/Settings/Security_Settings/General_Settings/transaction_details_api.htm but there is no such settings any more, we need to contact Authourize.Net to see how to enable it now.

1 0
View 6 previous replies
replied on July 2, 2019

Hi Xiuhong,

Thanks for the reply, I will relay this to the client and wait to hear more about enabling it.

Thank you!

Rob

0 0
replied on July 2, 2019

Hi Xiuhong,

The client got back to me explaining that the reached out to Authorize.Net and were pointed to the following development documentation:

https://developer.authorize.net/api/reference/index.html#payment-transactions

This isn't exactly relevant to Forms end users, so any information you have will be greatly appreciated.

Thanks,

Rob

0 0
replied on July 3, 2019

I checked by creating a new Sandbox account(refer to https://developer.authorize.net/hello_world/testing_guide/) and I didn't make any change to enable the API. By default, the fields defaulting to {/dataset/_paymentAmount} and {/dataset/_transactionId} can get values and the amount and transaction ID also appear in the step history. 

It seems Authorize.Net changed the UI to get rid of the Account > Settings > Transaction Details API as they always enable it now.

Can you please ask the customer to test with an Sandbox account as well?

0 0
replied on July 3, 2019

Hi Xiuhong,

Thank you for the information. I will pass it along to the client and let you know what happens.

Have a great weekend,

Rob

0 0
replied on July 5, 2019

Hi Xiuhong,

The client reported that the Authorize.Net transaction values are coming through when tokens are dropped in the body of an email service task, but not when they're used as default values on a form in the relevant process that's used to gather transaction data for generating reports:

The intent of the form is specifically to collate transaction data, it is never assigned to a user. I'm not sure if impacts anything.

Is there any reason these values would be available to/exposed through an email service task, but not when used as default values on the transaction report form?

Thank you,

Rob

0 0
replied on July 11, 2019

Are the fields used to collate transaction data only appear for that specific form? If those fields are used in other forms at earlier steps then the default values will not take effect as there are values for the fields pass from previous steps. Can you check with a simple process such as a two steps process:

1. Message start event with form 1 with payment enabled

2. User task with form 2 that contains fields use {/dataset/_paymentAmount} and {/dataset/_transactionId} as default value

Run the process and check whether there are values for the fields when open the user task. 

If you can't reproduce with the simple process but can reproduce with the original process, please record a video to illustrate the issue and export the process and open a support case for further trouble shooting. 

0 0
replied on July 11, 2019

Ok, I will relay this to the client. Thanks!

0 0
replied on July 11, 2019

Hi Xiuhong,

Just want to update you that we've created an LF Support case for this issue, and wanted to let you know that adding a user service task after the starting form submission/payment causes those values to default as expected. The client has sent videos/logs along for consideration.

The client's issue is that they do not want to have a user click "Submit" for every transaction that they receive just to facilitate reporting on those values.

Thanks!

0 0
replied on July 18, 2019

We confirmed it is expected behavior as the variables used in default value will only be parsed when load the form.

If they want to generate reports for the payments, there are two possible solutions:
1.    Add a user task after the message start event assign to initiator and enable auto load next task for the message start event, and they can make the second form as confirmation for end user by setting the fields to read-only with default value using payment variables(https://www.screencast.com/t/vTJOl8fy0or)
2.    Add a Workflow service task after the message start event and retrieve the payment variables from workflow the set back Forms field variables which will generate a submission(the workflow service task need to wait for the workflow to finish before proceeding)
 

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...