- DavidBrandsAsked on April 24, 2015 at 04:47 PM
I am using the paypal integration to receive payment to our Paypal (not Pro) account.
We are receiving payments fine, but they are being received by paypal as an Authorization, which we later have to go and manually capture.
What do I have to do to have Jotform submit the payment as a sale?
I've contacted paypal support level 2 and they've confirmed that the Payment action = Authorization in their logs. (I can submit those to you if required.)
The form is located here: http://www.jotform.ca/form/50774335345255
Thank you for your help!
- BenAnswered on April 24, 2015 at 05:40 PM
Based on what you are saying you seem to have the Authorization payments turned on, but looking at your jotform it seems that it is actually turned off - so the payment should be direct.
If you have changed that yourself you should now be OK. If you did not change anything then you should try setting it to Yes and then back to No again, just to make sure it is saved.
You can see how to come to this option How to Enable Payment Authorization
Do let us know if you have any questions in regards to this or if you continue to experience any issues and we would be happy to assist.
- DavidBrandsAnswered on May 27, 2015 at 02:41 PM
I followed the steps prescribed, but these transactions are still being submitted as Auth only, forcing me to catpure them manually in Paypal.
A (lengthy) call to Paypal level 2 support confirms that these transactions are being sent as Auth's only to Paypal.
Can you please assist? This appears to be a bug and (for once) not just a user error.
- JotForm SupportMikeAnswered on May 27, 2015 at 04:45 PM
I was able to reproduce the issue with the PayPal Express integration. The payments are being sent in Authorization mode for some reason. A bug report ticket has been attached to this thread and escalated to our Development Team. We will let you know when we have any updates.
In the meantime, you can switch to our standard PayPal integration. It should fix the issue.
- JotForm SupportpaulsimpsonAnswered on May 31, 2015 at 04:01 AM
This problem has now been fixed. Thank you for your patience and apologies for any inconvenience it has caused.