The following diagram shows the high-level architecture for the Experian Data Validation integrated into Snowflake.
What the diagram shows
The Data Validation app runs directly within your Snowflake account as a Snowflake Native App. Snowflake authentication, roles, and application permissions control who can open the Streamlit interface and call the SQL procedures.
The app provides two main areas:
- Snowflake Native App UI - guides setup, address, email, and phone configuration, test and bulk submission workflows, job status, usage dashboards, and result viewing.
- Native App processing - exposes SQL-callable validation operations, orchestrates single-record and bulk validation, tracks job progress, applies retry and status handling, and stores standardized results in Snowflake.
Data flow
- A user accesses the app in Snowflake.
- Snowflake authenticates the user and applies role-based access control.
- An administrator authorizes Experian credentials and outbound connectivity.
- A user configures validation options.
- A user tests one record or starts a bulk job.
- The app reads selected contact fields from Snowflake.
- The app sends HTTPS validation requests to Experian.
- Experian returns standardized values, confidence, and status.
- The app stores results in Snowflake.
- Users review status and consume results from Snowflake.
Data and security boundaries
Source tables remain in your Snowflake account. The app only uses the selected contact fields needed for validation, and sends those fields to Experian over HTTPS.
Client administrators control installation, permissions, credential binding, and outbound access approval. Results are returned to Snowflake for client-controlled querying, joining, reporting, and downstream use.
