Appearance
SMC-B verification
Use an endpoint job to verify an SMC-B through a Secunet Konnektor and a Cherry ST-1506 card terminal. The job opens the terminal's PIN channel, starts verification on the Konnektor, submits the PIN, and waits for confirmation.
Prepare the devices and values
Complete Telematik setup first. Both endpoints must belong to the same tenant, use the same connected Telematik service client, and have active credential profiles. The SMC-B must be inserted in the selected terminal and available to the intended Mandant on the Konnektor.
Run Collect Konnektor inventory to identify the card's ICCSN, terminal, and slot. Obtain the Mandant ID from the Konnektor's configuration. It is the Konnektor's Mandant identifier, not the Ordyn tenant name.
Store the PIN in a secret string variable, for example telematik.smcb_pin. A string preserves leading zeroes. The PIN field accepts normal templates, including secret variables: {{ vars.telematik.smcb_pin }}. Mandant ID and ICCSN also accept templates. Use job variables for values specific to this job or supplied when it starts.
Build the job
Create an endpoint job, set the endpoint-kind requirement to Telematik Konnektors, and run it on the Konnektor. Enable Allow individual steps to run on another endpoint so the terminal steps can use the selected card terminal.
Start with Read SMC-B PIN status on the Konnektor, providing the Mandant ID and ICCSN. Branch on its Card PIN status result:
verified: finish without submitting a PIN.verifiable: continue only when Remaining attempts is at least2.blockedorunknown: stop and investigate before sending a PIN.
Automated PIN entry requires at least two confirmed remaining attempts. With one attempt left, Ordyn refuses to send the PIN so automation cannot consume the final attempt. Check the PIN and handle verification manually at the terminal. An unknown attempt count also prevents automated PIN entry; read-only status checks remain available.
Add these steps in the verifiable branch, using the Telematik category. Keep Stop and fail error behavior so later PIN steps cannot run after a failed prerequisite.
| Order | Task | Execution endpoint | Configuration |
|---|---|---|---|
| 1 | Set card slot PIN mode | Card terminal | Select the SMC-B's slot and Remote web PIN entry. |
| 2 | Open SMC-B PIN session | Card terminal | Enter the same Mandant ID and ICCSN as the status step. |
| 3 | Start SMC-B verification | Konnektor | Use the open step's PIN session reference. |
| 4 | Submit SMC-B PIN | Same card terminal | Use the same session reference and the PIN template. |
| 5 | Wait for SMC-B verification | Konnektor | Use the session reference and the start step's Verification reference. |
Pass references using the IDs shown on your job steps. For example, if Open SMC-B PIN session has ID 3 and Start SMC-B verification has ID 4, enter:
| Field | Template |
|---|---|
| PIN session reference | {{ steps[3].result.session_ref }} |
| Verification reference | {{ steps[4].result.operation_ref }} |
The start step leaves verification running while the submit step sends the PIN to the matching terminal prompt. Submit SMC-B PIN succeeding means the terminal accepted the submission. Wait for SMC-B verification confirms that the card is verified. Keep these steps together within the PIN session's five-minute deadline.
Choose the terminal mode after the job
PIN mode is an explicit job setting. Opening or closing a PIN session does not change the slot mode or restore its previous value.
If the terminal should return to Local PIN entry or PP-1516, add Set card slot PIN mode to the job's Cleanup, selecting the same terminal, slot, and intended final mode. Condition it on the initial mode-setting step succeeding. Cleanup also runs after failure, cancellation, or timeout. The final mode is the one you configure in the job; the previous setting is not captured automatically.
Investigate a failed or interrupted verification
Ordyn permits one PIN submission per verification session. If the PIN is rejected or its outcome cannot be confirmed, further PIN automation for that card is put on hold to prevent another automatic attempt. Cancelling a job cannot undo a PIN already sent to the card.
Read the PIN status and remaining attempts again before retrying. A card can be verified even when confirmation was interrupted. Keep the verification branch conditional on verifiable with at least two remaining attempts, and correct an incorrect PIN before starting another attempt.
The Konnektor overview's SMC-B cards table shows PIN automation on hold. This is an Ordyn automation hold; it does not mean the card itself is PIN-blocked. After reviewing the card and the failed run, a Service Operator can use Clear hold in that row. Clearing is allowed only after the PIN session has ended and its five-minute deadline has passed. It does not verify or unblock the card, reset its remaining attempts, or resend the PIN. The minimum of two remaining attempts still applies after clearing a hold.