Skip to main content

Application forms

V
Written by Victor Fteha

Every merchant submission becomes a deal in MCA Pilot: your application form or CRM workflow sends the data to us by webhook, we create the deal, assign it to the right rep, and run AI underwriting automatically. Pick your intake path below — Jotform, DocuSeal, a custom form, GoHighLevel/MCA Simplified, or a webhook with a separate file form — and follow its setup guide. Each path starts with a one-time setup where we generate your webhook URL and map your form fields to deal fields.

Choose your intake path

Match your platform to the guide below; each guide covers its own setup, rep assignment, and troubleshooting. If your platform is not listed, see How to integrate your application form with MCA Pilot — we build custom integrations for platforms like Fillout, and connect Zoho during onboarding.

Intake path

Best for

Setup guide

Jotform

The most common setup, with file attachments delivered through an API key

DocuSeal

Applications that need e-signature

Custom form

Developer-built forms that can send HTTP callbacks or webhooks

GoHighLevel / MCA Simplified

CRM-driven intake where applying a tag to a contact pushes it to MCA Pilot as a deal

Webhook with a separate file form

Bank statements or other files that come from a different form than the application

What happens after a merchant submits

The platform you pick only changes the setup steps; after submission, every intake path follows the same workflow.

  • The form platform sends the submission to your webhook URL, and MCA Pilot maps the fields to deal fields and creates the deal.

  • The deal is auto-assigned to the rep whose form ID is on their profile, set at Settings → Workspace → Edit → Unique App ID.

  • File uploads such as bank statements, tax returns, and voided checks land on the deal, and AI underwriting and document verification run automatically.

  • The rep selects the funders and submits in one action. MCA Pilot sends an independent submission to each selected funder, and one funder's validation error does not block the rest.

  • Every submission is logged in the Submissions table and lands on the deal, where you can mark declines, paste responses, or add offers.

A deal being created does not mean it is ready to send to funders. Many funder integrations require specific fields, so a submission with missing merchant data or documents can still be blocked when you try to submit.

Before you begin

First-time setup is done with our support team; adding a new rep's form afterward is self-service.

  • Share your form link or builder access with us through the blue chat icon in MCA Pilot or email [email protected]. We generate your unique webhook URL and map your form fields to deal fields.

  • Give each rep their own form, then paste the form's ID into their profile at Settings → Workspace → click the rep → EditUnique App ID. Deals only auto-assign when a form ID is linked to a rep profile; for new reps, clone an existing form and reuse the same webhook URL.

  • For Jotform file attachments, send us an API key with Read Access once per account so we can download bank statements and other files from submissions.

Verify your first submission

Submit one test application and confirm the result before going live — replaying a submission can create duplicate deals instead of updating the existing one.

  1. Submit a test application with realistic merchant data.

  2. Open MCA Pilot and confirm the deal appears.

  3. Confirm the deal is assigned to the expected rep.

  4. Confirm the business name, owner details, and monthly revenue match the submitted values.

  5. If the form includes uploads, confirm the files appear in the Bank Statements field. If files are missing or you need to confirm completeness, open the Underwrite tab and run AI Docs Check.

Related guides

These articles cover the common follow-ups and failure modes for application intake.

Did this answer your question?