LogoLogo
  • API Documentation
  • Authentication
  • Testing
  • Contact Support
  • System Status
  • VX
    • Create Session
    • API Methods
  • Agematch
    • United States
    • United States (DMV)
    • International
    • With KBA Quiz
    • Selfie Age Estimation
  • IDMATCH
    • United States
      • With KBA Escalation
      • KYC/CIP Compliance
      • COPPA Compliance
    • International
  • idmatch+
    • United States
  • IDMATCH+PREDICT
    • Fraud Score
  • phonematch
    • Verification and Validation
      • Smart 2FA
      • Phone Verification
      • Phone Validation
    • One Time Passwords
      • SMS
      • Call
    • Message Delivery
      • Dialer
  • emailmatch
    • Email Validation
  • dcams
    • Document Capture and Management Services
      • Scanning Basic
      • Scanning Enhanced
      • Manual Review
      • Storage
        • Create or Update a Customer
        • Get Customer Status
        • Get Customer Document Images
        • Update Customer Status
      • iFrame
        • Canned Responses
        • Create Token
        • View Callback
        • User Status
        • Generate Link
      • Swift SDK
      • Android SDK
  • Bouncer
    • Overview
    • Bouncer as an add-on
  • V-PIN
    • Overview
    • V-PIN as an add-on
    • V-PIN Stand Alone
  • Service Coverage
    • Data Coverage
  • Testing
    • Test Cases
    • Answers to KBA Questions
  • Reporting
    • Audit
  • API Processing Errors
    • Error Returns
  • Knowledge Base
    • Best Practices
    • Understanding Veratad Services
  • IDMax
    • IDMax Button Creator SDK
Powered by GitBook
On this page
  • What data should I send with each request?
  • Does Veratad store the input request?
  • How should I use the reference field?
  1. Knowledge Base

Best Practices

Below are some best practices when implementing the IDR5 API.

What data should I send with each request?

You must send the required fields and if you use an additional matching ruleset you must provide that element or the transaction will fail. That said, when searching for an individual in the data sources it is always more helpful to provide as much data as you collect. The more information we have on a person, the more people we will find.

Does Veratad store the input request?

No, Veratad does not store any sensitive PII information from your request. The only exception to this rule is when you use the document storage service.

How should I use the reference field?

Since Veratad does not store sensitive PII it is important for you to send a unique value in the reference field with each request. This will help for reporting and audit trail purposes.

PreviousError ReturnsNextUnderstanding Veratad Services

Last updated 4 years ago