Business Overview

<!-- ── TITLE ─────────────────────────────────────────── -->
<h1>Welcome to the ProphetX ISV!</h1>

<p>
  ProphetX is a CFTC-regulated sports prediction market exchange. Through the ISV program, partners embed ProphetX's exchange infrastructure — markets, order execution, KYC, and settlement — directly into their own product. You own the product experience. ProphetX handles the regulated layer underneath.
</p>
<p>
  Before you write any code, there are four integration decisions to work through with your ProphetX contact. This page walks you through each one. The API is REST-based with webhook delivery for real-time updates, all requests are authenticated, and sandbox credentials are available so you can test against a live-shaped environment before going to production.
</p>

<hr>

<!-- ── HOW IT WORKS ───────────────────────────────────── -->
<h2>How the integration works</h2>

<div class="how-cards">
  <div class="how-card">
    <div class="step-num">1</div>
    <div class="arrow">→</div>
    <h3>Integrate to ISV APIs</h3>
    <p>Connect to ProphetX's ISV API suite — market data, user onboarding, order placement, and settlement webhooks — all server-to-server from your backend.</p>
  </div>
  <div class="how-card">
    <div class="step-num">2</div>
    <div class="arrow">→</div>
    <h3>Build your front end</h3>
    <p>You own the full UI and UX. Show ProphetX markets alongside your own content however you choose. ProphetX is invisible to your end users.</p>
  </div>
  <div class="how-card">
    <div class="step-num">3</div>
    <h3>ProphetX handles the rest</h3>
    <p>Trade execution, settlement, KYC, and CFTC compliance all run on ProphetX. Your users trade; ProphetX settles.</p>
  </div>
</div>

<hr>

<!-- ── FOUR DECISIONS ─────────────────────────────────── -->
<h2>Four things to decide before you build</h2>
<p>
  Work through these with your ProphetX contact during onboarding. Each decision affects how your integration is structured and what you need to build.
</p>

<!-- ── DECISION 1: WALLET MODEL ──────────────────────── -->
<div class="step-card">
  <div class="step-card-header">
    <div class="step-num-lg">1</div>
    <div>
      <h3>Wallet model</h3>
      <div class="step-sub">Determines whether you use ProphetX payment rails or your own</div>
    </div>
  </div>
  <div class="step-card-body">
    <p>Your wallet model is set during commercial onboarding and cannot be changed at runtime. It determines how money moves between your platform and ProphetX — and whether you build your own payment flows or embed ProphetX's.</p>

    <div class="wallet-diagram">
      <div class="wd-center">
        <div class="wd-decision">
          <div class="wd-label">Choose one</div>
          <div class="wd-title">Which model did ProphetX provision?</div>
          <div class="wd-sub">Agreed during commercial onboarding · Cannot change at runtime</div>
        </div>
        <div class="wd-fork"><div class="wd-fork-l"></div><div class="wd-fork-gap"></div><div class="wd-fork-r"></div></div>
        <div class="wd-branches">
          <div class="wd-branch">
            <div class="wd-model">
              <div class="wm-tag">Standing Fund</div>
              <div class="wm-name">You manage payments</div>
              <div class="wm-desc">You pre-fund a standing fund wallet at ProphetX via bank wire. You own user wallets and payment flows on your side. ProphetX debits the standing fund wallet per trade and notifies you via webhook.</div>
            </div>
            <div class="wd-conn"></div>
            <div class="wd-result plain">
              <div class="wr-title">You build the payment UI</div>
              <div class="wr-desc">Use your own payment rails. ProphetX has no role in the deposit or withdrawal flow. Daily reconciliation + net settlement on agreed cadence.</div>
            </div>
          </div>
          <div class="wd-branch">
            <div class="wd-model">
              <div class="wm-tag">Individual Wallets</div>
              <div class="wm-name">ProphetX hosts payments</div>
              <div class="wm-desc">Each user has their own ProphetX wallet, created on KYC success. Users deposit directly through ProphetX-hosted modals you embed.</div>
            </div>
            <div class="wd-conn"></div>
            <div class="wd-result green">
              <div class="wr-title">ProphetX provides the payment UI</div>
              <div class="wr-desc">Embed ProphetX-hosted deposit and withdrawal modals in your app. See Decision 2 below.</div>
            </div>
          </div>
        </div>
      </div>
    </div>
  </div>
