This is can be caused by one of 3 main issues.

In the majority of cases this is down to port 4430 not being open to outgoing TCP on your server. Your server hosts should be able to open this for you.

To download a port test click here and upload to your server and run in a web browser.

The second cause for this can be in relation to the password being incorrect for the gateway. If you believe this is the issue then you will need to login to the MMS and reset your gateway password (see "Changing Gateway Password" under "Merchant Management System").

The Third cause can be in relation to not properly escaping special characters in the fields passed to the gateway. Ensure the CustomerName, OrderID, OrderDescription all have htmlentites() converting any symbols.

[ASP Classic Users: Please check that the DLL’s are correctly installed] 

Please check that you are using the correct Gateway Details, and not the Merchant Management System login details. (Please see "Gateway Required Resources")

Your Gateway Merchant Account is not set up to accept payments using this card type and/or Currency. You must have a merchant account for the currency that you wish to accept (GBP/USD/EUR). If you need a new route please contact customer.service@paymentsense.com.

The details that you will require to connect the merchant account to the webshop/external system are:

1. Gateway MerchantID ("first_six_letters_of_the_company_name" "hyphen" "seven_numerics" eg. TESTPS-1234567). (also known as the merchant ID within the shopping cart integration page) this can be found in the 'Gateway Account Admin' tab, which is beneath 'User Admin' within your Merchant Management System. The gateway ID will be six letters with a hyphen and then some numbers xxxxxx-+++++++ (ECOM GBP). You will have different ones if you have more than one merchant ID.

2. Gateway Password - (test accounts this is emailed to you when you confirm your email address. Live you would have set this using the link from within the Production account email when you went live).

3. Port 4430 needs to be open on the merchants server.

4. Payment Processor Domain needs to be paymentsensegateway.com

CardName has not been submitted.

CardNumber has not been submitted.

Card ExpiryDate has not been submitted.

No card details have been submitted.

This message means that either:

The customer has taken too long processing the transaction

Or

The Time and Date is out of Sync on the server hosting the website, so this will need to be checked to ensure that the offset is correct.

This is not an error, only a warning that the browser will be navigating from a HTTPS website (SSL secured website) to the HTTP website (unsecured website).

There are two ways to fix this:

• Get an SSL for the merchant's website (Paymentsense Recommended this option).

• User the Server Result delivery method (this may require extra implementation).

This problem can be caused by a connection with the directory servers as part of the 3D Secure process. This issue is temporary and should be resolved quickly. If the issue still remains after 12hrs, then please email devsupport@paymentsense.com.

Within the Merchant Management System please navigate to Account Admin > Gateway Account Admin and un-click the "No external systems will use this account " option. You need to ensure that the correct gateway Merchant ID and Password is being used eg.Gateway MerchantID: (PAYMEN-1234567), Password: (Payment123)[numbers and letters only]

The Gateway MerchantID being used is not correct. Please ensure you are using the Gateway MerchantID and not the MerchantID used for logging into the Merchant Management System.

The Gateway MerchantID starts with the first 6 characters of the company name. This can be found in the 'Gateway Account Admin' tab, which is beneath 'User Admin' within your Merchant Management System. The gateway ID will be six letters with a hyphen and then some numbers xxxxxx-+++++++ (ECOM GBP). You will have different ones if you have more than one merchant ID.

The details that you will require to connect the merchant account to the webshop/external system are:

• Gateway MerchantID ("first_six_letters_of_the_company_name" "hyphen" "seven_numerics" eg. TESTPS-1234567). (also known as the merchant ID within the shopping cart integration page) this can be found in the 'Gateway Account Admin' tab, which is beneath 'User Admin' within your Merchant Management System. The gateway ID will be six letters with a hyphen and then some numbers xxxxxx-+++++++ (ECOM GBP). You will have different ones if you have more than one merchant ID.

• Gateway Password - (test accounts this is emailed to you when you confirm your email address. Live you would have set this using the link from within the Production account email when you went live).

• PreSharedKey - (also known as a secret key) this can be found in your Merchant Management System (MMS) in the 'Account Settings' tab.

• Hash Method - This is located under the PreSharedKey.

The MerchantID variable was not posted to the Hosted Payment Form. You should check the form variables being post to the Hosted Payment Form. This may also be caused by spelling mistakes.

The Amount variable was not posted to the Hosted Payment Form. You should check the form variables being post to the Hosted Payment Form. This may also be caused by spelling mistakes.

The CallbackURL variable was not posted to the Hosted Payment Form. You should check the form variables being post to the Hosted Payment Form. This may also be caused by spelling mistakes.

The CurrencyCode variable was not posted to the Hosted Payment Form. You should check the form variables being post to the Hosted Payment Form. This may also be caused by spelling mistakes.

The HashDigest variable was not posted to the Hosted Payment Form. You should check the form variables being post to the Hosted Payment Form. This may also be caused by spelling mistakes.

The OrderID variable was not posted to the Hosted Payment Form. You should check the form variables being post to the Hosted Payment Form. This may also be caused by spelling mistakes.

The TransactionDateTime variable was not posted to the Hosted Payment Form. You should check the form variables being post to the Hosted Payment Form. This may also be caused by spelling mistakes.

