LessChurn Docs

Errors

Did you know we'll do all this for you?

We'll screenshare and walk you through every step! Ask for help.

Here's a list of the error codes you can see on the confirmations page, along with explanations of what the codes mean.

1001 or 1002 - An internal error has occurred. We've been notified.

Explanation: An internal error has occurred within LessChurn itself. We're notified when this happens and we try to resolve the issue as quickly as possible. We'll reach out to you as soon as things are back to normal.

Action required on your end: None.

2001 - The Stripe Customer ID was not sent.

Explanation: The URL you have used for the LessChurn iFrame is missing a customer_id parameter.

Action on your end: On your website, edit the URL of your LessChurn iFrame to include the customer ID of the current customer (as shown in Stripe or Braintree). Go to the LessChurn settings page if you need to copy the iFrame snippet again.

2002 - We couldn't find a customer with the ID you sent us.

Explanation: We couldn't find the customer from the customer_id parameter you specified in the iframe.

Action on your end: On your website, edit the URL of your LessChurn iFrame to include the customer ID of the current customer (as shown in Stripe or Braintree). Go to the LessChurn settings page if you need to copy the iFrame snippet again. Feel free to get in touch with us, we'd love to help out.

2003 - This LessChurn business is not connected to a payment gateway.

Explanation: You don't have a connection to your gateway set up.

Action on your end: Go to Lesschurn and you will be prompted to connect to your gateway. Follow the instructions there and you should be all set.

2005 - This business does not have a redirect URL set up.

Explanation: You haven't configured a redirect URL for your business.

Action on your end: When a customer of yours selects one of the options from the form and we confirm that everything went well, we redirect them to a URL that you have specified in your settings. Alternatively, you can specify a custom redirect URL for each individual option in the churn form, but you can't skip any. For the time being, this step is mandatory.

2006 - The API key was not sent.

Explanation: The iFrame's URL does not have an api_key parameter.

Action on your end: On your website, edit the URL of your LessChurn iFrame to include the api_key. Go to the LessChurn settings page if you need to copy the iFrame snippet again. You will also find the API key listed there. Feel free to get in touch with us, we'd love to help out.

2007 - The API key is invalid.

Explanation: The iFrame's URL does not have a valid api_key parameter.

Action on your end: On your website, edit the URL of your LessChurn iFrame to include the correct api_key. Go to the LessChurn settings page if you need to copy the iFrame snippet again. You will also find the API key listed there. Feel free to get in touch with us, we'd love to help out.

2008 - This customer has already been deleted from your payment gateway.

Explanation: The customer you're trying to load the iFrame for has alredy been deleted on Braintree/Stripe.

Action on your end: What this most likely means is that you didn't delete the user's account when we sent you a webhook that said the customer deleted. You will need to manually delete the user from your system. Please respond with an HTTP status other than 200 if you failed to delete the customer from your end. That tells us we need to stop any action on our end and we can let the user know their account wasn't actually deleted.

2010 - Gateway api key is no longer authorized (but LessChurn thinks it is).

Explanation: Braintree/Stripe reported your API key is no longer valid, but LessChurn thinks it is.

Action on your end: Go into your settings and remove the connection, then reconnect to your gateway.

3001 - We tried to send you a webhook, but failed due to an internal error on your end.

Explanation: When we sent you the webhook, there was an error on your end since you responded with a status other than 200. The customer has not been deleted.

Action on your end: It's up to you to fix this issue, but feel free to get in touch with us if you're confused, we'd love to help out.

3003 - We tried to send you a webhook, but failed due to a timeout. We've been notified.

Explanation: We couldn't send you a webhook because of a timeout.

Action on your end: We've been notified, and will be looking into this, but you need to review any logs or error notifications on your end as well. Feel free to get in touch with us if you're confused, we'd love to help out.

3002 - We tried to send you a webhook, but bailed out because your SSL certificate isn't valid.

Explanation: We tried to send you a webhook but found that your SSL certificate is invalid for some reason. As a result, we never sent any data and the customer has not been deleted.

Action on your end: It's up to you to fix this issue, but feel free to get in touch with us if you're confused, we'd love to help out.

4001 or 4002 - There was an error while communicating with your payment gateway. We've been notified.

Explanation: An error occurred when we tried to interact with your payment gateway (Stripe or Braintree). We're notified when this happens and we try to resolve the issue as quickly as possible. We'll reach out to you as soon as things are back to normal.

Action required on your end: None.

Did you know we'll do all this for you?

We'll screenshare and walk you through every step! Ask for help.