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

Question

Question

Forms Payment Collection - Declines and Optional

Forms
Updated October 27, 2021
asked on August 22, 2019

We are using Forms 10.3.1.690 and are relatively new to the process.  We've created several public portal forms and recently started adding ones that collect payment.  We use Authorize.net and thought we had everything set up correctly.  However, we've run into two problems:  (1) Forms is allowing users to submit the form even though the payment was declined by Authorize.net and (2) there doesn't appear to be a way to hide the payment section of the form when payment isn't required.

Is there a way to make the payment required so the form cannot be submitted when the payment is declined?  We didn't see any settings for it in the payment collection portion of the Forms process.

 Can we hide the payment collection when payment is not necessary?  Alternatively, can we create another "payment form" that is opened and populated with values from the first form when payment is required?

We waited a long time for Forms to start collecting payments, but it certainly seems to be missing some very basic functionality.

Thanks.

1 0

Replies

replied on February 5, 2020

Not sure if your still looking for it, but I can help you with hiding the payment collection portion when not necessary. The following code is what I'm using until a user enters a reference number (which triggers a lookup but that's just my thing).

 

$('#authorizeNetPaymentBlock').hide();
  
  $('#Field8').on('change', function(){
    
    if($('#Field8').val() != 0){
      
    $('#authorizeNetPaymentBlock').show();
    
    }
    else{
      
      $('#authorizeNetPaymentBlock').hide();
      
    }
    
  });

The first line hides the payment block. The second says: when the value of Field 8 changes check to see if the value is not equal to 0. If it is different than 0 (my default value for it) then show the payment block.

You can change the code to fit your needs. Maybe you want it to trigger on a radio button being selected, or whatever condition. As of writing this post, the payment collection block selector for Authorize.Net is $('#authorizeNetPaymentBlock').

 

I'm also looking at not allowing the form to submit until payment has been approved first. But it may not be possible given the way that Laserfiche Forms submits information. If I find a solution to it I'll try to remember to post it here, if you still need it.

 

Let me know if you have any issues with the code above.

0 0
View 5 previous replies
replied on April 1, 2021

I am having this issue also. It seems odd that there's not an easy workaround for this problem. Any one have any insight on how to fix?

0 0
replied on April 2, 2021

Unfortunately, we moved away from Authorize.Net but from my experience with it there isn't an easy way to use the built-in Authorize.Net payment and modify values based on the status of the transaction. It seems like Forms doesn't get the status from Authorize.Net, they only post the transaction and Authorize.Net handles what happens to the transaction if it's declined.

 

You can get status codes from Authorize.Net, but only after the form has been submitted, so it's not entirely useful unless you use some JavaScript on the confirmation page to react to the status code accordingly. However, it would require some possibly heavy testing to make sure it does what you want it to.

 

Sorry, wish I had better news. I haven't got a chance to test out 11 with Authorize.Net, but it might be more of the same. Maybe now that 11 has been released they can check out the options they offer with the payment gateways they have. Good Luck. If you need further advice on this I'll be happy to help.

0 0
replied on April 5, 2021

Thank you for sharing. Does Braintree do the same thing? It seems kind of odd to me that there's no way to verify payment. It puts on the onus on staff to notice that payment wasn't accepted before completing the process. Not super helpful when we're trying to automate and make things easier!

0 0
replied on April 7, 2021

I think Braintree does. It comes down to the way the interface for Forms works. It's less about which payment gateway you're using and more that Laserfiche doesn't have a way to verify the transaction until after the form has been submitted. You can get the status in Workflow after the fact, but it would require another form for that user, so it could get very complicated fast. Good luck with this!

0 0
replied on October 20, 2021

Hi All, we built a work process for every form wit ha payment to verify the transaction status, and notify folks.  It also won't kick off our internal processes unless it is verified as successful:

This has been nice because it doesn't require our staff to do anything.  I haven't personally tried the script to variably hide the payment box.  We are on 10.4.2.  

1 0
replied on October 20, 2021

Thank you so much! I will have to try adding this to ours as well. Really appreciate you sharing your solution. 

0 0
replied on October 27, 2021

John-Paul - thanks for the post.  We would love to see your solution.  Is a copy of your process posted somewhere we can access?

0 0
replied on October 27, 2021

I do not have a stand alone process for this step in particular, but if you click on the image I attached to the previous post, it shows you the transaction statuses that are available as variables.  The exclusive gateway is only looking at the transaction variables, if that clarifies it a bit, too.  Basically, the process either moves along (a successful payment), or tells the submitter they need to try again because the payment failed.  I should note that this all occurs after submission.  So it requires they provide an email address at some point, and that hey check their email!

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

Sign in to reply to this post.

Details
Related Posts
Loading ...