The TransactionType variable was not posted to the Hosted Payment Form. You should check the form variables being post to the Hosted Payment Form. This may also be caused by spelling mistakes.

There are a number of reasons that can cause this issue. If you are using one of our shopping carts or un-edited sample code:

• Password does not match the Gateway Password set within the Merchant Management System

• (please see "Changing the Gateway Password").

• PreSharedKey does not match that set within the Merchant Management System

• (please see "Locating the PreSharedKey/Hash Method").

• Hash Method set for the webshop does not match the Hash Method in the Merchant Management System

• (please see "Locating the PreSharedKey/Hash Method").

• or a combination of the above.

If you are using a bespoke system then the issue could be caused by one of the above issues or:

• The HashDigest being created on the merchants webshop contains variables/values that are different to those being passed to the Hosted Payment Form.

The MerchantID has not been sent to the Hosted Payment Page (please see Required Variable: MerchantID is missing).

This message means that either:

• The customer has taken too long processing the transaction

• The Time and Date is out of Sync on the server hosting the website so this will need to be checked to ensure that the offset is correct.

Unable to log you in due to Invalid login details. Please check your details and try again. If the error persists please attempt to reset your password and login with the new details.

Issue connecting to the acquiring bank. A 'log on' is likely required, which will need to be performed by our Support team.

Please contact customer.service@paymentsense.com or on 0800 103 2959 (UK) / 01 696 8393 (ROI) so that our team can complete the actions necessary to resolve this error.

The IP address of the device you are using is not permitted. Please close the browser and try again or try another device. If the issue persists then please email customer.service@paymentsense.com.

Please Perform a hard refresh on your browser by holding the CTRL key and tap F5, then attempt to login.

This is sent by the customers banks ACS (3DS Verification page) page. It means that 3D Secure was attempted but could not be completed. This could be due to a time out on the banks side or an issue with the customers banks verification system. The ACS sends back the PaRES (Payment Authorisation Result) with the status set as "A" instead of "Y".

This means that the customer failed the 3D Secure check for their card.

Click here to find out more about 3D Secure.

The customers bank have not forced them to enroll their card for 3D Secure.

Click here to find out more about 3D Secure.

3D Secure is not active on your account. If you have received an email regarding 3D Secure setup yet the message is still displayed please check it is enabled within the Merchant Management System.

This means that the customer successfully completed the 3D Secure check on their card.

There has been an issue with the 3D Secure set-up on your account. Please contact customer.service@paymentsense.com.

This represents a successful transaction.

This can be caused by 2 main reasons:

• The customers bank has blocked the card.

• There are not enough funds available in the account.

For Both of these situations the customer should contact their bank.

The billing address the customer entered does not match the billing address held by their bank.

The AVS Policy looks at the numerical values of Address line 1 and the PostCode.

For Example:

Wrong Format:

Edward Street,

Trdn jdh

Correct Format:

32 Edward Street,

TR14 8PA

Click here to find out more about AVS.

This means that the CV2 for the card that the customer was using for the transaction was incorrect. 

The CV2 is the 3 (sometimes 4) digit number found on the back of a bank card.

This is rare but means that the customer's bank was unable to authorise the transaction. The customer will need to contact their card issuer and request that they allow the transaction to go ahead.

This message occurs when trying to run a recurring/scheduled CrossReference Transaction through a standard merchant account. Please ensure these transactions are run through a recurring merchant account.

If you require a recurring account, please contact customer.service@paymentsense.com.

There is an issue with your 3D Secure set-up on your account. Please contact customer.service@paymentsense.com.

Your account is not set up to accept this card type and currency. Please contact customer.service@paymentsense.com to discuss setting up a new currency.

This is an issue with your gateway account set-up. Please contact customer.service@paymentsense.com.

There is an issue with your gateway MID and TID.

Please contact our Customer Service team on 0800 103 2959 (or customer.service@paymentsense.com) and let the advisor know that you're getting this error. 

There was an issue processing the transaction. Please ask the card holder to contact their card issuer for further information.

These messages appear 2 hours after the transaction was initially carried out. The reason for these issues are due to customers not completing 3D Secure when prompted or the PaRES not being returned to the gateway after 3DS has been completed.

Click here to find out more about 3D Secure.

This means that the gateway was busy at the time of the transaction. Please wait a few minutes and attempt the transaction again.

This means that a refund has been processed successfully.

Incorrect card details have been submitted by your customer.

TheCardName variable was not posted to the Transparent Redirect Page. You should check the form variables being post to the Transparent Redirect Page. This may also be caused by spelling mistakes.

The CardNumber variable was not posted to the Transparent Redirect Page. You should check the form variables being post to the Transparent Redirect Page. This may also be caused by spelling mistakes.

The ExpiryDateMonth variable was not posted to the Transparent Redirect Page. You should check the form variables being post to the Transparent Redirect Page. This may also be caused by spelling mistakes.

The ExpiryDateYear variable was not posted to the Transparent Redirect Page. You should check the form variables being post to the Transparent Redirect Page. This may also be caused by spelling mistakes.

The MerchantID variable was not posted to the Transparent Redirect Page. You should check the form variables being post to the Transparent Redirect Page. This may also be caused by spelling mistakes.