Skip to main content
Audience: Pre-sales, Product Managers, Compliance Teams

​
Important Disclaimers

​
This is NOT API Documentation

This document describes FrankieOne’s platform capabilities for vendor and data source management. It does not describe API-controllable features. What customers CANNOT do via API:
  • Select specific vendors
  • Configure routing rules
  • Define fallback logic
  • Control data source cascade
  • Modify vendor selection strategies
What customers CAN do:
  • Submit verification requests via FrankieOne’s API
  • Receive verification results
  • Work with FrankieOne to request configuration changes to vendor setup

​
Pricing Disclaimer

All pricing examples are illustrative only. Actual costs vary based on requirements, volumes, geographic coverage, vendor selection, contract terms, and custom configurations. Contact your FrankieOne representative for accurate pricing.

​
Table of Contents

  1. Understanding FrankieOne’s Orchestration Platform
  2. Types of Vendors and Data Sources
  3. How FrankieOne Configures Vendor Selection
  4. Data Source Selection Strategies
  5. Vendor Routing and Fallback
  6. Optimizing Pass Rates
  7. Working with FrankieOne
  8. Common Scenarios
  9. FAQs

​
Understanding FrankieOne’s Orchestration Platform

​
What is FrankieOne?

FrankieOne is an orchestration platform that connects you to a global ecosystem of verification vendors and data sources through a single API integration. FrankieOne manages all vendor relationships, routing logic, and data source selection on your behalf. Architecture Overview: WITHOUT FRANKIEONE: = 6 separate integrations to build and maintain WITH FRANKIEONE: = 1 API integration, FrankieOne manages 350+ sources

​
Key Platform Capabilities

1. Single API Integration
  • One API integration to FrankieOne
  • FrankieOne maintains connections to 350+ data sources globally
  • Coverage in 195+ countries
  • No need to integrate with each vendor separately
2. FrankieOne-Managed Vendor Selection
  • FrankieOne configures which vendors are used for your verifications
  • Routing rules are set by FrankieOne based on your requirements
  • Changes to vendor configuration require coordination with FrankieOne
3. Vendor Flexibility
  • FrankieOne can change underlying vendors without requiring changes to your API integration
  • No vendor lock-in at the integration level
  • Ability to adapt to changing requirements through FrankieOne configuration
4. Simplified Management
  • Single contract with FrankieOne
  • Consolidated billing
  • Unified support
  • Consistent API response format across all vendors

​
Types of Vendors and Data Sources

FrankieOne connects to vendors across multiple verification categories. The specific vendors used for your account are configured by FrankieOne based on your requirements.

​
1. KYC (Know Your Customer) Vendors

Purpose: Verify identity details against authoritative data sources Capabilities May Include:
  • Electronic verification (e.g., 2+2 rule compliance)
  • Credit bureau checks
  • Electoral roll verification
  • Government database checks
  • Utility record verification
Use Cases:
  • Standard customer onboarding
  • Electronic verification
  • Address verification
  • Identity confirmation

​
2. IDV (Identity Verification) Vendors

Purpose: Verify documents and biometrics Capabilities May Include:
  • Document authenticity verification
  • OCR (data extraction from documents)
  • Liveness detection
  • Face matching (biometrics)
  • Forgery detection
Use Cases:
  • Document verification
  • Remote identity verification
  • Biometric verification
  • High-assurance verification

​
3. AML (Anti-Money Laundering) Vendors

Purpose: Screen against watchlists and sanctions Capabilities May Include:
  • PEP (Politically Exposed Persons) screening
  • Sanctions list screening
  • Watchlist screening
  • Adverse media screening
  • Ongoing monitoring
Use Cases:
  • Compliance screening
  • Risk assessment
  • Ongoing monitoring
  • Enhanced due diligence

​
4. Fraud Detection Vendors

Purpose: Detect fraud signals and risk Capabilities May Include:
  • Device intelligence
  • Email risk assessment
  • Phone risk assessment
  • IP address analysis
  • Behavioral analytics
Use Cases:
  • Fraud prevention
  • Risk scoring
  • Account takeover prevention
  • Transaction monitoring

​
5. KYB (Know Your Business) Vendors

