EIN application

Employer Identification Number (EIN) is a federal tax ID issued by the IRS for your customer’s business. This guide describes how the standalone EIN order fits the same service cart → order → Customer Portal pattern as other standalone products.

Coming soon: The EIN standalone service may not yet appear in GET /service-carts for all partner accounts. Confirm availability with [email protected] before go-live. Until the cart is enabled, treat the JSON below as the intended integration shape.

Related: Partner products overview · State requirements reference · Standalone flows (user journey)

When to use this flow

Use the standalone EIN service when the entity already exists (or will exist) and the customer only needs an EIN, without a full incorporation package. If EIN is bundled with formation, use Incorporation Service Example instead.

Service slug and catalog

1. Call Get Service Carts and find the EIN entry when it is available for your program.
2. Use that item’s slug for Get Service Configuration and Create New Order.

The examples below use the slug ein or ein-application. Replace with the slug returned for your account.

API flow

Step	Method	Endpoint
1. List carts	GET	externalCart.index
2. Configuration, input_fields, catalog	GET	externalCart.getCart
3. NAICS list (if required)	GET	businessClassification.index
4. Create order	POST	order.store
5. Submit order (if required)	POST	order.submitOrder
6. Post-checkout (optional)	GET	order.getOrderPostCheckout
7. Get order (optional)	GET	order.getOrder

Follow Standalone Service Example for whether submit is required.

State-specific requirements (discovery)

EIN is a federal filing, but input_fields still depend on entity type and address. Use Get Service Configuration for your EIN slug and supply business_data (including formation_state where the entity is formed or principal address state) per the returned keys.

Example: Get Service Configuration

GET {baseUrl}/service-carts/ein?service=ein
Authorization: Bearer {token}

Abbreviated success payload:

{
  "success": true,
  "data": {
    "name": "EIN Application",
    "slug": "ein",
    "description": "Federal Employer Identification Number (EIN) application.",
    "input_fields": [
      {
        "name": "Entity legal name",
        "key": "business_data.name",
        "type": "string",
        "description": "Legal name for IRS records",
        "validation_rules": ["required"]
      },
      {
        "name": "Formation state",
        "key": "business_data.formation_state",
        "type": "enum",
        "description": "State of formation or principal business (two-letter code)",
        "validation_rules": ["required", "exists:states,abbr"]
      }
    ],
    "catalog": [
      {
        "sku": "SF_EIN_EXAMPLE_SG_0",
        "name": "EIN Application",
        "item_type": "product",
        "has_gov_fee": false,
        "price": 79,
        "package": false
      }
    ]
  }
}

sku and field keys are illustrative until the live cart is enabled.

Example: Create order

{
  "service": "ein",
  "email": "[email protected]",
  "first_name": "Chris",
  "last_name": "Lee",
  "phone_number": "5554443333",
  "consent_sms": false,
  "business_data": {
    "name": "Acme Holdings LLC",
    "type": "LLC",
    "formation_state": "WY",
    "category": "541211",
    "address": "30 N Gould St",
    "city": "Sheridan",
    "state": "WY",
    "zip": "82801"
  }
}

Abbreviated response:

{
  "success": true,
  "data": {
    "message": "Order created successfully",
    "order_uuid": "d4e5f6a7-b8c9-0123-def0-234567890123"
  }
}

Example: Submit order

{
  "order_uuid": "d4e5f6a7-b8c9-0123-def0-234567890123",
  "skus": ["SF_EIN_EXAMPLE_SG_0"],
  "total_amount": 79.0,
  "payment_method_nonce": null,
  "service": "ein"
}

Fulfillment

1. Questionnaire: Customers typically complete an EIN questionnaire in the Customer Portal; see Standalone flows for the status narrative.
2. Webhooks: Track order_status_change and order_processing_status_change. See Webhooks.
3. Completion: The IRS issues the EIN; documents appear under the customer’s account per your configuration.

Errors and edge cases

• Responsible party / SSN: Sensitive fields may be collected in Swyft Customer Portal rather than initial POST /orders, depending on cart configuration.
• Rejections: IRS rejections surface as order tasks or rejections in the portal; handle via Swyft Customer Portal and webhooks.