Credit card number doesnt save on submit

G’day entegy,

With eWAY Client Side Encryption, the credit card number and cvn are encrypted and then the input fields are wiped so that they cannot be intercepted. The encrypted values are passed to eWAY with the transaction.

Are you seeing a problem with transactions failing? What message do you get?

cheers,
Ross

This is the error message I am getting:

Transaction failed:
Error posting eWAY request: 403, Forbidden

That sounds like a problem with the API key / password. Please check to ensure that you have the correct API key / password set in your settings.

NB: if you are using the Test mode / sandbox, you need a sandbox account with its separate API key / password / CSE (client side encryption) key.

https://go.eway.io/s/article/What-is-the-Sandbox-and-how-do-I-get-it
https://go.eway.io/s/article/How-do-I-set-up-my-Sandbox-API-Key-and-password

cheers,
Ross

Hi Ross,
I have a sandbox account have entered the correct details but I am still getting the below error.

Error posting eWAY request: 401, Unauthorized.

Any suggestions on what I need to do to fix this?

• This reply was modified 7 years, 9 months ago by entegy.

G’day entegy,

It still sounds like your API key / password for the sandbox aren’t correct. Please recheck all of your settings:

* live API key / password / CSE key in the Live settings fields
* sandbox API key / password / CSE key in the Sandbox settings fields
* Use Sandbox (testing) ticked

If all are correct, then please contact eWAY to verify that your account is correctly configured at their end.

cheers,
Ross

Hi Ross,
The live setting worked so I am not sure what was wrong with the Sandbox mode.

Did you check with eWAY? What did they say about your sandbox account?

cheers,
Ross