Skip to main content

Overview

Follow these best practices to maximize the value of Fraudiant while optimizing performance, cost, and user experience.

Performance Optimization

Implement Caching

Caching validation results can reduce API calls by 70-90% and dramatically improve response times.
Recommended caching strategy:
Cache duration recommendations:
  • Email validation: 24-48 hours
  • Domain validation: 48-72 hours (domains change less frequently)
  • Blocklist checks: No caching (real-time updates needed)

Use Redis for Distributed Caching


Error Handling

Fail Open Strategy

If the Fraudiant API is unavailable, allow users to proceed rather than blocking legitimate signups.

Implement Retry Logic with Exponential Backoff


Rate Limit Management

Monitor Rate Limit Headers

Implement Request Queuing


Security Best Practices

Protect API Keys

Never expose API keys in client-side code, public repositories, or logs.
DO:
  • Store keys in environment variables
  • Use secret management systems (AWS Secrets Manager, HashiCorp Vault)
  • Rotate keys regularly
  • Use separate keys for each environment
DON’T:
  • Hardcode keys in source code
  • Commit keys to version control
  • Share keys via email or chat
  • Use production keys in development

Validate Server-Side Only


User Experience

Provide Clear Feedback

Implement Progressive Validation

Handle Typos Gracefully


Cost Optimization

Batch Validation

Use Domain Validation for Pre-filtering


Testing

Create Test Helpers

Test with Different Environments


Monitoring & Observability

Log Validation Results

Track Rejection Rates


Summary

Cache aggressively

Reduce API calls by 70-90% with proper caching

Fail open gracefully

Don’t block users when service is unavailable

Monitor rate limits

Track usage and implement queuing strategies

Validate server-side

Never expose API keys in client code

Provide clear feedback

Help users understand validation failures

Test thoroughly

Use separate environments and mock validators