Purpose: Verify business entities Capabilities May Include:
  • Company registry searches
  • Beneficial ownership verification
  • Business verification
  • Corporate structure analysis
  • Director verification
Use Cases:
  • Business onboarding
  • Corporate verification
  • UBO (Ultimate Beneficial Owner) verification
  • Corporate due diligence

​
Data Source Types

Within each vendor category, different types of data sources may be available: Government Data Sources:
  • Passport databases
  • Driver license databases
  • National ID databases
  • Birth/death registries
  • Electoral rolls
Commercial Data Sources:
  • Credit bureaus
  • Utility providers
  • Telecommunications providers
  • Financial institutions
  • Property records
Watchlist Data Sources:
  • OFAC (US sanctions)
  • UN sanctions lists
  • EU sanctions lists
  • PEP databases
  • Adverse media databases
Proprietary Data Sources:
  • Vendor-specific databases
  • Consortium data
  • Historical verification data
  • Fraud intelligence networks

​
How FrankieOne Configures Vendor Selection

​
The Configuration Process

Important: Vendor selection and routing are configured by FrankieOne, not controlled by API parameters.

​
Configuration Factors

FrankieOne considers multiple factors when configuring vendor selection: Geographic Coverage:
  • Which countries/regions need coverage
  • Local vs international data sources
  • Regional regulatory requirements
Verification Requirements:
  • Type of verification needed (KYC, IDV, AML, etc.)
  • Required data points
  • Regulatory compliance needs
  • Industry-specific requirements
Performance Requirements:
  • Pass rate targets
  • Response time requirements
  • Availability requirements
Cost Constraints:
  • Budget per verification
  • Volume projections
  • Cost vs pass rate trade-offs
Regulatory Compliance:
  • Industry regulations (financial services, gaming, etc.)
  • Regional requirements (GDPR, CCPA, etc.)
  • Audit requirements

​
Data Source Selection Strategies

FrankieOne can configure your account with different data source selection strategies. The strategy used is set by FrankieOne, not controlled via API.

​
Strategy 1: Single Data Source

How It Works:
  • FrankieOne configures a single primary data source for verifications
  • All verification requests are processed using this configured source
When FrankieOne May Configure This:
  • High-quality single source available
  • Cost optimization priority
  • Regulatory requirement for specific source
  • Simple use case with good baseline pass rates
Characteristics:
  • Simplest configuration
  • Lowest cost per verification
  • Pass rate dependent on single source quality
  • No redundancy if source is unavailable
Example Scenario: Customer operates only in Australia and has regulatory requirement to use specific government data source.

​
Strategy 2: Cascade (Sequential Fallback)

How It Works:
  • FrankieOne configures a primary data source
  • If primary source returns no match, FrankieOne’s platform automatically attempts secondary source
  • Process continues through configured sources until match is found or all sources exhausted
When FrankieOne May Configure This:
  • Need for higher pass rates
  • Coverage gaps in primary source
  • Multiple complementary data sources available
Characteristics:
  • Higher pass rates than single source
  • Incremental cost (only pay for sources actually used)
  • Automatic fallback on no-match
  • Sequential processing may increase latency
Example Configuration:

​
Strategy 3: Parallel Verification (coming soon)

This feature is under assessment if interested in Parallel verification please reach out as we have this planned; however, require customer interest. Due to the cost many customers select alternate options. How It Works:
  • FrankieOne configures multiple data sources to be queried simultaneously
  • Results from all sources are aggregated
  • Higher confidence through multiple confirmations
When FrankieOne May Configure This:
  • High-assurance verification needed
  • Fraud prevention priority
  • Regulatory requirement for multiple independent checks
Characteristics:
  • Highest confidence
  • Best for high-risk scenarios
  • Higher cost (pay for all parallel sources)
  • Fastest response time (parallel execution)
Example Configuration:

​
Strategy 4: Conditional Routing

How It Works:
  • FrankieOne configures different data sources for different scenarios
  • Routing rules based on entity attributes, risk signals, or geographic location
When FrankieOne May Configure This:
  • Different requirements for different customer segments
  • Geographic optimization needed
  • Risk-based verification strategies
Characteristics:
  • Optimized for specific scenarios
  • Cost-effective for diverse use cases
  • Complex configuration
  • Requires clear segmentation logic
Example Configuration:

