Skip to content

Document 3RI sandbox tests (last-4 PAN pattern)#42

Merged
thejspr merged 1 commit into
masterfrom
3ri-sandbox-testcards
Jun 29, 2026
Merged

Document 3RI sandbox tests (last-4 PAN pattern)#42
thejspr merged 1 commit into
masterfrom
3ri-sandbox-testcards

Conversation

@thejspr

@thejspr thejspr commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

What

The sandbox docs had no 3RI section, and the last-4 message-version rule read as browser-only. This documents that 3RI (deviceChannel 03) uses the same last-4 PAN encoding as the browser channel, so integrators drive 2.1.0 / 2.2.0 / 2.3.1 by varying the last four digits of any scheme test PAN.

Changes

  • New "3RI Tests" section describing the shared last-4 encoding: first digit → message version, third+fourth → ARes outcome. 3RI is frictionless only (Y/N/A/R/U + DS timeout); challenge/decoupled/information-only combinations are rejected for deviceChannel 03.
  • Browser "Message version" note updated to say the last-4 encoding is shared with 3RI (not browser-only).
  • Cross-link the Basic 3RI Example to the 3RI test-card section.
  • Fix the browser version table 2.32.3.1.

@thejspr thejspr marked this pull request as ready for review June 24, 2026 06:30
peterklogborg
peterklogborg previously approved these changes Jun 24, 2026
@Lassejoe

Lassejoe commented Jun 24, 2026

Copy link
Copy Markdown

Just wondering, since it was me who made the implementation for the deviceChannel: 02 in sandbox.

Why not follow the same pattern for 3RI?
You can determine it is 3RI by deviceChannel.
By doing so the integrators can still mimic MasterCard, AMEX PANs and so forth in their sandbox environment.

This seems like going back to the old setup more or less.

The sandbox docs had no 3RI section, and the last-4 message-version rule read
as browser-only. Document that 3RI (deviceChannel 03) uses the same last-4 PAN
encoding as the browser channel, so integrators can drive 2.1.0 / 2.2.0 /
2.3.1 on any scheme PAN by varying the last four digits.

- Add a "3RI Tests" section describing the shared last-4 encoding: first digit
  selects the message version, third+fourth select the ARes outcome.
- 3RI is frictionless only: document the available outcomes (Y/N/A/R/U + DS
  timeout) and that challenge/decoupled/information-only combinations are
  rejected for deviceChannel 03.
- Clarify in the browser "Message version" section that the last-4 encoding is
  shared with 3RI (not browser-only).
- Cross-link the Basic 3RI Example to the new 3RI test-card section.
- Fix the browser version table: 2.3 -> 2.3.1 (the sandbox serves 2.3.1).

Refs clearhaus/issues-pci#7131

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@thejspr thejspr force-pushed the 3ri-sandbox-testcards branch from 49d2fc1 to b6c7e5b Compare June 24, 2026 07:49
@thejspr thejspr changed the title Document 3RI sandbox test cards (2.1.0 / 2.2.0 / 2.3.1) Document 3RI sandbox tests (last-4 PAN pattern) Jun 24, 2026
@thejspr thejspr marked this pull request as draft June 24, 2026 07:59
@thejspr

thejspr commented Jun 24, 2026

Copy link
Copy Markdown
Contributor Author

Good point @Lassejoe 👋🏻 Might as well follow the new approach

@thejspr thejspr marked this pull request as ready for review June 24, 2026 08:33
@thejspr thejspr merged commit 34c09f9 into master Jun 29, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants