Acceptance time is financial data

What the public implementation shows

SIPS Connect has focused tests for acceptance timestamps across payment requests, payment responses, status responses, and return-status parsing. The tests distinguish offset-based request formatting from UTC Z formatting and explicitly require an absent acceptance time to remain absent.

The builders and parsers carry both message creation time and acceptance time, but the test contract prevents one from being substituted for the other. This is the implementation fact behind the note; the architectural reading begins from that visible boundary rather than from an assumed production story.

Operating principleA timestamp should describe a real event, not fill an XML field because a nearby clock value exists.

The decision behind the mechanism

The implementation treats formatting and event semantics as separate controls: a known acceptance instant is serialized according to the receiving contract, while an unknown instant is not fabricated.

Copying message creation time into acceptance time can make a pending or rejected payment appear financially accepted and can distort latency, dispute, and reconciliation evidence. The mechanism matters because it gives that failure a named boundary, durable evidence, and a controlled response instead of leaving the outcome to timing or operator guesswork.

• Document the event represented by each ISO date-time field.
• Preserve absent acceptance dates instead of defaulting to now.
• Test the exact offset and Z suffix required by each message path.
• Keep creation, receipt, acceptance, and settlement times distinct.

How the control should be operated

Teams should define the source event for every financial timestamp, preserve its offset or UTC meaning, and test missing values as carefully as populated values.

Downstream systems can compare payment timelines without mistaking transport chronology for business completion. The reusable lesson is not to copy a class or endpoint in isolation, but to preserve the relationship between identity, state, authority, evidence, and operational ownership.