Persona: Vendor / Integration Partner

You’re talking to a broker about integration. They want a 30-minute meeting; you want to look prepared. By the end of this reading list, you’ll know exactly where your product fits in the broker’s operational stack, which fields you produce or consume, what SLA matters at your touchpoint, and what gotchas your sales engineer hasn’t told you about yet.

This page is your shortcut.

What you’ll find useful here

Three layers matter most:

• The Vendor Atlas — your category and your competitors. Know where you stand.
• The Field Atlas — which fields your product produces or consumes (depending on category).
• The Integration DAG — your position in the dependency graph; what blocks what.

Then domain-specific deep-dives for your product category.

Suggested reading path (in this order)

1. Vendor Atlas Overview — find your category. 22 categories total. Skim peers; understand positioning conventions used on the site (descriptive, not endorsement).

2. Field Atlas Overview — if your product produces or consumes data, find the per-destination page that maps to your product. For example:

   • KYC verification → KYC verification destination and CKYC.
   • eSign → eSign-related blueprint rows — eSign isn’t a destination in the atlas because it’s signed input; relevant context is in journey screen 9.
   • AA / consent manager → most relevant in Income Verification and bank verification rows.
   • DLT / SMS → DLT comms destination.
   • OMS / RMS / back-office → back-office destination, RMS destination.
   • Surveillance / AML → AML/FIU destination.

3. Integration DAG Overview — find your phase. Your product likely sits in one of: Onboarding (KYC verification, eSign, AA, penny drop) / BOD (file fetch from exchanges) / Trading Hours (OMS, RMS, surveillance) / EOD & Settlement (back-office, DLT comms) / Lifecycle Events (modification routing).

4. Deep dive for your domain:

   • eSign → Journey screen 9 + Compliance Blueprint KYC domain.
   • AA / consent manager → Compliance Blueprint AA-related rows + Field Atlas Section F (income verification flows).
   • KYC verification / face-match / penny-drop → Journey screens 2, 3, 5.
   • DLT comms → DLT Framework deep-dive — TRAI framework, registration, scrubbing, error codes.
   • OMS / RMS → OMS Internals deep-dive + RMS / SPAN Methodology.
   • Back-office → Compliance Blueprint Reporting + Investor Servicing domains.
   • Surveillance → Surveillance — NORMS / GSM / ASM deep-dive.
   • AML / sanctions → Compliance Blueprint AML domain + AML / FIU destination page.

5. Broker Process Narrative — light read. Useful for understanding how your product fits the broker’s operational rhythm.

That’s the foundation.

Tip

The Vendor Atlas is endorsement-free. Your product gets a row with descriptive positioning (“dominant in retail back-office”, “common AA gateway”). The convention is to enumerate, not to recommend. Brokers reading the atlas use it to scope; they don’t take vendor selection from this site. Your sales conversation is still yours to win.

Common questions in your role

• Which fields does my product need to send to the broker? → Field Atlas destination page for your category — per-destination listing.
• What format does the broker expect? → Field Atlas destination page → format column.
• What’s the SLA the broker needs at my touchpoint? → Integration DAG — find your node; sla column.
• What happens if my service fails? → Integration DAG node → failure_surface column + retry_policy column.
• Is my product DLT-compliant for the broker’s SMS use case? → DLT Framework deep-dive.
• Does my product need to be empanelled with the exchange? → Depends on category. CTCL / algo vendors have NSE / BSE / MCX empanelment paths. See OMS Internals deep-dive + Retail Algo Framework.
• The broker says ‘I need your product to integrate with my back-office’. What does that involve? → Back-office destination page — typical fields; [vendor-specific] tags indicate where your product’s column names will differ from “industry typical.”
• What’s the broker’s CSCRF expectation for me as a vendor? → CSCRF deep-dive — vendor due diligence section.

What to skip (and why)

• All persona pages other than this one — you don’t need them.
• appendix/* — out of scope unless your product specifically handles those cohorts.
• The lifecycle walkthroughs — useful context but not direct integration material.
• Compliance / audit deep-dives beyond CSCRF (which affects you) — broker’s domain.

When you’d hand off

• “What’s the broker’s procurement process?” → Product Manager at the broker side.
• “Integration technical questions” → Backend Engineer at the broker side.
• “Compliance questions for the broker’s clients” → Compliance Officer at the broker side.
• “Cost / commercial questions” → out of this site’s scope; broker-vendor commercial discussion.

Verified through

2026-05-14

---

AI-generated and not legal, financial, or compliance advice. See the project README for full disclaimer.