> For the complete documentation index, see [llms.txt](https://doc.threatreaper.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.threatreaper.ai/user-guide/payments_billing.md).

# Payments\_Billing

**Menu:** Settings > Payments.

This is where your organisation manages how it pays for LockThreat and reviews past invoices. Only users with billing permissions can make changes here.

## 17.1 How to configure it

### Add a payment method

* **Credit/Debit Card:** Cardholder Name, Card Number, Expiry Date (MM/YY), CVC, and an option to set it as default.
* **Bank Account:** Account Holder Name, Routing Number (9 digits), Account Number, Account Type (checking/savings), and an option to set it as default.

{% hint style="info" %}
Card details are processed by a PCI-compliant payment provider and are never stored on LockThreat's servers.
{% endhint %}

### Billing settings

Company Name, Billing Email (required), Tax ID, billing address, and Country, plus preferences for Auto Pay, email notifications, and invoice format (PDF/CSV/JSON).

## 17.2 Errors you might see and how to fix them

| **Message**                                                  | **What it means**                             | **What to do**                                                                            |
| ------------------------------------------------------------ | --------------------------------------------- | ----------------------------------------------------------------------------------------- |
| "Invalid card number"                                        | The card number isn't a valid 16-digit number | Re-check the number you entered                                                           |
| "Invalid expiry date"                                        | Expiry isn't in MM/YY format                  | Enter the expiry as shown on your card                                                    |
| "Invalid CVC"                                                | The security code is too short                | Re-enter the 3–4 digit code from your card                                                |
| "Routing number must be 9 digits" / "Invalid account number" | Bank details don't match the expected format  | Double-check the numbers with your bank                                                   |
| "Failed to add payment method"                               | The payment provider rejected the request     | Confirm your details are correct, or try a different payment method                       |
| An invoice shows status **Failed** or **Past Due**           | A scheduled payment didn't go through         | Update your payment method, then contact your administrator or LockThreat billing support |

## 17.3 What success looks like

VISA •••• •••• •••• 4242 Expires 12/28 ✓ Default Payment Method

### Payment history

| **Date**   | **Description**      | **Amount** | **Status** | **Invoice** |
| ---------- | -------------------- | ---------- | ---------- | ----------- |
| 2026-10-10 | Monthly Subscription | $99.00     | Paid       | Download    |
| 2026-09-10 | Monthly Subscription | $99.00     | Paid       | Download    |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://doc.threatreaper.ai/user-guide/payments_billing.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.