why1 reason
data_leakpayment_card
payment_note carries a payment card number (41************11), which would be written to a permanent public record
what it was decided fromfingerprints
- rule compiled from it
- 1e9557414b36fdfc43bf9d1e9d7f03e3a3470e6ea5940495fc1358dd0df33e03
- request
- 37eb3ce46f8e8a998fbe06014e5a345240abb0aab0e66cae07f90131142d9202
- transaction
- 4bd9ac6205216dc33de731f09bfb7c1cf9a3bb842be289907d199eedcf71ee9dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75674
the chainentry 75674
- sealed to the entry before
- 42c954405c700ebf591cf4b5552c8102b20c677c3a74660cb6fd3f85ce7a17ac
- this leaf
- ff2ec0f27e54e23e5a7970847fec5cda4a36da50e5af6ec7174448f56f287add
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2WoIRT8VfHIVzfY0jhIk7E/fbAmgZUP80rv74lADFdQH9LKOuiwJ08P2ENCGdxvanXjz/ejZaMUM4vQM51FHCQ==