​
Strategy 5: Geographic Routing

How It Works:
  • FrankieOne configures different data sources for different countries/regions
  • Requests are routed based on customer’s declared country
When FrankieOne May Configure This:
  • Multi-country operations
  • Regional data sources perform better locally
  • Regulatory requirements vary by region
Characteristics:
  • Optimized for geographic coverage
  • Addresses regional data availability
  • May use different strategies per region
Example Configuration:

​
Vendor Routing and Fallback

​
How Routing Works

Important: All routing logic is configured and managed by FrankieOne, not controlled by API parameters submitted by customers.

​
Routing Configuration Types

1. Geographic Routing
  • FrankieOne configures routing based on customer’s country
  • Example: Australian customers → Australian data sources
  • Ensures local data coverage and compliance
2. Document-Type Routing
  • For IDV checks, FrankieOne may configure different vendors for different document types
  • Example: Passport checks → Vendor A, Driver License checks → Vendor B
  • Optimizes for vendor strengths
3. Risk-Based Routing
  • FrankieOne may configure routing based on risk signals
  • Example: High-risk → Enhanced verification path, Low-risk → Standard path
  • Requires risk scoring configuration
4. Performance-Based Routing
  • FrankieOne may configure routing to optimize for pass rates
  • Example: If Vendor A pass rate drops, route to Vendor B
  • Requires monitoring and dynamic configuration

​
Fallback Configuration

Automatic Fallback: FrankieOne can configure automatic fallback in several scenarios:
  1. No Match Fallback
    • Primary source returns no match
    • System automatically tries configured secondary source
    • Continues through fallback chain if configured
  2. Vendor Unavailability Fallback
    • Primary vendor is unavailable or times out
    • System automatically routes to configured backup vendor
    • Ensures service continuity
  3. Error Fallback
    • Vendor returns error response
    • System may retry with alternate vendor if configured
    • Depends on error type and configuration
Example Fallback Configuration:

​
Resilience Features

FrankieOne’s platform includes resilience features (configuration dependent):
  • Timeout Handling: Configured timeouts for vendor responses
  • Retry Logic: May retry requests on transient failures
  • Circuit Breakers: May temporarily disable failing vendors
  • Monitoring: Tracks vendor performance and availability
Note: Specific resilience configurations are managed by FrankieOne based on your SLA requirements.

​
Optimizing Pass Rates

Pass rate optimization is achieved through FrankieOne configuration changes, not API controls.

​
What Affects Pass Rates

Data Quality:
  • Accuracy of customer data submitted via API
  • Completeness of required fields
  • Data formatting and standardization
Data Source Coverage:
  • Whether configured data sources have records for your customer demographics
  • Geographic coverage of configured sources
  • Recency of data in configured sources
Configuration Strategy:
  • Single source vs cascade vs parallel (configured by FrankieOne)
  • Number of fallback sources configured
  • Match criteria sensitivity (configured by FrankieOne)

​
How to Request Pass Rate Improvements

1. Review Current Performance
  • Analyze pass rate data from FrankieOne reporting
  • Identify patterns in failures
  • Understand failure reasons
2. Contact FrankieOne
  • Provide pass rate data and failure analysis
  • Discuss your target pass rates
  • Share any constraints (budget, latency, etc.)
3. FrankieOne Recommends Configuration Changes Options may include:
  • Adding fallback data sources
  • Switching primary data source
  • Adjusting match criteria
  • Implementing cascade strategy
  • Geographic routing optimization
4. Test in UAT
  • FrankieOne implements proposed changes in UAT
  • Customer tests with real data via API
  • Measure pass rate improvements
  • Evaluate cost impact
5. Production Deployment
  • Once approved, FrankieOne deploys to production
  • Monitor ongoing pass rates
  • Iterate if needed

​
Pass Rate Improvement Strategies

Strategy 1: Add Fallback Sources
  • Configuration Change: FrankieOne adds secondary/tertiary sources
  • Impact: Higher pass rates, incremental cost
  • Best For: Cases with clear coverage gaps
Strategy 2: Switch Primary Source
  • Configuration Change: FrankieOne changes which source is tried first
  • Impact: Different coverage, may affect cost
  • Best For: When alternative source has better coverage for your demographics
