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

Question

Question

Forms Payment Gateway Integrations

asked on August 22, 2019

We have set up a public form via webportal that will collect application payments. We have set up both Authoriz.net and Braintree accounts.  Payments go through using their web tools, but our forms will not.  We get a very generic failure message.

Payment Failed: An error occurred during the payment transaction on <API Name>. Please refer to Authorize.Net with Payment Gateway ID: xxxxxxx

Payment Failed: An error occurred when sending verification to processor on <API Name>. Please refer to Braintree with Merchant ID: xxxxxxxxxxxxxxxx

Both Authorize.net and Braintree support wants to know the response string we are getting back, but so far I have not been able to capture it.  

I have debug level diagnostics enabled in forms, not seeing anything useful in the event viewer. I've also tried HAR trace, maybe just not adept enough to find what I'm looking for there.  Going to set up a packet trace today, I expect the traffic to be encrypted, so I'm not sure how useful it will be. 

I'm no developer, but I can read code OK. Does anyone with experience with either of these integrations have any tips for me? 

0 0

Replies

replied on November 12, 2019

Kyle, 

We have struggled with this as well, thus far I have not found the solution. In checking with Braintree it seems like nothing is even hitting their machine beyond the widget request.

0 0
replied on March 21, 2024

I am getting this same error message for most the payments submitted on our Laserfiche Form. I am not sure how to troubleshoot this, and why it's happening all the sudden after years without issue. I can't tell if I should work with Finance to contact Authorize.net, or our VAR. Without a transaction ID, it makes it hard for Finance to get any information from Authorize.net. Does anyone know why this message could come up in batches?

 

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

Sign in to reply to this post.