What Is an Rx PCN Number? BIN, PCN, and Group ID Explained

PCN: Processor Control Number

The PCN (Processor Control Number) is a secondary routing code that the claims processor uses to identify a specific plan, program, or processing path within their system. Think of it as a sub-address.

A single BIN might handle dozens of different plans. The PCN tells the processor which set of rules to use for this particular patient. Without it (when required), your claim gets rejected because the processor can't figure out which plan you're billing against.

BIN: Bank Identification Number

The BIN is the primary routing number for pharmacy claims. It's a 6-digit code that identifies the claims processor or PBM that should receive the transaction. The name "Bank Identification Number" is a holdover from the era when pharmacy claims were processed through banking networks.

When a pharmacy submits a claim, the claim switch looks at the BIN first. It's the top-level routing decision: which processor gets this claim? Everything else follows from there.

Group ID: The employer or plan identifier

The Group ID identifies the specific employer, union, or organization whose plan covers this patient. A single PBM might manage pharmacy benefits for thousands of different employers, each with different formularies, copay structures, and coverage rules.

Two patients with the same BIN and PCN but different Group IDs might have completely different copays for the same drug. The Group ID is what connects the patient to their specific employer's benefit plan.

How BIN + PCN + Group ID work together

Think of these three fields as a hierarchical address system:

When you submit a claim or eligibility check, all three fields get sent together. The switch reads the BIN for routing. The processor uses the PCN and Group to find the right plan. The cardholder ID and person code identify the specific patient within that plan.

Where to find BIN, PCN, and Group on an insurance card

On a pharmacy benefit card, these fields are usually labeled clearly. But sometimes they go by different names:

Some cards combine medical and pharmacy benefits. The pharmacy-specific fields are usually on the front or a separate "Rx" section. If a card doesn't show a PCN, that processor may not require one.

What happens when there's no PCN?

Not every insurance card has a PCN, and that's normal. Some PBMs route claims using only BIN + Group. Others use the PCN as an optional override. If you see "no PCN" or an empty field on a card, try submitting with just the BIN and Group.

In code, you can send an empty string or omit the PCN field entirely. Starlight's API handles both cases, routing the claim based on whatever identifiers are available.

Using BIN, PCN, and Group in your code

Here's how these fields look in a real API request. This eligibility check uses all three to route to the right PBM and plan:

curl -X POST https://starlight.claims/api/v1/eligibility \
  -H "X-API-Key: your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "transaction_type": "E1",
    "patient": {
      "first_name": "JOHN",
      "last_name": "SMITH",
      "date_of_birth": "19900301"
    },
    "insurance": {
      "bin_number": "610014",
      "pcn": "MEDDPRIME",
      "group_id": "RXGROUP01",
      "cardholder_id": "SMITH123456",
      "person_code": "001",
      "relationship_code": "01"
    }
  }'

The same identifiers get used for B1 claim submissions and B2 reversals. Once you have the BIN/PCN/Group, you can do anything in the claims workflow.

For a deeper look at programmatic BIN/PCN lookups and validation, see our BIN PCN Lookup API guide.

Common BIN numbers and their processors

Here are some BINs you'll encounter frequently in testing and production:

There are hundreds of active BINs in the US. ANSI maintains the official registry, but in practice you don't need to know them all. Your claim switch (or Starlight) handles the routing lookup automatically based on the BIN your patient provides.