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
- 2fd20548a9781ce120aa8e5d9db02d657b92538ddb6bc2a9e3619b2b1b610eea
- request
- 75f016136795324335341bbf61d1bf929c2c31b00aa0c7957c5d565e4a500dd7
- transaction
- 526d7135ee56611e3e8bd7d019878f071c1a2a77b720e9415bf339fb5618a8bacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73867
the chainentry 73867
- sealed to the entry before
- 73fe472c3b3c4cf546bc4bf95da2cc87a36dd6e0eefa6a0d5c90a2e88f0b289d
- this leaf
- 4855856022bd426889b4594ec2816c13f1fcd2bdd4001af83f2d8504ac4a0265
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4rwwMtRKDjTS8WZSRzoHGiK+cakHHI41fiqsb7ojkmSJfAz1rLNy5hf8ZE46e5DkdDEd3rWXBFzQzHs1Q6xQDQ==