Fintech: Merchant Underwriting Review with Claude Code: API Runtime Pattern
A production playbook for merchant underwriting review in fintech operations using Claude Code: api runtime pattern, run-scoped inputs, logs, typed results, and artifacts.
Audience: Fintech risk teams underwriting merchants
The problem
Fintech risk teams underwriting merchants need merchant underwriting review to run repeatedly against applications, bank statements, websites, KYC docs, and risk policies. In fintech operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.
Implementation path
Package the merchant underwriting review instructions as a skill, send applications, bank statements, websites, KYC docs, and risk policies as run-scoped inputs, execute with Claude Code, poll terminal status, and consume argo.result.v1 instead of parsing a transcript.
Tradeoffs and failure modes
The API boundary forces the workflow to define inputs, terminal states, and result shape before customers depend on it. For merchant underwriting review, the practical test is whether a second run can be debugged, retried, and consumed by a product without reading the raw agent transcript.
Run request
POST /api/skills/<skill_id>/run
provider=claude-code
workflow=fintech-underwriting-review
inputs[]=@./input-pack.zip
result_schema=argo.result.v1
Run this on Argo