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

# Payment Security

***

### Our secure Payment Gateway partners

We are securely integrated with Global Payments, Judo Pay and Braintree.

***

### Encrypted and secure transactions

Our trusted partner Payment Gateways handle payment processing and ensures that all customer payment information and personal data are encrypted using state-of-the-art encryption techniques.

With end-to-end encryption, you can confidently sell online, knowing that sensitive data is securely transmitted and stored, maintaining leading standards of security and compliance.

***

### Hosted payment window

Card details are taken on an external payment window hosted by the payment gateway, external from our servers.

This is typically embedded into your website Checkout using an `iframe`.

***

### Detect fraudulent payments

While it is impossible to entirely mitigate all fraud, our Gateway partners employ advanced fraud detection algorithms and rules to identify and prevent suspicious transactions in real time.

By proactively monitoring for signs of fraud, they mitigate the risks posed to your business and help you maintain trust with your customers.

***

### Store tokenised card details

Let your customers securely store card details in their Accounts through tokenisation. This will enable convenient Repeat Purchases and Subscription services without compromising sensitive payment information.

***

### Automatically hold Orders when payment fails

Orders are automatically held when certain rules or thresholds are met.

By default, we automatically hold orders pending payment confirmation or if the payment method is not working.

We can also define custom thresholds that trigger holds, such as Order Values exceeding a certain amount, or unusual order patterns.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.venditan.com/docs/payments/payment-security.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
