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

# checkout and security

TrendSwap partners with **Stripe** — the global leader in digital payments — to deliver bank-grade security and frictionless payment processing for creators worldwide.

***

## Payment Architecture & Security

* **PCI-DSS Level 1 Compliance**: All payment card details are encrypted directly in the user's browser using Stripe Elements. Credit card numbers, CVVs, and expiration dates never touch or pass through TrendSwap servers.
* **Supported Payment Methods**:
  * Visa, Mastercard, American Express, Discover, JCB, Diners Club.
  * Apple Pay & Google Pay (1-click checkout on mobile devices).
  * Link by Stripe for instant 1-tap checkout.
* **Zero Recurring Charges**: Every transaction on TrendSwap is a one-time charge. We will never automatically renew or charge your card without your explicit interaction.

***

## Instant Fulfillment

{% stepper %}
{% step %}

## Stripe emits an authenticated webhook

Stripe emits an authenticated webhook (`checkout.session.completed`) to TrendSwap's payment worker.
{% endstep %}

{% step %}

## Verify the webhook signature

The webhook handler verifies the cryptographic signature (`stripe-signature`).
{% endstep %}

{% step %}

## Credit the user's account

Credits are credited to the user's account within 500 milliseconds.
{% endstep %}

{% step %}

## Send an itemized invoice receipt

An itemized invoice receipt is emailed directly from Stripe to the customer's billing address.
{% endstep %}
{% endstepper %}


---

# 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.trendswap.app/pricing/checkout-and-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.