Strategy 3: Parallel Verification
  • Configuration Change: FrankieOne configures multiple sources to run in parallel
  • Impact: Highest pass rates, highest cost
  • Best For: High-value customers or regulatory requirements
Strategy 4: Optimize Data Quality
  • Customer Action: Improve data submitted via API (not a configuration change)
  • Impact: Better matching across all sources
  • Best For: When data quality is identified as primary issue
Strategy 5: Geographic Routing
  • Configuration Change: FrankieOne implements region-specific source routing
  • Impact: Optimized pass rates per region
  • Best For: Multi-country operations

​
Cost vs Pass Rate Trade-offs

FrankieOne helps you balance cost and pass rates: Pass rates and costs are illustrative - actual results vary by configuration and data quality Work with FrankieOne to:
  • Define your acceptable pass rate
  • Understand your cost constraints
  • Find optimal configuration
  • Test and validate trade-offs

​
Working with FrankieOne

​
Initial Setup Process

1. Requirements Gathering Contact FrankieOne with:
  • Geographic coverage needs
  • Verification types required
  • Expected volumes
  • Pass rate targets
  • Budget constraints
  • Regulatory requirements
  • Timeline for deployment
2. FrankieOne Provides Recommendations FrankieOne will:
  • Recommend specific vendors for your use cases
  • Propose routing and fallback strategy
  • Provide estimated pass rates
  • Share pricing proposal
  • Explain configuration rationale
3. Customer Review and Approval You will:
  • Review vendor recommendations
  • Understand trade-offs
  • Ask questions
  • Approve proposed configuration
  • Sign contracts if needed
4. FrankieOne Configuration FrankieOne will:
  • Set up vendor connections
  • Configure routing rules
  • Implement fallback logic
  • Prepare UAT environment
  • Provide API credentials
5. UAT Testing Customer will:
  • Test verification API with sample data
  • Validate pass rates
  • Check response formats
  • Test error scenarios
  • Measure latency
6. Production Deployment FrankieOne will:
  • Deploy approved configuration to production
  • Monitor initial traffic
  • Provide go-live support

​
Ongoing Optimization

Monthly/Quarterly Reviews FrankieOne can provide:
  • Pass rate reports
  • Cost analysis
  • Vendor performance metrics
  • Failure reason analysis
  • Optimization recommendations
Configuration Changes To request configuration changes:
  1. Contact your FrankieOne representative
  2. Explain what you want to change and why
  3. FrankieOne provides options and impact analysis
  4. Test changes in UAT
  5. Deploy to production once approved
Common Change Requests:
  • Add new verification types
  • Expand to new countries
  • Adjust pass rate vs cost balance
  • Add fallback sources
  • Change routing strategy

​
Support and SLAs

Support Channels:
  • Your FrankieOne account representative
  • Technical support (for API integration questions)
  • Configuration requests (for routing/vendor changes)
SLA Considerations:
  • API availability SLAs
  • Response time SLAs
  • Support response times
  • Configuration change timelines
Contact FrankieOne to discuss specific SLA requirements.

​
Common Scenarios

​
Scenario 1: Starting with Single Country

Situation:
  • New business, operating only in Australia
  • Need standard KYC verification
  • Limited budget, volume under 1000/month
FrankieOne May Configure:
  • Single Australian KYC vendor
  • One fallback source
  • Standard match criteria
Why This Configuration:
  • Cost-effective for low volumes
  • Adequate pass rates for single market
  • Simple to test and deploy
  • Room to expand later
Customer Experience:
  • Submit verification via API
  • Receive pass/fail response
  • No API changes needed if vendors change

​
Scenario 2: Multi-Country Expansion

Situation:
  • Established business expanding from Australia to UK and Singapore
  • Need consistent verification across regions
  • Volume: 5,000/month split across countries
FrankieOne May Configure:
  • Geographic routing:
    • Australia → Australian KYC vendor + fallback
    • UK → UK KYC vendor + fallback
    • Singapore → APAC KYC vendor + fallback
  • Consistent fallback strategy across regions
  • Unified reporting
Why This Configuration:
  • Optimized for local data coverage
  • Regulatory compliance per region
  • Consistent customer experience
  • Centralized management
