> This is Payabli documentation. For a complete page index, fetch https://docs.payabli.com/llms.txt — append .md to any page URL for lightweight markdown. For section-level indexes, query parameters, and other AI-optimized access methods, see https://docs.payabli.com/ai-agents.md

# Transaction Duplicated

POST 

Triggered when Payabli's duplicate detection flags a pay out transaction as a potential duplicate. The payload identifies the affected transactions and the details of the anomaly.

Notification name: `payout_transaction_duplicated`

Reference: https://docs.payabli.com/developers/webhooks/payout-transaction-duplicated

## Request

### Payload

- `anomalyType` (string, required) — Type of anomaly detected
- `anomalyStatus` (string, required) — Status of the anomaly
- `affectedIds` (string, required) — Identifiers of the affected transactions
- `gateway` (string, required) — Payment gateway
- `duplicateCount` (integer, required) — Number of duplicate transactions detected
- `createdAt` (string, required) — Creation timestamp
- `paypointId` (integer, required) — Unique identifier of the paypoint
- `vendorId` (integer, required) — The unique identifier for the vendor
- `vendorName` (string, required) — The vendor name
- `vendorNumber` (string, required) — Internal vendor identifier
- `event` ("PayoutTransactionDuplicated", required) — Event type identifier
- `paypoint` (string, required) — The name of the merchant/paypoint
- `text` (string, required) — Human-readable description of the event
- `contactUs` (string, required) — Contact information string
- `entryPoint` (string, required) — System entry point identifier