Supported Service Type Codes (STCs) by payer
Jan 29, 2026
Guide
To verify insurance or health benefits with an eligibility check, most payers require a Service Type Code (STC).
The STC tells the payer what kind of benefits information you want back – mental health, vision, urgent care, and so on.
But not every payer accepts every STC.
There are over 150 HIPAA-adopted STCs. Most payers support only a small subset of those codes.
How do you know which STCs a payer will accept?
For the best results, you need to test each STC with each payer. This guide gives you a head start. It includes a table of STCs supported by Stedi’s top payers based on payer documentation.
Supported STCs by payer
The table below lists supported STCs for 50 of Stedi’s top payers, sorted by eligibility volume in December 2025. Together, they represent over 65% of Stedi's eligibility check volume. The listed STCs come from payer and third-party documentation as published at the time of writing. Not all payers are included.
For definitions of each code, see the STC code list in the Stedi docs.
Important: Treat this table as a starting point, not a source of truth. Payer documentation may be wrong, incomplete, or outdated. Always validate STC support. Unsupported STCs may still return a baseline response. See How payers handle unsupported STCs.
Use one STC per request
When running eligibility checks, only include one STC per request unless you’ve confirmed the payer supports multiple STCs. For best practices, see our docs.
Payer name | Primary payer ID | Stedi Payer ID | Supported STCs |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
|
How payers handle unsupported STCs
When you send STC 30 (Health Benefit Plan Coverage) in an eligibility request, and the patient is covered, many medical payers return a baseline response for a standard, HIPAA-mandated set of STCs.
If you send an unsupported STC to a payer in an eligibility request, the payer may return:
A response with a benefits information code of
V(Cannot Process) or no benefits informationA AAA error, such as
42(Unable to Respond at Current Time)A rejection of the request using a 999 Implementation Acknowledgement, indicating the request was invalid for processing
Behavior varies by payer. Just because you receive a successful response from a payer doesn’t mean the payer supports the STC. The payer may return a baseline response with benefits information unrelated to the STC you requested.
Process eligibility checks with Stedi
Stedi lets you run HIPAA-compliant real-time and batch eligibility checks using our JSON API endpoints. We also support X12, SOAP, and – for batch checks – CSV.
If you’re new to Stedi, you can try out eligibility checks on our Basic plan for free. You get 100 free checks each month along with access to mock requests and responses.
Signup takes less than two minutes. No credit card is needed.
To verify insurance or health benefits with an eligibility check, most payers require a Service Type Code (STC).
The STC tells the payer what kind of benefits information you want back – mental health, vision, urgent care, and so on.
But not every payer accepts every STC.
There are over 150 HIPAA-adopted STCs. Most payers support only a small subset of those codes.
How do you know which STCs a payer will accept?
For the best results, you need to test each STC with each payer. This guide gives you a head start. It includes a table of STCs supported by Stedi’s top payers based on payer documentation.
Supported STCs by payer
The table below lists supported STCs for 50 of Stedi’s top payers, sorted by eligibility volume in December 2025. Together, they represent over 65% of Stedi's eligibility check volume. The listed STCs come from payer and third-party documentation as published at the time of writing. Not all payers are included.
For definitions of each code, see the STC code list in the Stedi docs.
Important: Treat this table as a starting point, not a source of truth. Payer documentation may be wrong, incomplete, or outdated. Always validate STC support. Unsupported STCs may still return a baseline response. See How payers handle unsupported STCs.
Use one STC per request
When running eligibility checks, only include one STC per request unless you’ve confirmed the payer supports multiple STCs. For best practices, see our docs.
Payer name | Primary payer ID | Stedi Payer ID | Supported STCs |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
|
How payers handle unsupported STCs
When you send STC 30 (Health Benefit Plan Coverage) in an eligibility request, and the patient is covered, many medical payers return a baseline response for a standard, HIPAA-mandated set of STCs.
If you send an unsupported STC to a payer in an eligibility request, the payer may return:
A response with a benefits information code of
V(Cannot Process) or no benefits informationA AAA error, such as
42(Unable to Respond at Current Time)A rejection of the request using a 999 Implementation Acknowledgement, indicating the request was invalid for processing
Behavior varies by payer. Just because you receive a successful response from a payer doesn’t mean the payer supports the STC. The payer may return a baseline response with benefits information unrelated to the STC you requested.
Process eligibility checks with Stedi
Stedi lets you run HIPAA-compliant real-time and batch eligibility checks using our JSON API endpoints. We also support X12, SOAP, and – for batch checks – CSV.
If you’re new to Stedi, you can try out eligibility checks on our Basic plan for free. You get 100 free checks each month along with access to mock requests and responses.
Signup takes less than two minutes. No credit card is needed.
To verify insurance or health benefits with an eligibility check, most payers require a Service Type Code (STC).
The STC tells the payer what kind of benefits information you want back – mental health, vision, urgent care, and so on.
But not every payer accepts every STC.
There are over 150 HIPAA-adopted STCs. Most payers support only a small subset of those codes.
How do you know which STCs a payer will accept?
For the best results, you need to test each STC with each payer. This guide gives you a head start. It includes a table of STCs supported by Stedi’s top payers based on payer documentation.
Supported STCs by payer
The table below lists supported STCs for 50 of Stedi’s top payers, sorted by eligibility volume in December 2025. Together, they represent over 65% of Stedi's eligibility check volume. The listed STCs come from payer and third-party documentation as published at the time of writing. Not all payers are included.
For definitions of each code, see the STC code list in the Stedi docs.
Important: Treat this table as a starting point, not a source of truth. Payer documentation may be wrong, incomplete, or outdated. Always validate STC support. Unsupported STCs may still return a baseline response. See How payers handle unsupported STCs.
Use one STC per request
When running eligibility checks, only include one STC per request unless you’ve confirmed the payer supports multiple STCs. For best practices, see our docs.
Payer name | Primary payer ID | Stedi Payer ID | Supported STCs |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
|
How payers handle unsupported STCs
When you send STC 30 (Health Benefit Plan Coverage) in an eligibility request, and the patient is covered, many medical payers return a baseline response for a standard, HIPAA-mandated set of STCs.
If you send an unsupported STC to a payer in an eligibility request, the payer may return:
A response with a benefits information code of
V(Cannot Process) or no benefits informationA AAA error, such as
42(Unable to Respond at Current Time)A rejection of the request using a 999 Implementation Acknowledgement, indicating the request was invalid for processing
Behavior varies by payer. Just because you receive a successful response from a payer doesn’t mean the payer supports the STC. The payer may return a baseline response with benefits information unrelated to the STC you requested.
Process eligibility checks with Stedi
Stedi lets you run HIPAA-compliant real-time and batch eligibility checks using our JSON API endpoints. We also support X12, SOAP, and – for batch checks – CSV.
If you’re new to Stedi, you can try out eligibility checks on our Basic plan for free. You get 100 free checks each month along with access to mock requests and responses.
Signup takes less than two minutes. No credit card is needed.
Share
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
Developers
Resources
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.
Developers
Resources
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.
Developers
Resources
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.