</div>

<!-- ── DECISION 2: DEPOSIT & WITHDRAWAL ──────────────── -->
<div class="step-card">
  <div class="step-card-header">
    <div class="step-num-lg">2</div>
    <div>
      <h3>Deposits &amp; withdrawals</h3>
      <div class="step-sub">Individual wallet model only</div>
    </div>
  </div>
  <div class="step-card-body">
    <p>If you're on the Individual wallet model, ProphetX provides pre-built deposit and withdrawal modals you embed directly in your app. Users complete the deposit or withdrawal inside the modal — funds go directly to and from their individual ProphetX wallet. You never handle the money.</p>

    <div class="option-split">
      <div class="option-box highlighted">
        <div class="option-label">Deposit modal</div>
        <h4>Users fund their ProphetX wallet</h4>
        <p>Surface the ProphetX deposit modal at the point in your app where users add funds. Supported providers: Aeropay, ZeroHash, and wire. The modal is ProphetX-hosted and branded, but configurable to match your app's theme.</p>
      </div>
      <div class="option-box highlighted">
        <div class="option-label">Withdrawal modal</div>
        <h4>Users withdraw their winnings</h4>
        <p>Surface the ProphetX withdrawal modal where users cash out. Settlement credits go directly to the user's wallet — no wire to you. Withdrawal is processed through the same payment providers as deposit: Aeropay, ZeroHash, and wire.</p>
      </div>
    </div>

    <div class="callout">
      <strong>Standing Fund partners</strong>
      If you're on the Standing Fund model, skip this section — you own the deposit and withdrawal flow entirely using your own payment rails. See the <a href="https://isv-docs.prophetx.co/docs/wallets">Wallets</a> section for reconciliation and net settlement details.
    </div>
  </div>
</div>

<!-- ── DECISION 3: T&Cs ───────────────────────────────── -->
<div class="step-card">
  <div class="step-card-header">
    <div class="step-num-lg">3</div>
    <div>
      <h3>Terms &amp; Conditions</h3>
      <div class="step-sub">CFTC requirement — all ISV users must accept ProphetX T&Cs before trading</div>
    </div>
  </div>
  <div class="step-card-body">
    <p>CFTC regulations require that every user trading on ProphetX has explicitly accepted ProphetX's Terms and Conditions. T&C acceptance must be captured and confirmed to ProphetX before a user can place their first trade. You have two options for how to handle this:</p>

    <div class="option-split">
      <div class="option-box highlighted">
        <div class="option-label">Option A</div>
        <h4>ProphetX T&amp;C modal</h4>
        <p>ProphetX provides a pre-built T&C modal you surface as part of your onboarding flow. The user reviews and accepts the ProphetX T&C documents inside the modal. Acceptance is recorded with a timestamp and automatically confirmed to ProphetX. Nothing to build on your side.</p>
      </div>
      <div class="option-box">
        <div class="option-label">Option B</div>
        <h4>Co-joined T&amp;C page</h4>
        <p>If you want to combine ProphetX T&Cs with your own, you can design a single T&C page. ProphetX has specific design requirements for this approach — ProphetX branding must be prominently displayed on the page and on all T&C documents. Reach out to your ProphetX contact for the design requirements before building.</p>
      </div>
    </div>

    <div class="callout">
      <strong>How acceptance is tracked</strong>
      T&C acceptance is a one-time step per user. ProphetX keeps a log of when each document was accepted and which version was in effect at the time. If ProphetX updates its T&C documents, users will need to re-accept before trading again — your integration will be notified so you can prompt them at the right moment.
    </div>

  </div>
</div>

