NagentArtefacts
Dev & Technology
Enterprise and White Glove
Company
FraudLabs Pro connects to a Nagent workspace with an API key. Once it is connected, agents can call 8 FraudLabs Pro actions, such as "Create FraudLabs Pro Reseller Sub-Account", "Get FraudLabs Pro Order Result (v2)" and "Get SMS Verification Result". Nothing is enabled on connect: each action is allowed one at a time, and an action with side effects runs or waits for a person according to the agent's level.
Every operation an agent can call against FraudLabs Pro, with input parameters and output schema.
FRAUDLABS_PRO_CREATE_ACCOUNTCreates 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
Input parameters
Fax number (digits only, no special characters). Optional.
FraudLabs Pro Reseller API key (different from regular API key). Required for account creation. Apply at https://www.fraudlabspro.com/reseller/program
City name for the billing address
Full name of the account holder (first and last name)
Email address for the new account. Used for login and communications.
Contact phone number (digits only, no special characters or spaces)
State or province name/code for the billing address
Response format (json or xml). Defaults to json for structured data.
Company or organization name for the account
ISO 3166-1 alpha-2 country code (2-letter code). See https://www.fraudlabspro.com/developer/reference/country-codes
Primary street address (building number and street name)
Secondary address line (apartment, suite, unit, floor, etc.). Optional.
Industry classification ID (1-14). Options: 1=Retail(e-Commerce), 2=Retail(Brick&Mortar), 3=Hospitality, 4=Ticketing, 5=Clubs, 6=Memberships, 7=Digital Content, 8=Online Games, 9=Software, 10=Telecom, 11=Travel, 12=Non-Profit, 13=Services, 14=High Risk
Desired username for the new FraudLabs Pro account. Must be unique across all accounts.
Postal code or ZIP code for the billing address
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FRAUDLABS_PRO_FLP_FEEDBACK_ORDERSubmit 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.
Input parameters
The fraudlabspro_id returned from a Screen Order API call. This identifies which transaction to provide feedback for.
Your FraudLabs Pro API license key.
Optional internal note explaining the reason for this feedback decision (e.g., 'Customer verified by phone', 'Known fraudster pattern').
Feedback action: APPROVE (legitimate transaction), REJECT (fraudulent), or REJECT_BLACKLIST (fraudulent and add to permanent blacklist for enhanced future detection).
Response format. Defaults to 'json'.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FRAUDLABS_PRO_FLP_SCREEN_ORDERTool to screen orders for fraud. Use when you need to assess transaction risk before fulfillment.
Input parameters
Transaction IP address (IPv4 or IPv6)
User's email address
Transaction amount (must be positive)
First 6 or 8 digits of card for bank identification
Response format
Transaction currency (ISO-4217 code, e.g., USD)
Total quantity of items
Username used for signup
Billing street address
Billing city
SHA2 hash of card number
User's last name
Shipping street address
Shipping city
Single-character AVS result from processor
Billing state or province (US/CA code, e.g., NY)
Single-character CVV2 result (processor response)
Merchant product/service department ID
SHA2 hash of email if email not provided
User's first name
Shipping state or province (US/CA code, e.g., NY)
User's phone number
Billing country ISO-3166 alpha-2 code (e.g., US)
Email domain; auto-extracted if email provided
Device validation checksum from FraudLabs Pro JavaScript
Payment mode for transaction
Shipping country ISO-3166 alpha-2 code (e.g., US)
Billing postal or ZIP code
Shipping postal or ZIP code
Merchant's order ID (max 15 chars)
Shipping recipient last name
Payment gateway name
Shipping recipient first name
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FRAUDLABS_PRO_GET_ORDER_RESULT2Tool to retrieve an existing transaction from FraudLabs Pro fraud detection system using the v2 API. This API is only available for paid plans.
Input parameters
FraudLabs Pro transaction ID (fraudlabspro_id) or your platform's order ID (user_order_id). Required unless retrieving without specific ID.
FraudLabs Pro API key. If not provided, will use key from authentication metadata.
Response format; json (default) or xml
Type of ID provided in the 'id' parameter. Use FraudLabsPro::ID for FraudLabs Pro transaction IDs or FraudLabsPro::UserOrderID for your order IDs.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FRAUDLABS_PRO_GET_SMS_VERIFICATION_RESULTVerify 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.
Input parameters
FraudLabs Pro API key
The one-time password (OTP) code received by the user via SMS that needs to be verified
Response format, 'json' (default) or 'xml'
Unique transaction ID returned by the Send SMS Verification API
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FRAUDLABS_PRO_SEND_SMS_VERIFICATIONSends 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'.
Input parameters
FraudLabs Pro API key
Recipient mobile number in E.164 format, e.g., +12015550123
SMS message template; must include <otp> placeholder; max 140 characters
Response format: json (default) or xml
OTP timeout in seconds; default 3600; min 15; max 86400
ISO 3166 country code for the phone, e.g., US
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FRAUDLABS_PRO_SUBSCRIBE_PLANTool 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.
Input parameters
Your Reseller API key.
Plan code. Only MICRO plan is currently accepted.
Response format. Valid values: json, xml. Default is json.
Username of the account to subscribe.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FRAUDLABS_PRO_WEBHOOK_ORDER_STATUS_CHANGEDTool 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.
Input parameters
Test transaction id to include in the webhook payload
FraudLabs Pro status to include in the webhook payload
URL to receive FraudLabs Pro order status change notifications
Additional key/value pairs to include in the payload
Payload encoding format for the test webhook POST
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
Agents can call 8 FraudLabs Pro actions on Nagent, including "Create FraudLabs Pro Reseller Sub-Account", "Get FraudLabs Pro Order Result (v2)" and "Get SMS Verification Result". Create FraudLabs Pro Reseller Sub-Account: Creates a new FraudLabs Pro user account under a reseller account. Each action is listed on this page with its input parameters and its output.
FraudLabs Pro connects with an API key, under your workspace's own connection. Nothing is enabled on connect: each action is allowed one at a time and can be scoped to the agents that need it.
Create FraudLabs Pro Reseller Sub-Account takes 12 required inputs: key, city, name, email, phone, state, company, country, address1, industry, username and zip_code. It also takes 3 optional inputs: fax, format and address2. It returns data, error and successful.