Handle RFIs - Whop Docs

An RFI (Request for Information) is raised when Whop needs something extra from a user — a document, a tax ID, a business detail. Each open RFI appears as an item in the verification’s requested_information array, and the verification’s status becomes action_required until every item is answered. Every item tells you exactly what to collect: a stable field key, an input type, a human-readable label and description, allowed options for select fields, and the exact upload slots for document requests. See every RFI field for the full catalog.

How RFIs work

Information is requested

Whop flags that something is needed. The verification status changes to action_required and an identity_profile.needs_action webhook fires.

You read the items

Call GET /api/v1/verifications?account_id={biz_ tag}. The requested_information array on each verification lists what’s needed and what type of answer to collect.

You collect and submit

Get the info from your user and send it back via PATCH /api/v1/verifications/{id} with a requested_information array. We route each answer to the right place.

Review continues

Answered items leave the array. Once it’s empty, the status returns to approved. If an answer is rejected, the item reappears with error_message explaining why — resubmit it.

Reading RFIs

cURL

curl "https://api.whop.com/api/v1/verifications?account_id=biz_xxxxxxxxxxxxx" \
  -H "Authorization: Bearer $WHOP_API_KEY"

When RFIs are outstanding, the verification looks like:

{
  "id": "idpf_xxxxxxxxxxxxx",
  "kind": "individual",
  "status": "action_required",
  "requested_information": [
    {
      "id": "inrqi_xxxxxxxxxxxxx",
      "field": "date_of_birth",
      "type": "date",
      "label": "Date of Birth",
      "description": "Your date of birth, used to confirm your identity.",
      "requested_files": [],
      "options": [],
      "error_message": null
    },
    {
      "id": "inrqi_yyyyyyyyyyyyy",
      "field": "business_structure",
      "type": "select",
      "label": "Business Structure",
      "description": "Your business's legal structure, such as an LLC, corporation, or sole proprietorship.",
      "requested_files": [],
      "options": ["single_member_llc", "multi_member_llc", "sole_proprietorship", "private_corporation"],
      "error_message": null
    },
    {
      "id": "inrqi_zzzzzzzzzzzzz",
      "field": "payout_upload_request",
      "type": "files",
      "label": "Payout Destination Verification",
      "description": "Upload the requested payout verification document.",
      "requested_files": [
        {
          "label": "Bank Statement",
          "category": "payout_verification_document",
          "kind": "Bank Statement",
          "is_optional": false,
          "multiple": false
        }
      ],
      "options": [],
      "error_message": null
    }
  ]
}

Item fields

Field	Description
`id`	The item identifier, prefixed `inrqi_` — include it when submitting an answer
`field`	Stable field key, such as `ssn` or `business_description` — see every RFI field
`type`	What to collect: `text`, `date`, `phone`, `address`, `select`, or `files`
`label`	Human-readable name for the field, such as `Social Security Number`
`description`	Instructions for this item, or `null`
`options`	Allowed values for a `select` field — the submitted value must be one of these. Empty for other types.
`requested_files`	Upload slots for a `files` item. Each slot has a `label`, a `category` and `kind` to copy back when uploading, `is_optional`, and `multiple` (whether the slot accepts more than one file). Empty for non-file items.
`error_message`	Why a previous answer was rejected, or `null` if nothing has been rejected

Only open items are returned — answered items leave the array, so anything still present is owed. The verification stays action_required until the array is empty.

Answering RFIs

Send a PATCH to the verification’s idpf_ tag with a requested_information array. Each entry needs the item id and exactly one answer payload matching the item’s type:

Item `type`	Answer payload
`text`, `date`, `phone`, `select`	`value`
`address`	`address` object
`files`	`files` array

You can answer several items in one request:

cURL

curl -X PATCH https://api.whop.com/api/v1/verifications/idpf_xxxxxxxxxxxxx \
  -H "Authorization: Bearer $WHOP_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "requested_information": [
      { "id": "inrqi_xxxxxxxxxxxxx", "value": "1990-01-15" },
      { "id": "inrqi_yyyyyyyyyyyyy", "value": "single_member_llc" }
    ]
  }'

Text, date, phone, and select values

Pass the answer as value. Dates use YYYY-MM-DD, phone numbers use E.164 format (+12125550123), and select values must be one of the item’s options.

Addresses

Pass an address object:

cURL

curl -X PATCH https://api.whop.com/api/v1/verifications/idpf_xxxxxxxxxxxxx \
  -H "Authorization: Bearer $WHOP_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "requested_information": [
      {
        "id": "inrqi_xxxxxxxxxxxxx",
        "address": {
          "line1": "123 Spring Street",
          "city": "New York",
          "state": "NY",
          "postal_code": "10012",
          "country": "US"
        }
      }
    ]
  }'

PO boxes are not accepted for personal or business addresses.

Documents

Upload the file first, then reference it in the answer. Fill one entry per slot in requested_files, copying the slot’s category and kind:

cURL

curl -X PATCH https://api.whop.com/api/v1/verifications/idpf_xxxxxxxxxxxxx \
  -H "Authorization: Bearer $WHOP_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "requested_information": [
      {
        "id": "inrqi_zzzzzzzzzzzzz",
        "files": [{
          "attachment_id": "file_xxxxxxxxxxxxx",
          "category": "payout_verification_document",
          "kind": "Bank Statement"
        }]
      }
    ]
  }'

