← Graph

How did the new flow handle different third-party request parameters?

question 1 connections

Audience member asks how the new flow worked when the parameters it would send to third parties differed from what was recorded in the old flow. Answer: recorded stubs were transformed before matching — e.g. detecting that a user identifier had a known prefixed/public format and rewriting it to the new flow's format — so the verification used the new flow's data against stubs derived from old-flow responses. No entirely new HTTP calls were added; the underwriting process itself was unchanged, only the preparation differed.

answer_summary
Recorded stubs were evaluated and rewritten to match the new flow's parameter format (e.g. user-id prefix patterns). No new HTTP calls were introduced — the underwriting itself stayed the same.
question How did the new flow handle different third-party request parameters?
asked_at
Asked during the talk's Q&A.

Provenance