End-to-end test mode

Run mock eligibility checks and submit test claims without sending transactions to a payer. Simulate the revenue cycle with no PHI.

Test mode gives you a free, safe way to build your Stedi integration. It’s great for coding agents, integration tests, and new applications.

Test credentials

Eligibility check

Mock request

Test claim

Stedi Test Payer

Event destination

Webhook endpoint

No PHINo payer traffic

Mock eligibility checks

Run predefined mock eligibility checks in test mode. Get back realistic responses that mirror those from well-known payers.

Test claims

Send test professional, dental, and institutional claims. We validate each test claim against our database of edits and repairs.

Realistic test responses

Get a realistic 277CA claim acknowledgment for every test claim. The Stedi Test Payer also returns test ERAs.

Test credentials

Test credentials keep test traffic separate from production. No transaction reaches the actual payer.

How it works

One test environment for eligibility checks and claims

If you’re migrating to Stedi, test mode makes it easier to validate your workflows before going live. If you’re already a Stedi customer, you can use test workflows to build integration tests or work with coding agents.

Run mock eligibility checks

Send mock eligibility checks with a test API key or through the Stedi portal. Choose from predefined requests for well-known payers, including Aetna, Cigna, UnitedHealthcare, and CMS.

Each request returns a realistic mock benefits response for that payer, with examples of copays, deductibles, and active coverage.

mockEligibilityResponse.json

{
  "planStatus": [
    {
      "statusCode": "1",
      "status": "Active Coverage",
      "planDetails": "Aetna Choice POS II"
    }
  ],
  "benefitsInformation": [
    {
      "name": "Co-Payment",
      "serviceTypes": ["Chiropractic"],
      "coverageLevel": "Family",
      "benefitAmount": "15",
      "inPlanNetworkIndicator": "Yes"
    }
  ]
}

Submit test claims

You can submit test claims three ways:

1Use a test API key with the JSON or Raw X12 claim submission APIs.
2Use test SFTP credentials to submit X12 files.
3Turn on Test mode in the Stedi portal to upload EDI files or fill out the CMS-1500 claim form.

Test claims work for all three claim types: professional, dental, and institutional. Unsolicited claim attachments are also supported.

submitTestClaim.js

fetch(
  "https://healthcare.us.stedi.com/2024-04-01/change/medicalnetwork/professionalclaims/v3/submission",
  {
    method: "POST",
    headers: {
      Authorization: testApiKey,
      "Content-Type": "application/json",
      "Idempotency-Key": crypto.randomUUID(),
    },
    body: JSON.stringify({
      tradingPartnerServiceId: "STEDI",
      submitter: {
        organizationName: "Doctors LLC",
        contactInformation: {
          name: "Doctors LLC",
          phoneNumber: "5552221212",
        },
      },
      receiver: { organizationName: "Stedi Test Payer" },
      billing: { organizationName: "Doctors LLC", npi: "1999999984" },
      subscriber: {
        memberId: "U1234567890",
        firstName: "Jane",
        lastName: "Doe",
        dateOfBirth: "19891002",
      },
      claimInformation: {
        patientControlNumber: "11122333",
        serviceLines: [{}],
      },
    }),
  }
).then((response) => response.json())

Catch claim errors before payers do

Stedi checks each test claim against claim edits that mirror those payers use. You get back validation errors in real time.

Submit a test claim for a payer, and Stedi runs the same edits we’d run for a production claim.

Stedi’s claim edits reduce payer rejections by catching errors before they reach the payer. Fewer payer rejections mean faster payments. Claims submitted through Stedi have a 98% payer acceptance rate.

claimEditError.json

{
  "errors": [
    {
      "code": "33",
      "description": "The billing provider tax id (TIN), 1234567890, is invalid. The TIN must be a string of exactly 9 numbers with no separators. Correct and resubmit.",
      "followupAction": "Please Correct and Resubmit"
    }
  ]
}

Realistic 277CA claim acknowledgments and ERAs

When you submit a test claim, Stedi sends back a realistic 277CA claim acknowledgment – just like you’d get for a production claim.

If you submit a test claim to the Stedi Test Payer, you also get back a test ERA.

Test ERAs mirror what you’d receive from payers in production. Each contains the same information as if the test claim were paid in full.

testEra.json

{
  "claimPaymentInfo": {
    "claimPaymentAmount": "109.20",
    "patientControlNumber": "ABCDEF12345267890",
    "totalClaimChargeAmount": "109.20"
  },
  "financialInformation": {
    "creditOrDebitFlagCode": "C",
    "paymentMethodCode": "ACH"
  },
  "payer": {
    "name": "STEDITEST"
  }
}

Get started with test mode

Mock eligibility checks are free and available on all Stedi accounts, including free sandbox accounts.

Test mode for claims is available for free on all Stedi production accounts.

End-to-end test mode

Benefits of test mode

Mock eligibility checks

Test claims

Realistic test responses

Test credentials

One test environment for eligibility checks and claims

Run mock eligibility checks

Submit test claims

Catch claim errors before payers do

Realistic 277CA claim acknowledgments and ERAs

Get started with test mode