> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fraudeg.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect FraudEG with Payment and Identity Platforms

> Integrate FraudEG with payment processors, digital wallets, identity providers, and communication platforms to unify fraud prevention across your stack.

FraudEG sits between your user-facing application and your financial rails, which means it can only be as effective as the data flowing into it. Integrations solve this by connecting FraudEG directly to the systems that originate transactions, verify identities, and route money — enriching every fraud signal with real context rather than relying on a single data source. The broader your integration footprint, the more accurate and decisive FraudEG's risk scoring becomes.

<Note>
  All FraudEG integrations use encrypted, authenticated connections. Data in transit is protected with TLS 1.2 or higher, and each integration authenticates using short-lived tokens or rotating API keys stored in FraudEG's secrets vault. No credentials are stored in plaintext.
</Note>

***

## Integration categories

<CardGroup cols={2}>
  <Card title="Payment Processors" icon="credit-card">
    Stripe, Adyen, Braintree, Checkout.com
  </Card>

  <Card title="Digital Wallets" icon="wallet">
    PayPal, Apple Pay, Google Pay, Alipay
  </Card>

  <Card title="Bank Transfer Rails" icon="building-columns">
    ACH, SEPA, FPS, SWIFT
  </Card>

  <Card title="Identity Providers" icon="id-card">
    Jumio, Onfido, Persona
  </Card>

  <Card title="Communication Platforms" icon="bell">
    Twilio, SendGrid, Slack, PagerDuty
  </Card>

  <Card title="Crypto & Blockchain" icon="link">
    Chainalysis, Elliptic
  </Card>
</CardGroup>

***

## Payment processors

Connecting a payment processor lets FraudEG intercept transaction data before authorization and feed its risk decision back to the processor in real time.

**Supported:** Stripe, Adyen, Braintree, Checkout.com

| Data direction          | What flows                                                                                                           |
| ----------------------- | -------------------------------------------------------------------------------------------------------------------- |
| **Processor → FraudEG** | Card BIN, billing address, 3DS data, device fingerprint, transaction amount and currency, merchant category code     |
| **FraudEG → Processor** | Risk decision (`allow`, `challenge`, `block`), risk score, matched signals, recommended 3DS exemption or enforcement |

When you connect Stripe, for example, FraudEG registers as a Radar extension. Every charge passes through FraudEG's scoring engine before Stripe finalises the authorization outcome.

***

## Digital wallets

Wallet integrations give FraudEG visibility into tokenised payment flows where raw card data is not present.

**Supported:** PayPal, Apple Pay, Google Pay, Alipay

| Data direction       | What flows                                                                            |
| -------------------- | ------------------------------------------------------------------------------------- |
| **Wallet → FraudEG** | Device trust signals, payment token metadata, wallet account age, buyer history flags |
| **FraudEG → Wallet** | Risk decision, challenge flag                                                         |

***

## Bank transfer rails

For ACH, SEPA, FPS, and SWIFT transactions, FraudEG validates payer identity and detects account-level fraud patterns such as first-party fraud, account takeover, and mule account behaviour.

**Supported:** ACH (US), SEPA (EU), FPS (UK), SWIFT (international)

| Data direction     | What flows                                                                                |
| ------------------ | ----------------------------------------------------------------------------------------- |
| **Rail → FraudEG** | Sort code / routing number, account number (hashed), beneficiary details, transfer amount |
| **FraudEG → Rail** | Risk decision, velocity flags, payer identity match confidence                            |

***

## Identity providers

FraudEG's built-in KYC layer is augmented when you connect a document verification provider. Verification outcomes feed directly into the risk score and can trigger rules or workflows.

**Supported:** Jumio, Onfido, Persona

| Data direction                  | What flows                                                                                                                                    |
| ------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
| **Identity provider → FraudEG** | Document verification result, liveness check outcome, extracted document data (name, DOB, country), fraud signals from the provider's network |
| **FraudEG → Identity provider** | User identifier, session context                                                                                                              |

***

## Communication platforms

These integrations power the notification and alerting actions available in workflows.

**Supported:** Twilio (SMS OTP), SendGrid (transactional email), Slack (channel alerts), PagerDuty (incident escalation)

| Data direction         | What flows                                                              |
| ---------------------- | ----------------------------------------------------------------------- |
| **FraudEG → Platform** | Alert message, event payload, templated notification content            |
| **Platform → FraudEG** | Delivery status, message SID (Twilio), bounce or open events (SendGrid) |

***

## Crypto and blockchain monitoring

For platforms that process cryptocurrency transactions, FraudEG integrates with blockchain analytics providers to screen wallet addresses, detect mixing or tumbling activity, and comply with travel rule requirements.

**Supported:** Chainalysis, Elliptic

| Data direction                     | What flows                                                                             |
| ---------------------------------- | -------------------------------------------------------------------------------------- |
| **Blockchain analytics → FraudEG** | Wallet risk score, exposure categories (darknet, sanctions, ransomware), entity labels |
| **FraudEG → Blockchain analytics** | Wallet address, transaction hash, asset type                                           |

***

## How to set up an integration

<Steps>
  <Step title="Open the integrations catalogue">
    Go to **Platform → Integrations**. You'll see all available integrations organised by category.
  </Step>

  <Step title="Select a provider">
    Click the provider you want to connect. The detail page shows what data is exchanged and any prerequisites (such as a Stripe Radar plan or an Onfido API key).
  </Step>

  <Step title="Authenticate">
    Paste in your API key or OAuth credentials for the provider. FraudEG stores these securely in its secrets vault — you can rotate them at any time without downtime.
  </Step>

  <Step title="Configure data flow">
    Choose which events should be sent to FraudEG and what decisions or signals FraudEG should write back. Most integrations have sensible defaults you can accept immediately.
  </Step>

  <Step title="Test in sandbox">
    Use a sandbox event to confirm the integration is receiving and returning data correctly. Check **Platform → Integrations → \[Provider] → Logs** to inspect individual requests and responses.
  </Step>

  <Step title="Enable for production">
    Once your sandbox tests pass, toggle the integration to **Production**. Ensure you have entered production credentials, not test keys from the provider.
  </Step>
</Steps>

<Tip>
  Always validate a new integration end-to-end in the sandbox before enabling it in production. Use FraudEG's integration test tool — available on each provider's detail page — to fire a synthetic event and verify the full data round-trip without touching real transaction data.
</Tip>

***

## Custom integrations

If your payment processor, identity provider, or internal tool is not in the native catalogue, you can build a custom integration using FraudEG's webhooks and REST API.

* **Inbound:** Send event data to `POST https://api.fraudeg.com/v1/events` with a structured payload. FraudEG scores it and returns a decision synchronously.
* **Outbound:** Configure a webhook URL in **Platform → Integrations → Custom Webhook** to receive real-time event notifications from FraudEG.

This approach gives you full flexibility to connect any system that can make HTTP requests or receive webhook callbacks.