> For the complete documentation index, see [llms.txt](https://docs.taloflow.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.taloflow.ai/security/trust-and-governance/payment-security.md).

# Payment Security

How Taloflow processes payments and protects payment details.

### Scope

This page covers payment processing and what Taloflow does (and does not) store.

For application security controls, see [Security Overview](/security/security-overview.md).

### Payment processor

Taloflow uses **Stripe** to process payments.

Payment card details are handled by Stripe.

Taloflow does not store raw card numbers.

{% hint style="info" %}
Taloflow receives Stripe identifiers and non-sensitive card metadata.

Stripe stores and processes the underlying payment credentials.
{% endhint %}

### Stripe security (high level)

Stripe is designed to reduce the amount of sensitive payment data merchants handle.

Stripe publishes security and compliance information in their documentation.

See <https://stripe.com/docs/security>.

### What Taloflow stores

Taloflow stores only the billing metadata needed to manage your account.

This can include:

* Stripe customer and subscription identifiers
* Payment method identifiers (tokens) and non-sensitive card metadata (for example, brand and last 4 digits)
* Invoice and transaction status

### Questions and customer requests

If you need vendor documentation for a security review, send your request via the [Support Hub](broken://spaces/-MQkUmzRViVxDERN9vKk/pages/7w2btLpaU63hhnW4Dd7q).

For Stripe’s own security and compliance information, see Stripe’s documentation.


---

# 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://docs.taloflow.ai/security/trust-and-governance/payment-security.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.