# Going-live checklist The final review before we make our first call. Work through this list with your customer success contact, or independently if you've done this before. > There is no "Go live" button. The platform's real activation gate is the issuance of your `ca_*` API key — that only succeeds once the FSM has walked all the way to `verified` AND Stripe Connect payouts are enabled AND the current MSA is on file. The compliance engine then refuses outreach on any placement until those conditions hold. ## 1. Account verified * [ ] Onboarding wizard's status check (`GET /v1/creditors/me/status`) returns `status: "verified"`. * [ ] `creditor.verified` audit event present in the timeline (records the verification method: `middesk_kyb+sanctions`, `manual_admin`, etc.). * [ ] Legal entity name on your account is exactly what you want our voice agent to say on calls. ## 2. Bank link complete (Stripe Connect Express) * [ ] Stripe Connect Express onboarding finished. * [ ] Stripe has sent the `account.updated` webhook with `payouts_enabled=true` (the platform won't transition you past `pending_bank_link` without it). * [ ] You can see your linked account in the dashboard. ## 3. MSA accepted * [ ] Current MSA version (today: `msa_v1`) accepted via the click-through flow. * [ ] You downloaded the audit certificate PDF — the signed URL is only valid for 1 hour, so save it now. ## 4. API key issued * [ ] `POST /v1/creditors/me/issue-api-key` returned a `ca_*` key. * [ ] You stored the plaintext key in your secret manager. **It is returned exactly once.** If lost, you'll need an admin to rotate. ## 5. Strategy set * [ ] Confirm `posture_default` (preserve / escalate) matches what you want for new placements. This is the only creditor-tunable strategy knob today — see [Configuring your strategy](/for-creditor-partners/creditor-onboarding/configuring-your-strategy.md). * [ ] (Optional) `webhook_url` set if you want event callbacks. ## 6. Compliance basics understood * [ ] You understand the difference between 3P and 1P. 3P is what's built today. * [ ] You understand what the compliance engine handles automatically and what stays your responsibility — see [Compliance basics](/for-creditor-partners/creditor-onboarding/compliance-basics.md). * [ ] You've reviewed the [Debtor rights overview](/for-debtors/compliance-and-rights/debtor-rights-overview.md) so you can answer your team's questions. ## 7. Placements uploaded and spot-checked * [ ] At least one placement has cleared enrichment and is not flagged with `volume_quota_exceeded` or other safety flags. * [ ] Spot-check three placements: * [ ] Debtor business name and contact info look right. * [ ] Invoice reference and amount match your records. * [ ] Notes / description are what you want our agent to reference. * [ ] No placements stuck in `needs_review` you don't recognize. If any are, check why and either recall or fix. ## 8. Communication test (optional) * [ ] Ask your customer success contact to set up a test call so you can hear our agent's introduction using your legal entity name. * [ ] Verify the platform's outbound email lands in your inbox (and not spam) when sent to your address. ## How activation actually happens Once the API key is issued, the planner can pick up `ready` placements and start scheduling outreach. There is no separate "go live" action — the moment all the gates above are satisfied and you've uploaded placements, the system is live. If you want a soft launch, the practical lever is to start with a small batch (a handful of placements). The planner's per-state contact-time rules and the volume policy will pace things naturally; there is no per-creditor "throttle" knob today. ## What happens in the first 48 hours * Outreach starts as soon as the planner runs for each placement and the compliance engine returns `can_call=true` within the legal contact window for the debtor's state. * The dashboard's live feed updates in real time. See [live feed overview](/for-creditor-partners/creditor-operations/live-feed-overview.md). * You receive event callbacks at your configured `webhook_url` (if set). ## Common first-day situations * **Debtor pays immediately.** Placement transitions to `paid`. Payment shows up in the dashboard and on your next remittance. * **Debtor disputes.** Placement transitions to `disputed`; you get a notification. See [Responding to a dispute](/for-creditor-partners/creditor-operations/responding-to-a-dispute.md). * **Debtor offers a plan.** The agent records the proposal; settlement logic in `src/services/strategy/settlement.py` evaluates it. Operator review may be required. * **Debtor unreachable.** The planner keeps trying within the state's frequency cap. Terminal "no contact" outcomes end up in `closed_uncollected` after the planner exhausts options. ## TODO * Screenshot: wizard "API key issued" screen. * Screenshot: post-activation live feed. * Screenshot: example first-day webhook payload. *** Last reviewed: 2026-05-24 by Customer Success. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://help.moderncollections.io/for-creditor-partners/creditor-onboarding/going-live-checklist.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.