This document describes the key process flows within DCKAP Integrator, detailing each step through which data moves from source systems to destination systems. These diagrams and their textual descriptions serve as evidence of processing controls for SOC 2 compliance.
2. Core Integration Process Flow
Step 1 — Source System Event / Schedule Trigger
An order, inventory change, or other business event occurs in the source system (e.g., eCommerce).
DCKAP Integrator receives a webhook notification OR polls the source system API on schedule.
Source credentials are validated from the encrypted credential vault before any data is fetched.
Step 2 — Data Ingestion
Raw payload is received at the DCKAP API Gateway.
TLS 1.2+ encryption is verified for the incoming connection.
Payload is logged (with PII masked) and placed in the ingestion queue.
Step 3 — Input Validation
Schema validation: payload checked against the registered connector schema.
Mandatory field check: all required fields present.
Format and range checks applied to each field.
Duplicate detection: record key checked against recent processing log.
PASS → record enters transformation queue. FAIL → record rejected, error logged, admin alerted.
Step 4 — Data Transformation
Field mapping rules applied: source fields renamed/reordered for destination schema.
Data type conversions applied (dates, currencies, booleans).
Value translations applied (status codes, country codes, etc.).
Conditional logic evaluated to apply business-specific transformations.
Enrichment lookups performed if configured.
Transformation output validated against destination schema.
Step 5 — Routing
Routing rules evaluated to determine destination endpoint.
Record marked with destination system ID and delivery priority.
Step 6 — Delivery to Destination
Transformed record posted to destination system API.
Idempotency key included to prevent duplicate writes.
Destination response (success / error) captured and logged.
On transient error: retry with exponential back-off (up to 3 times).
On persistent failure: record moved to dead-letter queue; alert sent.
Step 7 — Audit Logging & Confirmation
Full processing record written to the immutable audit log.
Sync status updated in the DCKAP portal dashboard.
Customer admin can view per-record status in the portal.
