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
- 4d7b36c3be0399dc628e2e6414a954b6ddb70ac426bbb416d19fc55259345d19
- request
- 4c17cd1573fc4819167037d81ae7c8345452a20f4988d15c32f5723d8a12a9b0
- transaction
- 481ef45371b4277b54045a0b290603dd654ad60989c5dabbb0afce717d8735a0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 24169
the chainentry 24169
- sealed to the entry before
- 48c65e7c39c94ca19a490513bac678fff535182251f8ab84e35d76a8ff0671ec
- this leaf
- 410461351b5b177402bbe42e4985cf353d456013fc72fff985d49e05031c5efc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- tjSKwO+OUKuq+R5gwk7IIyZGtllH8uwbeGxHLYibxxNpJ+YBpRPwA9PuEPycwPuZd4QNqXEuqKfTNsn582lyDA==