Customer Experience:
  • Same API integration for all countries
  • Submit country in API request
  • FrankieOne routes to appropriate vendors
  • Consistent response format

​
Scenario 3: High-Risk Vertical (Crypto Exchange)

Situation:
  • Cryptocurrency exchange
  • High regulatory scrutiny
  • Need enhanced due diligence
  • Fraud prevention critical
  • Budget allows for comprehensive verification
FrankieOne May Configure:
  • Parallel KYC verification (2-3 sources)
  • Enhanced IDV with liveness and biometrics
  • AML screening (PEP + sanctions)
  • Fraud signals (device, email, phone)
  • Ongoing monitoring
Why This Configuration:
  • High-assurance verification
  • Multiple independent confirmations
  • Comprehensive risk assessment
  • Regulatory compliance
Customer Experience:
  • Submit verification via API
  • FrankieOne orchestrates multiple checks
  • Receive aggregated pass/fail result
  • Access to detailed check results if needed

​
Scenario 4: Optimizing for Pass Rates

Situation:
  • Existing customer with 75% pass rate
  • Want to improve to 85%
  • Currently using single KYC source
FrankieOne May Recommend:
  1. Analysis of failure reasons
  2. Add cascade fallback source
  3. Test in UAT
  4. Measure pass rate improvement
  5. Evaluate cost increase
Potential Outcome:
  • Pass rate improves to 83%
  • Cost per verification increases 15%
  • Customer approves change
  • FrankieOne deploys to production
Customer Experience:
  • No API changes required
  • Improved pass rates
  • Transparent cost increase
  • Better customer conversion

​
Scenario 5: Adding New Verification Type

Situation:
  • Customer currently doing KYC only
  • Want to add document verification (IDV)
  • Same API integration preferred
FrankieOne May Configure:
  1. Add IDV vendor to customer’s configuration
  2. Configure document routing (passport vs license)
  3. Set up liveness detection
  4. Configure OCR extraction
  5. Test in UAT
Customer Experience:
  • Same API integration
  • New endpoints for IDV (as per OpenAPI spec)
  • Consistent authentication
  • Unified reporting across KYC and IDV

​
FAQs

​
General

Q: Can I choose which specific vendor is used for my verifications? A: Vendor selection is configured by FrankieOne based on your requirements. You cannot select vendors dynamically via API parameters. However, you can work with FrankieOne to:
  • Request specific vendors during initial setup
  • Understand which vendors are configured for your account
  • Request vendor changes if needed
Q: Can I change vendors after going live? A: Yes, but vendor changes are configuration changes managed by FrankieOne:
  1. Contact your FrankieOne representative
  2. Explain why you want to change vendors
  3. FrankieOne will recommend alternatives
  4. Test in UAT
  5. Deploy to production
Your API integration does not need to change. Q: Do I need a separate contract with each vendor? A: No:
  • Single contract with FrankieOne
  • FrankieOne manages all vendor relationships
  • Consolidated billing through FrankieOne
  • Unified support
Q: What happens if a vendor has an outage? A: Depends on your configuration:
  • If fallback is configured, FrankieOne automatically routes to backup vendor
  • If no fallback configured, requests may fail
  • Discuss resilience requirements with FrankieOne
Q: How do I know which vendor was used for a specific verification? A: FrankieOne can provide:
  • Vendor information in API responses (if configured)
  • Detailed reporting showing vendor usage
  • Audit logs
Check with FrankieOne about available reporting options.

​
Coverage and Capabilities

Q: What countries does FrankieOne support? A: FrankieOne provides access to data sources in 195+ countries. Specific coverage for your account depends on:
  • Which vendors are configured for you
  • The verification types you need
  • Your budget and volume
Contact FrankieOne to discuss coverage for your target markets. Q: Can FrankieOne verify all document types? A: FrankieOne connects to IDV vendors that support multiple document types:
  • Passports
  • Driver licenses
  • National ID cards
  • Residence permits
  • Other government-issued documents
Specific document support depends on:
  • Configured vendors
  • Country of document issuance
  • Document type
Q: Does FrankieOne support biometric verification? A: Yes, FrankieOne connects to IDV vendors that offer:
  • Liveness detection
  • Face matching
  • Document-to-selfie matching
This requires appropriate vendor configuration.