Each file entry takes either an attachment_id (a file_ ID from the upload flow) or a direct_upload_id from a direct upload. Documents must be JPEG, PNG, or PDF, up to 32 MB. When requested_files lists more than one slot with is_optional: true — for example several accepted document kinds — providing any one of them satisfies the request. Slots with is_optional: false are all required, such as the front and back of an ID.

Sensitive values

Tax and government ID numbers (ssn, ein, company_tax_id, personal_id_number) are submitted like any other value. They are tokenized in transit before reaching Whop’s systems, and only the tokenized reference is ever stored:

cURL

curl -X PATCH https://api.whop.com/api/v1/verifications/idpf_xxxxxxxxxxxxx \
  -H "Authorization: Bearer $WHOP_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "requested_information": [
      { "id": "inrqi_xxxxxxxxxxxxx", "value": "123-45-6789" }
    ]
  }'

If you already tokenize values yourself (Basis Theory), pass the token ID with value_type: "vault_token" instead.

Rejected answers

If a submitted answer is rejected, the item returns to requested_information with error_message set:

{
  "id": "inrqi_xxxxxxxxxxxxx",
  "field": "business_website",
  "type": "text",
  "label": "Business website or social profile",
  "error_message": "The website provided could not be reached.",
  "requested_files": [],
  "options": []
}

Fix the underlying issue and resubmit with the same item id. The verification stays action_required until the corrected answer is accepted.

Every RFI field

Each item’s field key is one of the values below.

Personal details

Field	Type	What to submit
`first_name`	`text`	Legal first name, capitalized (`Jane`)
`last_name`	`text`	Legal last name, capitalized (`Doe`)
`creator_legal_name`	`text`	Full legal name as it appears on official documents
`date_of_birth`	`date`	`YYYY-MM-DD`
`email`	`text`	Email address
`creator_email_address`	`text`	An email address where we can reach the user
`phone_number`	`phone`	E.164 format with country code (`+12125550123`)
`personal_address`	`address`	Current residential address — no PO boxes
`occupation`	`text`	SOC occupation code (`15-1132`), or `SELFEMP`, `STUDENT`, `RETIRED`, `UNEMPLO`, `OTHERXX`
`annual_salary`	`text`	Approximate yearly income in USD, digits only

Tax and government ID numbers

These values are tokenized in transit — see sensitive values.

Field	Type	What to submit
`ssn`	`text`	US Social Security Number, `XXX-XX-XXXX`
`ein`	`text`	US Employer Identification Number, `XX-XXXXXXX`
`company_tax_id`	`text`	Company tax ID in the issuing country’s format
`personal_id_number`	`text`	Government-issued personal ID number (passport, driver’s license, national ID)
`personal_id_number_country`	`select`	Country that issued the ID number — pick from `options`
`country_of_issue`	`text`	Two-letter country code of the issuing country (`US`)

Identity documents

Field	Type	What to submit
`identity_document`	`files`	Government-issued photo ID. Two slots: `identity_document_front` and `identity_document_back`

Business details

Field	Type	What to submit
`business_name`	`text`	Legal name the business is registered under
`trade_name`	`text`	Public-facing name if different from the legal name (DBA)
`company_title`	`text`	The company’s name
`business_structure`	`select`	Legal structure — one of `options`, e.g. `single_member_llc`, `sole_proprietorship`, `private_corporation`
`account_type`	`select`	`individual`, `company`, or `non_profit`
`business_representative_title`	`select`	Representative’s title — one of `options`, e.g. `CEO`, `Owner`, `Manager`
`industry_type`	`text`	Industry the business operates in
`business_description`	`text`	100–1000 characters: what is sold, what customers receive after payment, and where they access it
`product_description`	`text`	The product or service sold
`business_phone_number`	`phone`	E.164 format with country code
`business_address`	`address`	Registered business address — no PO boxes
`business_website`	`text`	Business website URL
`social_media_or_website`	`text`	Website, or a public social profile that represents what is sold
`store_page_url`	`text`	Link to the store or product page
`expected_monthly_volume`	`text`	Expected monthly processing volume in USD, digits only
`account_purpose`	`text`	What the account is primarily used for

Business documents

Field	Type	What to submit
`business_verification_document`	`files`	Document confirming the company’s legal identity — IRS Letter 147C, SS-4, or EIN Assistance Letter. Front slot required, back optional
`business_incorporation_papers`	`files`	Official incorporation documents
`processing_statements`	`files`	Statements from a previous payment processor showing processing history — not bank statements
`proof_of_fulfillment`	`files`	Screenshot, recording, or file showing what customers receive after purchase
`proof_of_funnel`	`text` or `files`	Where customers come from — a social account, website, or landing page

Payout account documents

Field	Type	What to submit
`payout_upload_request`	`files`	The document named by the slot’s `kind` (for example `Bank Statement`), with category `payout_verification_document`

Review questions

Field	Type	What to submit
`anything_else`	`text`	Anything else the review team should know
`accept_tos`	`text`	Confirmation that the terms of service are accepted

​How RFIs work

​Reading RFIs

​Item fields

​Answering RFIs

​Text, date, phone, and select values

​Addresses

​Documents

​Sensitive values

​Rejected answers

​Every RFI field

​Personal details

​Tax and government ID numbers

​Identity documents

​Business details

​Business documents

​Payout account documents

​Review questions

How RFIs work

Reading RFIs

Item fields

Answering RFIs

Text, date, phone, and select values

Addresses

Documents

Sensitive values

Rejected answers

Every RFI field

Personal details

Tax and government ID numbers

Identity documents

Business details

Business documents

Payout account documents

Review questions