Merchant Underwriting: Each Application Decided on Its Own Packet and Test Charges

Applications decided from the ticket, packet and test charges.

What it solves: Merchant applications are underwritten in one Kylon room. Agents read the HubSpot ticket, the Box packet and the merchant’s Stripe test charges, propose a decision and reserve, and the underwriting manager approves every decision before a merchant hears back.

How it runs

  1. Review Each ticket is checked against the policy in order, using the Box packet and the Stripe test charges Who decides: Underwriters accept or change each proposal
  2. Allocation Applications that need a person are assigned within each underwriter’s weekly capacity Who decides: The underwriting manager approves the assignments
  3. Reserve schedule audit Unapproved and duplicate lines are removed and each amount is checked against the table Who decides: The underwriting manager approves the schedule
  4. Compliance batch Applications named in the screening batch are re-run from the first check Who decides: The compliance analyst confirms each hit and the underwriting manager approves any change
  5. Category revision Every electronics application is re-run under the revised table Who decides: The underwriting manager approves changed decisions and reserves
  6. Chargeback correction A corrected chargeback history re-runs the merchant it belongs to Who decides: The assigned underwriter decides
  7. Closeout Notes per category, with still-held applications carried to next week Who decides: The underwriting manager signs off

Tools it connects

  • Box: Holds each merchant’s packet with registration, bank statements and processing history.
  • Google Drive: Keeps the policy, the category table and the draft reserve schedule.
  • HubSpot: Holds the application tickets, decisions, assignments and closeout notes.
  • Stripe: Shows the merchant’s test charges and descriptors, which Nova reads as evidence only.
  • Gmail (optional): Carries merchant correspondence and the verification provider’s replies, answered through drafts a person sends.
  • Slack (optional): Is where compliance posts screening batches and underwriters flag capacity.

Set-up prompt

Paste this into Kylon, or start it in one click below.

Set up our merchant underwriting desk in this Room. Take it one step at a time and wait for my OK before you move on.

1. Connect Box, Google Drive, HubSpot and Stripe first, since the first run needs them. Tell me which ones still need connecting. Gmail and Slack can wait until a step uses them.
2. Ask me who works this desk: the underwriting manager, the underwriters, the compliance analyst and the onboarding managers. Help me invite them to this Room.
3. Build an Underwriting Queue App with columns New, In Review, Held and Decided, one record per application. Pull open tickets from HubSpot and match each to its Box packet and Stripe test charges.
4. Check each application in order: duplicate, screening hit, category, packet and test charges, then reserve. The first check that fails decides the outcome. Propose a decision, a reason and a reserve line where our rules call for one. Show me every application that fails a check.
5. Draft information requests, decision emails and replies to the verification provider in Gmail. Draft each reserve line with the table row and amount. Nothing is sent and HubSpot is not updated until the underwriting manager approves every decision and every reserve line.
6. Write the precedence order and who approves what into this Room's guideline so every re-run starts from the first check.
7. After one clean week, offer to turn the weekly queue review into an Automation.

Start with step 1. Once the tools are connected, or I say the rest can wait, ask me for our rules one at a time.

Start in Kylon · Full page on kylon.io