​
Pricing

Q: How does FrankieOne pricing work? A: All pricing is determined by your FrankieOne representative and is customized based on:
  • Your specific requirements
  • Verification types and volumes
  • Geographic coverage needed
  • Selected vendors (configured by FrankieOne)
  • Contract terms
FrankieOne cannot provide standardized pricing because configurations vary significantly. Contact FrankieOne for accurate pricing. Q: Do I pay for failed verifications? A: Depends on the vendor and your agreement:
  • Some vendors charge for all attempts
  • Some vendors charge only for successful matches
  • Pricing models vary
Your FrankieOne representative will explain the pricing model for your configured vendors. Q: Are there volume discounts? A: Yes, volume discounts are typically available:
  • Higher volumes generally receive better per-unit pricing
  • Discount tiers vary by vendor and contract
  • Commitments may unlock better pricing
Contact FrankieOne to discuss volume discounts. Q: What if my volume changes? A: FrankieOne offers flexible options: Volume Increases:
  • May qualify for better pricing tiers
  • Can adjust contract terms
  • Discuss with your representative
Volume Decreases:
  • Depends on contract terms
  • May need to adjust commitments
  • FrankieOne works with you to find solutions
Best Practice:
  • Provide realistic volume estimates
  • Include growth projections
  • Discuss flexibility needs upfront
Q: Are there setup fees? A: Depends on configuration complexity:
  • Standard configurations may have no setup fees
  • Complex custom configurations may have setup fees
  • Professional services may be available
Your FrankieOne representative will provide transparent pricing.

​
Technical

Q: Do I need to integrate with each vendor separately? A: No:
  • Single API integration to FrankieOne
  • FrankieOne handles all vendor integrations
  • Consistent API across all vendors
  • No code changes needed when FrankieOne changes your vendor configuration
Q: How long does vendor configuration take? A: Typical timeline:
  • Simple: 1-2 weeks
  • Standard: 2-4 weeks
  • Complex: 4-8 weeks
Depends on:
  • Number of vendors
  • Complexity of routing
  • Testing requirements
  • Vendor onboarding needs
Q: Can I test vendors before committing? A: Yes:
  • Test in UAT environment
  • Use test data via API
  • Measure pass rates and performance
  • Make informed decision
FrankieOne provides UAT access for testing. Q: Can I control routing via API parameters? A: No. Routing logic is configured by FrankieOne, not controlled via API parameters. To change routing:
  1. Contact FrankieOne
  2. Request routing changes
  3. FrankieOne implements in UAT
  4. Test and approve
  5. Deploy to production
Q: What data do I need to provide in the API request? A: Required data depends on verification type. Refer to:
  • FrankieOne OpenAPI specification for required fields
  • Postman collection for example requests
  • API documentation at https://docs.frankieone.com
Common fields include:
  • Entity type (person, organization)
  • Name fields
  • Address fields
  • Date of birth
  • Document details (for IDV)

​
Vendor Selection

Q: How does FrankieOne recommend vendors? A: FrankieOne considers: Your Requirements:
  • Geographic coverage
  • Verification types
  • Pass rate targets
  • Budget constraints
  • Regulatory requirements
Vendor Capabilities:
  • Data source coverage
  • Verification accuracy
  • Response times
  • Reliability
  • Pricing
FrankieOne’s Experience:
  • Vendor performance data
  • Coverage analysis
  • Cost benchmarking
  • Best practices
Q: Can I request specific vendors? A: Yes:
  • Share preferences during requirements gathering
  • FrankieOne will evaluate feasibility
  • May recommend alternatives if better suited
  • Final decision requires FrankieOne approval
Q: What if I’m already using a specific vendor directly? A: FrankieOne may be able to:
  • Connect to your existing vendor account
  • Or configure FrankieOne’s connection to same vendor
  • Maintain continuity while adding flexibility
Discuss with FrankieOne during setup.

​
Pass Rates and Optimization

Q: What pass rate can I expect? A: Pass rates vary based on:
  • Data quality you submit via API
  • Configured vendors and data sources
  • Your customer demographics
  • Geographic market
  • Verification type
FrankieOne can provide:
  • Benchmark pass rates for similar customers
  • Estimated pass rates during vendor recommendation
  • Actual pass rates during UAT testing
  • Ongoing pass rate reporting
