RX BIN, PCN, and group: how a claim finds its plan.

Read the pharmacy route as one record: RX BIN sends the claim to a processor. PCN selects a line of business. RxGroup identifies a benefit or client when the payer uses it. Cardholder ID identifies the member. A familiar BIN is only the first part of the address.

RX BIN, PCN, group, and member fields

NCPDP's health-care ID card guidance uses RxIIN for the processor identifier and includes RxPCN and RxGRP when the benefit administrator requires them. Cards often print RxBIN instead. The pharmacy fields may sit beside unrelated medical-plan routing numbers, so use the labels prefixed with “Rx.”

One BIN can reach different benefits

RX BIN 003858 is a useful example. Public payer materials pair it with more than one PCN and group:

The BIN is valid in both rows, but the rows are not interchangeable. The TRICARE pharmacy FAQ publishes A4 and DODA together. The complete card or eligibility result determines which record belongs to the patient.

How to read routing rejects

The field-specific M/I codes help locate a formatting problem. Match failures and coverage codes answer a different question: the claim reached a processor, but the submitted route or member did not match its records. The definitions below follow the published NCPDP reject text in Medi-Cal Rx's April 2026 appendix.

A valid BIN can send a claim to the wrong processor or line of business and still produce a real adjudication reject. For codes outside this routing set, use the pharmacy claim reject-code reference.

Recover the current route without guessing

1. Read one source at a time. Take BIN, PCN, group, and member ID from the same card, eligibility response, coupon, or payer instruction.
2. Confirm the program and date. A January plan change, Medicaid carve-out, workers' compensation claim update, or regenerated coupon can replace a stored route.
3. Use Medicare E1 when appropriate. The current CMS Plan Communication User Guide describes the E1 transaction used by pharmacies to retrieve Medicare Part D billing information when the card is unavailable.
4. Use the card's pharmacy help desk. NCPDP's card guidance places pharmacy help-desk contact information on the back of the card.
5. Read the response before replacing coverage. A product, refill, or authorization reject may mean the route worked.

Why some PCNs are blank

A blank PCN is valid only when the payer's current instruction says the field is not used. Washington Labor & Industries, for example, publishes a state-fund payer sheet that leaves field 104-A4 blank. Many commercial and Medicaid sheets require an exact fixed value. A blank-looking card is a reason to check the payer source, not a reason to invent a PCN.

The six-digit BIN and the eight-digit transition

D.0 pharmacy claims currently submit six digits in field 101-A1. ISO/IEC 7812 expanded issuer identifiers to eight digits, and NCPDP's transition notice explains why using only the first six digits can become ambiguous. The NCPDP F6 standard expands the claim field to eight digits, with a compliance date of April 14, 2028. Until a workflow supports F6, retain the six digits supplied for the D.0 route, including leading zeros.

Why public BIN lists age

NCPDP assigns processor identifiers but does not maintain a public history of how every identifier is later used. Payers distribute current combinations through cards, payer sheets, portals, and trading-partner instructions. The RX BIN directory therefore keeps a published payer source beside each row and separates the source from the program guide.