<!-- ── DECISION 4: KYC ────────────────────────────────── -->
<div class="step-card">
  <div class="step-card-header">
    <div class="step-num-lg">4</div>
    <div>
      <h3>KYC — user identity verification</h3>
      <div class="step-sub">CFTC requirement — all ISV users must be KYC'd before trading</div>
    </div>
  </div>
  <div class="step-card-body">
    <p>
      Even though you own the customer relationship, CFTC regulations require ProphetX to know and monitor every user trading on the platform at the individual level. User identity must be tied to every trade. ProphetX runs KYC and AML — you choose how user information gets to us.
    </p>
    <p>You have two options depending on whether you already collect identity information from your users:</p>

    <div class="option-split">
      <div class="option-box">
        <div class="option-label">Option A — Already collecting KYC data</div>
        <h4>Send PII to ProphetX behind the scenes</h4>
        <p>If you already collect identity details from your users as part of your own onboarding, you can pass that information directly to ProphetX via the account creation API — no additional user-facing step required. ProphetX runs KYC and AML in the background and returns a status: <code>PENDING</code>, <code>SUCCESS</code>, or <code>FAILURE</code>. The user never sees ProphetX — it's entirely invisible to them.</p>
      </div>
      <div class="option-box highlighted">
        <div class="option-label">Option B — Not yet collecting KYC data</div>
        <h4>Use the ProphetX Verified modal</h4>
        <p>ProphetX provides a Verified modal you can embed in your onboarding flow. The user enters their <strong>phone number</strong> and <strong>last 4 digits of their SSN</strong> — the modal then pulls their full KYC details automatically and presents them for confirmation. Once the user confirms, ProphetX runs KYC in the background. No manual data entry of full PII required.</p>
      </div>
    </div>

    <div class="callout">
      <strong>Before calling KYC — verify email and phone first</strong>
      CFTC requires ProphetX to have a verified phone number and email address on record for every user before they can trade. Your onboarding flow must verify both before calling the ProphetX account creation endpoint — ProphetX will reject unverified contact details at the API level.
    </div>

    <h3>How KYC statuses work</h3>
    <table>
      <thead><tr><th>Status</th><th>What it means</th><th>What to do</th></tr></thead>
      <tbody>
        <tr><td><code>PENDING</code></td><td>KYC check is in progress</td><td>Poll <code>GET /private/v1/users/USERID/kyc</code> until status resolves</td></tr>
        <tr><td><code>SUCCESS</code></td><td>User is verified and can trade</td><td>Proceed to T&C acceptance, then deposit (if Individual model)</td></tr>
        <tr><td><code>FAILURE</code></td><td>KYC could not be completed automatically</td><td>Direct user to contact <a href="#">[email protected]</a> for manual review</td></tr>
      </tbody>
    </table>
  </div>
</div>

<hr>

<!-- ── WHAT'S IN THESE DOCS ───────────────────────────── -->
<h2>What's in these docs</h2>

<table>
  <thead><tr><th>Section</th><th>What it covers</th></tr></thead>
  <tbody>
    <tr><td><strong><a href="https://isv-docs.prophetx.co/docs/technical-overview#">Technical Overview</a></strong></td><td>Full technical orientation — request path, path prefixes, reading order, and the complete glossary. Read this before writing code.</td></tr>
    <tr><td><strong>User Management</strong></td><td>Creating users, running KYC, recording T&C acceptance, and managing wallets. The four decisions above map directly to this section.</td></tr>
    <tr><td><strong>Order Management</strong></td><td>Browsing fixtures and markets, placing market orders, and building parlays.</td></tr>
    <tr><td><strong>Push Integration</strong></td><td>Registering a webhook receiver so ProphetX pushes order and settlement events to you in real time.</td></tr>
    <tr><td><strong>Frontend Integrations</strong></td><td>Embedding ProphetX-hosted deposit, withdrawal, KYC, and T&C components. Relevant primarily for Individual wallet model partners.</td></tr>
    <tr><td><strong>Error Reference</strong></td><td>All error codes, rate limits, and configuration constants.</td></tr>
  </tbody>
</table>

<div class="callout info">
  <strong>Ready to dive in?</strong>
  Head to <a href="https://isv-docs.prophetx.co/docs/technical-overview#/">Technical Overview</a> for the full technical orientation, then work through each section in sequence. If you haven't agreed your wallet model and KYC approach with your ProphetX contact yet, do that first — it affects every section that follows.
</div>

<p style="font-size:13px; color:var(--gray-600); margin-top: 8px;">If anything is unclear or missing, reach out to your ProphetX integration contact. We'd rather hear from you early than have you guessing.</p>

<div class="next-nav">
  <a href="https://isv-docs.prophetx.co/docs/technical-overview#/#">
    <span class="nav-label">Next →</span>
    <span class="nav-title">Technical Overview</span>
  </a>
</div>