# FraudLabs Pro AI integration on Definable

> FraudLabs Pro is an online payment fraud detection service that helps merchants minimize chargebacks and maximize revenue by detecting fraud across various payment methods.

## What this connects

FraudLabs Pro is an online payment fraud detection service that helps merchants minimize chargebacks and maximize revenue by detecting fraud across various payment methods.

Vendor: https://www.fraudlabspro.com

## Tools available

**8** tools available. First 8:

- `FRAUDLABS_PRO_CREATE_ACCOUNT` — Create FraudLabs Pro Reseller Sub-Account — Creates a new FraudLabs Pro user account under a reseller account. Requires a Reseller API key (not a regular API key). Use this action to provision new sub-accounts for customers when operating as a FraudLabs Pro reseller. Returns account credentials (username and password) upon successful creation. Prerequisites: - Must have a FraudLabs Pro Reseller account (apply at https://www.fraudlabspro.com/reseller/program) - Requires valid Reseller API key (different from standard FraudLabs Pro API key) - All required fields must contain valid data matching FraudLabs Pro validation rules Important: - Phone numbers should contain only digits (no +, -, spaces, or parentheses) - Country must be valid ISO 3166-1 alpha-2 code (e.g., US, GB, CA) - Industry must be a valid ID from 1-14
- `FRAUDLABS_PRO_FLP_FEEDBACK_ORDER` — FLP Feedback Order — Submit fraud screening feedback to improve FraudLabs Pro's machine learning model. Use this after reviewing a screened order to mark it as approved, rejected, or blacklisted. This feedback trains the algorithm to better detect fraud patterns in future transactions.
- `FRAUDLABS_PRO_FLP_SCREEN_ORDER` — FraudLabs Pro Screen Order — Tool to screen orders for fraud. Use when you need to assess transaction risk before fulfillment.
- `FRAUDLABS_PRO_GET_ORDER_RESULT2` — Get FraudLabs Pro Order Result (v2) — Tool to retrieve an existing transaction from FraudLabs Pro fraud detection system using the v2 API. This API is only available for paid plans.
- `FRAUDLABS_PRO_GET_SMS_VERIFICATION_RESULT` — Get SMS Verification Result — Verify an OTP (one-time password) received via SMS. Returns 'Y' if the OTP is valid, 'N' if invalid or expired. Must be called after using Send SMS Verification to obtain a transaction ID.
- `FRAUDLABS_PRO_SEND_SMS_VERIFICATION` — Send SMS OTP Verification — Sends an SMS message containing a one-time password (OTP) to verify a user's phone number. The API generates a random 6-digit OTP, replaces the <otp> placeholder in your message template, and sends the SMS to the recipient. Returns a transaction ID that you must use with the Get SMS Verification Result action to verify the OTP the user enters. Testing: Use phone number '+11' for sandbox testing (no credits deducted). For verification testing with sandbox number, use OTP '123456'.
- `FRAUDLABS_PRO_SUBSCRIBE_PLAN` — Subscribe Reseller Plan — Tool to subscribe a reseller account to a specific plan. Use after obtaining a reseller API key and selecting a plan. Example: Subscribe user "john_doe" to the MICRO plan.
- `FRAUDLABS_PRO_WEBHOOK_ORDER_STATUS_CHANGED` — Test Order Status Changed Webhook Delivery — Tool to send a test webhook payload to the provided callback URL for FraudLabs Pro order status change notifications. This helps validate your endpoint behavior. Important: FraudLabs Pro webhook registration must be configured manually via dashboard.

## Auth

Auth schemes: `API_KEY`.

## How agents use FraudLabs Pro

Inside a Definable workflow, FraudLabs Pro is one of the tools the **Distributor specialist** can call. Example coordination patterns:

- **Researcher → FraudLabs Pro** — the Researcher (GPT-5.5) pulls context from FraudLabs Pro (records, threads, documents), synthesises findings, and briefs the rest of the team.
- **Writer → Distributor → FraudLabs Pro** — the Writer (Claude Opus 4.7) drafts copy in brand voice, the Verifier passes it, then the Distributor writes the result into FraudLabs Pro (create record, post message, draft email).
- **Designer / Engineer → Distributor → FraudLabs Pro** — the Designer ships an asset or the Engineer ships a code change, the Distributor delivers it via FraudLabs Pro (attach file, open PR comment, post status).

The Verifier checks every FraudLabs Pro call. On rate limit, schema drift, or auth refresh it self-heals and retries — the workflow completes without manual intervention.

## Categories

- payment processing — https://definable.ai/apps/category/payment-processing/
- security & identity tools — https://definable.ai/apps/category/security-&-identity-tools/

## Related

- HTML page: https://definable.ai/apps/fraudlabs_pro/
- Same category (payment processing): https://definable.ai/apps/category/payment-processing/
- All integrations: https://definable.ai/apps/
- Workflow (multi-agent loop): https://definable.ai/workflow/
- Apps llms.txt index: https://definable.ai/llms-apps.txt