Styxis
Company
Knowledge

Do not erase historical X2P1 transactions when payment service values change

Preparing a transition means preserving historical meaning as well as considering a new category.

Immediate preparation does not require replacement

A notice about changing payment-service values can tempt an operator to replace old names first. That could erase which service processed a historical transaction. A useful immediate action is to preserve the current contract and separate periods and versions in a transition-test copy. Truthound can check the proposed copy’s conditions. It does not process payments, adopt a standard or decide the correct regulatory implementation date.

The problem definition has a limited status

Australia’s DSB published its NPP service-values alignment problem definition on 19 October 2026. It discusses the X2P1 transition and representation of services including SCT. The document says it is informational, not draft standards or formal consultation; target timing remains conditional. Proposed values should therefore not be treated as already-adopted production requirements, however clear the intended direction appears in the discussion.

Put historical values beside the proposal

A proposed test table retains transaction period, schema version, original service value, mapping-rule version and review state. Do not collapse current and proposed categories into one permitted list. Preserve the original and explain its representation under a future rule separately. The owner establishes which rule applies to which period from the official decision and actual implementation conditions, rather than assuming that publication changes every record’s meaning.

Try a bounded version check

Truthound Core Python SDK 3.3.4 (open-source SDK, Polars backend) documents ColumnPairInSetValidator for approved rule-version and service-value pairs. ConditionalExpressionValidator can express caller-defined period or version conditions. The operator supplies valid_pairs, expressions and null handling. This is not CDR conformance certification, a payment-processing function or evidence that the proposed standard was adopted. It checks the contract staff chose for a specifically labelled test scope.

Keep the historical-rewrite counterexample

If historical X2P1 transactions and future transition candidates share a file, replacing all values with SCT would make the original processing meaning harder to recover. Banning every new value would also prevent a useful transition experiment. Separate the scope of current operation from that of proposed test rules. A global replacement is not evidence that transition preparation or compatibility testing has been completed.

An existing version contract can support the test

Pandera 0.35.0 (MIT open-source Python DataFrame validation library; pandas, Polars and other supported backends) custom checks can maintain the same version and period conditions. Retain a contract that already keeps history and proposals separate. Compare Truthound through preservation of original values and understandable exceptions. Selecting a library does not establish compliance with a payment standard or turn a tentative implementation schedule into a confirmed one; those grounds come from the responsible standards and operating owners.

Set the stop condition before production changes

First confirm that historical values remain recoverable and that proposal scope is explicit. Keep the production contract unchanged while an official decision or applicability date is absent. Hold records needing more evidence and return them to the standards owner. Separating preparation possible today from a later authorized operating change prevents a new rule from silently removing the explainability of the transactions already on record.

Conditions

Separate current and proposed rules and define historical-transaction meaning in a test copy.

Alternatives

Pandera 0.35.0 custom checks can retain equivalent version and period conditions.

Limitations

  • A problem definition is not an adopted standard; new values must not overwrite historical transactions wholesale.

Evidence

Event checked
Subject checked
Modified