Skip to main content

Card Payments not being accepted via Sage Pay/Opayo

This article outlines possible scenarios where a payment may be declined due to an error with SagePay/Opayo

Noel Collings avatar
Written by Noel Collings
Updated over a week ago

When taking payments some will fail with an error code. A complete list of error codes can be found on Opayo's website.
​
The most commonly encountered errors and how to resolve them are below:

Code

Description

Resolution

2003

Authorisation issue

Check Opayo's system monitor and raise a case with Opayo directly if they are not reporting any issues.

2007

Payment requires 3D Secure authentication

Weighsoft has been incorrectly configured for eCommerce payments instead of Moto. This can be corrected by going to Administration, then Settings then Finance then Payment then change Account Type from eCommerce to Moto.
​
For multi-company clients they may also need changing by going to Administration, then Lookups, then Companies, click the edit icon to the left of the company. Click on the Payments tab and change the Account Type to Moto. This will need to be done for each company.

2022

The Authorisation was Declined by the bank. SCA required

3109

The BillingFirstnames field is required

Known issue that is resolved in version 5.462 can be resolved by:

  1. Hovering over administration and clicking Settings

  2. Then click Finance

  3. Then click Payments

  4. Turn off the setting Use Card Name As Default

  5. Click Save

If an error code is not being given, but the message "The HTTP service located at http://yourdomain:port/PaymentService.asmx is unavailable" is returned, please raise a case so we can investigate

Did this answer your question?