eWay Integration: We are getting the error "message to long for RSA" when submitting a form.

The form is https://www.jotform.com/build/90517515785868

We have multiple reports today of people getting errors submitting the form. On testing the error we see is "message too long for RSA" (twice) and then "Error during transactionEWAY Error : eWAY library has encountered an invalid API key or password" (see below)

We have received payments successfully today (and over the last few days) to the following forms:

https://www.jotform.com/build/201200793427852

https://www.jotform.com/build/81768058855876

and they use the same credentials for the eWay integration.

Thanks

Duncan Gillespie

Hi Duncan,

Thanks for reaching out to Jotform Support. This commonly happens if one of the credentials entered into the integration dashboard is incorrect. Please ensure you've entered the most updated credentials correctly, especially the API and password. Note that it is the API password, not your eWay account password. Can you try regenerating the API credentials for your eWay account and then try integrating the payment with your form again? We have a guide explaining How to Integrate Eway With Jotform that you can check out.

You can obtain both the API Key and Password through the API Key section of your Eway account. Please visit the eWAY API Key and Password for the steps. In the meantime, I've cleared your form caches to see if this would correct any unnecessary errors in the form. If the same thing happens again, we'll investigate it more to see if we can figure out what's going on.

Give it a try and let us know how it goes.

ThanksRene - my main concern with doing this is breaking the other two forms that are currently working. It is strange as we did not make a change to the form.

Just to check, would I need to just change the API credentials once I had regenerated them, I would not have to reconnect the integration and then add the payment element again?

Hi FriendsSchool,

Thanks for reaching us back. The other two forms that are working can be left untouched. For the form that did show the error, you can apply the new API key and password in the integration settings. There's no need to add the payment integration into the form again, just reconnect. Please refer to the screenshot below:

If you have questions, please let us know.

Thanks Kenneth. The other forms have the same credentials (at least for the text that is displayed in the boxes you have highlighted and the Client-side Encryption Key.

I have updated the form with a separate set of credentials and no longer get the error, but the form does not submit.

Hello FriendsSchool,

Are you still getting an invalid API Key error? Since you are using the same credentials for the other forms that are working, can you please try switching to a different payment method and then switch back to eWay to refresh the connection?

1. Open your form in Form Builder and click on the Add Form Element menu on the left side of the page.
2. Under the Payment tab, click on the Three Dots icon next to the Payment method you used and click on Switch to Another Gateway. 
3. Choose a payment method (Purchase Order) and click on Use Selection.
4. Now, repeat the same steps to switch to eWay and add the same credentials.

Keep us updated and let us know if you need any more help.

I am using different credentials from the other two forms as I would have to regenerate the API Password if I wanted to use the same API Key and at this stage I am reluctant to do that.

eWay allow us to have two API Keys, so I set up a new one.

There is no longer either of the errors, I press the "Submit" button and nothing happens.

I have tried to follow the steps to switch to a different payment method, but the three dots do not appear next to eWay (or any other payment method) so perhaps that is related to the issue?

Hi Duncan,

Thanks for getting back to us. I checked both of your forms, but I can see the 3 dots icon to switch to a different gateway.

Can you please try clearing your browser's cache and cookies or using a different browser in switching to a different gateway and switching it back to eWay? Once switched back, please add your eWay credentials again and check if the form is not submitting when pressing "Submit".

Let us know how it goes.

Thanks for the support.

In the end I did not need to remove the payment element from the form. I was able to set up a second API Key and Password in eWay, but the first time I did it, I made the password two long (the limit is 20 characters). After fixing this and updating the details in the payment settings the payment worked without the error.