---
title: Troubleshooting
slug: troubleshooting
docTags: 
createdAt: 2024-06-04T12:30:57.967Z
---

# Troubleshooting Common Errors

## Important to Consider

- How your app handles negative flows
- Your customer's experience should a negative flow occur:
  - Logic to communicate error messages
  - Customise how your app responds
- How to maintain application consistency

It is advised to generate:

- Successful
- Declines
- Errors

If you need to familiarise yourself with any of our** key terms**, see [Key Terms](docId\:S_8hOAMytkgY13t0P657-).

***

## Common Errors

| **Code** | **Error Description**                                                                                                                                                                                    | **Possible Reason**                                                                                                                                 | **Resolution**                                                                                              |
| -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------- |
| 403      | Sorry, but we were unable to authenticate your request. Please check your details and try again.                                                                                                         | The Incorrect:<br />- API Token<br />- API Secret or<br />- endpoint<br />has been sent.                                                            | Check you have the correct environment (live or sandbox) for your:<br />- API Token<br />- API Secret       |
| 86       | Sorry, this payment has been stopped as it is a duplicate transaction.                                                                                                                                   | **yourPaymentReference** has already been used.<br />This value should be unique in order to protect your customers against duplicate transactions. | Check you are providing a unique **yourPaymentReference**.                                                  |
| 154      | Your provided consumer reference is incorrect, please check your details and try again.                                                                                                                  | The incorrect **yourConsumerReference** has been used when making a token payment.                                                                  | **yourConsumerReference&#x20;**&#x6D;ust match the original reference when the token was initially created. |
| 191      | The purchase cannot be completed at this time. For additional information please contact your card issuer at 0345 266 8634<br />"Message": "Unable to process transaction. Too many challenge attempts". | The card issuer has declined this transaction.                                                                                                      | Please retry, or use a different card.                                                                      |
| 70       | Sorry, but it looks like the card token specified is not valid. Please check your details and try again.                                                                                                 | The **cardToken&#x20;**&#x61;n&#x64;**&#x20;yourConsumerReference** are incorrect.<br />                                                            | Check the **cardToken&#x20;**&#x61;nd **yourConsumerReference** are valid.                                  |

***

### Network Error

If you initiate a payment, but do not receive a payment response confirmation due to a network error or internet outage, try the following to check the **transaction status**:

- Use the **GET&#x20;**`/transactions` endpoint from Judopay’s Transaction API and include `yourPaymentReference` and `yourConsumerReference` in the request.
  This will return a list of transactions associated with those references.
  For more information, see [Get Transactions](https://docs.judopay.com/api-reference/index.html#/Receipts/get_transactions).

- Use the **GET &#x20;**`/webpayments/{reference}` and include the **paymentSession&#x20;**&#x72;eference returned in response to the creation of the session.
  This will return the transaction associated with that payment session.
  For more information, see [Get Transactions with paymentSession](https://docs.judopay.com/api-reference/index.html#/Payment%20Sessions/get_webpayments__reference_).

- Implement **Webhooks**.

  Webhooks notify your system when a transaction or event has taken place.
  The benefit of using webhooks means you do not need to pull information from the Judopay API for every event.

  You can set up webhooks from the Judopay Portal.

  For more information on setting up webhooks, see [Enable Webhooks](docId\:mQjiiZXmCRo1cpvAUaWuD).

Example Web SDK network error message:

:::BlockQuote
"\{
&#x20;   "name":"Error",
&#x20;   "message":"Network Error"
}"
:::

***

## Helping Us...

Before you contact our support teams, make sure you have captured the following:

- The **judoId**.
- The sandbox **API Token and Secret**.
- The **receiptId** of the transaction.
  - This is Judopay's unique reference for the transaction.
- The specifi&#x63;**&#x20;error code**(s) returned.
  - For example: 154 | 77 | 175 | 182
- **yourPaymentReference**
  - This is your unique reference for the transaction.
- Time-stamp when the issue occurred.
- Any **screen shots** showing the error.

These will help us investigate your issue.