Stedi now blocks claim attachments for unsupported payers

Jan 22, 2026

If you try to submit a claim with electronic attachments to a payer who doesn't support them, Stedi now blocks the request before it reaches the payer. This affects 837P professional, 837D dental, and 837I institutional claims.

Electronic claim attachments let you send supporting documents – like X-rays and medical records – alongside claims in Stedi. Stedi lets you submit claims and claim attachments electronically using JSON API, X12 API, or SFTP.

However, not every payer supports electronic claim attachments. Previously, if you submitted an attachment to a payer who didn’t support them, the payer would reject the attachment as an error downstream. This could delay payment for the provider.

Now, Stedi checks payer support upfront and catches the issue before the claim reaches the payer. That means faster turnaround times for errors – and faster payments for providers.

Errors

If you submit a claim with attachments to an unsupported payer using Stedi's JSON or X12 Claim Submission APIs, you'll receive an error response with a 400 Bad Request HTTP status code and an error message:

{
  "code": "TRANSACTION_TYPE_NOT_SUPPORTED",
  "message": "Payer 62308 (Stedi Payer ID HGJLR) is not configured for Unsolicited Claim Attachment (275). Please check our published payer list or contact Stedi support to resolve."
}

If you submit a claim with attachments to an unsupported payer using SFTP, Stedi will reject the claim with a 277CA claim acknowledgment:

STC*A7:N21*[DATE]*PR*[AMOUNT]********Payer 62308 (Stedi Payer ID HGJLR) is not configured for Unsolicited Claim Attachment (275). Please check our published payer list or contact Stedi support to resolve

Check payer support

To avoid errors, check whether a payer supports electronic claim attachments using the Stedi Payer Network site or Stedi’s Payers API.

For example, in a Search Payers API response:

{
  "items": [
    {
      "stediId": "HGJLR",
      "displayName": "Cigna",
      "primaryPayerId": "62308",
      "transactionSupport": {
        "unsolicitedClaimAttachment": "NOT_SUPPORTED", // Electronic claim attachments not supported
        ...
      },
      ...
    },
    ...
  ]
}

If you try to submit a claim with electronic attachments to a payer who doesn't support them, Stedi now blocks the request before it reaches the payer. This affects 837P professional, 837D dental, and 837I institutional claims.

Electronic claim attachments let you send supporting documents – like X-rays and medical records – alongside claims in Stedi. Stedi lets you submit claims and claim attachments electronically using JSON API, X12 API, or SFTP.

However, not every payer supports electronic claim attachments. Previously, if you submitted an attachment to a payer who didn’t support them, the payer would reject the attachment as an error downstream. This could delay payment for the provider.

Now, Stedi checks payer support upfront and catches the issue before the claim reaches the payer. That means faster turnaround times for errors – and faster payments for providers.

Errors

If you submit a claim with attachments to an unsupported payer using Stedi's JSON or X12 Claim Submission APIs, you'll receive an error response with a 400 Bad Request HTTP status code and an error message:

{
  "code": "TRANSACTION_TYPE_NOT_SUPPORTED",
  "message": "Payer 62308 (Stedi Payer ID HGJLR) is not configured for Unsolicited Claim Attachment (275). Please check our published payer list or contact Stedi support to resolve."
}

If you submit a claim with attachments to an unsupported payer using SFTP, Stedi will reject the claim with a 277CA claim acknowledgment:

STC*A7:N21*[DATE]*PR*[AMOUNT]********Payer 62308 (Stedi Payer ID HGJLR) is not configured for Unsolicited Claim Attachment (275). Please check our published payer list or contact Stedi support to resolve

Check payer support

To avoid errors, check whether a payer supports electronic claim attachments using the Stedi Payer Network site or Stedi’s Payers API.

For example, in a Search Payers API response:

{
  "items": [
    {
      "stediId": "HGJLR",
      "displayName": "Cigna",
      "primaryPayerId": "62308",
      "transactionSupport": {
        "unsolicitedClaimAttachment": "NOT_SUPPORTED", // Electronic claim attachments not supported
        ...
      },
      ...
    },
    ...
  ]
}

Get started with Stedi

Get started with Stedi

Automate healthcare transactions with developer-friendly APIs that support thousands of payers. Contact us to learn more and speak to the team.

Get updates on what’s new at Stedi

Get updates on what’s new at Stedi

Get updates on what’s new at Stedi

Get updates on what’s new at Stedi

Backed by

Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on our site are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.

Get updates on what’s new at Stedi

Backed by

Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on our site are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.

Get updates on what’s new at Stedi

Backed by

Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on our site are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.