# Overview

![](/files/8qhrQTao3FeQxRJ5wtt6)

TxShield is a payment processing & fraud/chargeback prevention, handling & response system. Along with over 300+ payment processor integrations to processors all over the world, it has a heavy emphasis on fraud/chargeback prevention (active and passive), handling & response. Systems have been designed to mitigate the potential for fraudulent transactions to be processed and chargebacks to be lodged by customers.

### TxShield Documentation

[TxProcess - Transaction processing](https://docs.payshield.ai/transaction-processing/)

[TxAlerts - Pre-dispute alerts](https://docs.payshield.ai/txalerts-dispute-alerts/)

### Transaction Processing

TxShield can process transactions for every major card platform;

* Visa
* Mastercard
* JCB
* CUP
* Amex
* Diners

TxShield is built to hand every variety of transaction workflow;

* Synchronous
* Asynchronous
* Redirect

### Fraud/chargeback mitigation

TxShield's fraud/chargeback modules include:

**Dispute Alerts**\
The alert module receives notifications that a dispute is about to be raised against your account by a cardholder, and lets you respond to the dispute before it becomes a chargeback. The alerts can be managed from our dashboard, or integrated into your CRM.

**Risk-Based Assessment**\
With integrations to many fraud detection and risk-based assessment platforms, TxShield can return to you a fraud score for the transaction, allowing you to setup automated rules based on the result.


---

# Agent Instructions: 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:

```
GET https://cliq.epspci.com/overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.