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
- 3655efb8ff6963079060587bb1430796d67672710ae7dc9500757c63b5271a2f
- request
- 15a391e5e6aae5898ff04ed6855017d4997b451d5e5d6dfee49850d5cc5ce2cf
- transaction
- c374b23eceaf908411f55f614fc6cedb3a90a8f42fd4235f22aaf889512fab1ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69046
the chainentry 69046
- sealed to the entry before
- 91de8d52c16b7205931a08d6b74894034ae14b9afc08c3ecde535743bf437ec8
- this leaf
- 584f6cd3bce139bd8dc07453c1c21840e780d7fa31f0bed9852901074b690c44
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- yWgytMZLZnmzDkhO4lkXVN2D0zGfoFQlYD/jIBD3KRaRvTrNvLB+NpZkReDYvMsVg9SkNag6IF8ap65GG7oFDA==