Q: How can I improve my pass rates? A: Two approaches: 1. Improve Data Quality (Customer Action):
  • Submit complete, accurate data via API
  • Ensure proper formatting
  • Include all available data points
  • Standardize address formats
2. Configuration Changes (FrankieOne Action):
  • Add fallback sources
  • Switch primary vendor
  • Implement cascade strategy
  • Optimize match criteria
Contact FrankieOne to analyze pass rates and discuss optimization options. Q: What causes verification failures? A: Common reasons:
  • No match in configured data sources
  • Incomplete data submitted via API
  • Data formatting issues
  • Customer not in vendor databases
  • Vendor service issues
FrankieOne reporting can break down failure reasons.

​
Summary

​
Key Takeaways

FrankieOne is an Orchestration Platform
  • Single API integration
  • Access to 350+ data sources
  • Coverage in 195+ countries
  • Vendor-agnostic integration
Vendor Selection is Configured by FrankieOne
  • Not controllable via API parameters
  • Based on your requirements
  • Considering coverage, cost, and performance
  • Customer approves final configuration
Flexibility Without Code Changes
  • Switch vendors without changing your integration
  • Add new verification types
  • Expand to new countries
  • Optimize based on performance
Pricing is Customized
  • Determined by FrankieOne representative
  • Based on specific requirements
  • Varies by volume, coverage, vendors
  • Contact FrankieOne for accurate pricing
Multiple Configuration Strategies
  • Single source (simple, cost-effective)
  • Cascade (higher pass rates)
  • Parallel (highest confidence)
  • Conditional routing (optimized)
  • Geographic routing (regional optimization)
Continuous Optimization
  • Monitor performance through reporting
  • Request configuration adjustments
  • Test changes in UAT
  • Deploy approved changes to production

​
Next Steps

​
1. Define Your Requirements

Prepare the following information:
  • Geographic coverage: Which countries?
  • Verification types: KYC, IDV, AML, KYB, Fraud?
  • Volume: Expected verifications per month
  • Pass rate targets: What success rate do you need?
  • Budget: Cost constraints
  • Regulatory: Compliance requirements
  • Timeline: When do you need to go live?

​
2. Contact FrankieOne

Schedule consultation to:
  • Discuss your requirements
  • Receive vendor recommendations
  • Understand routing strategy options
  • Get customized pricing proposal
  • Plan implementation timeline

​
3. Review Recommendations

FrankieOne will provide:
  • Recommended vendors
  • Proposed configuration strategy
  • Estimated pass rates
  • Pricing details
  • Implementation plan

​
4. Test in UAT

Once configured:
  • Test verification API
  • Use real sample data
  • Measure actual pass rates
  • Validate response formats
  • Test error scenarios

​
5. Deploy to Production

After UAT approval:
  • FrankieOne activates production configuration
  • Begin sending production traffic via API
  • Monitor pass rates and costs
  • Request optimizations as needed

​
Resources

FrankieOne Documentation:
  • API Documentation: https://docs.frankieone.com
  • OpenAPI Specification: Available from FrankieOne
  • Postman Collections: Available from FrankieOne
Support:
  • Contact your FrankieOne representative
  • Technical support for API integration questions
  • Configuration change requests
What to Prepare for Your FrankieOne Call:
  • Your requirements (see “Define Your Requirements” above)
  • Target markets / countries
  • Expected verification volumes
  • Budget constraints
  • Current challenges or pain points
  • Timeline and go-live date

​
Final Reminders

​
This Document Describes Platform Capabilities

This is a conceptual guide explaining how FrankieOne’s platform works. It does not describe API-controllable features. For API Documentation:
  • See FrankieOne’s OpenAPI specification
  • See API documentation at https://docs.frankieone.com
  • Use Postman collections for example requests

​
Vendor Selection is Configuration, Not API Control

You cannot control vendor selection, routing, fallback, or data source cascade through API parameters. These are configured by FrankieOne based on your requirements.

​
All Pricing is Customized

Examples in this document are illustrative only. Contact your FrankieOne representative for accurate pricing based on your specific situation.
Document Version: 1.0
Last Updated: February 2026
Document Type: Conceptual Guide (Non-API)