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
- 21e6200cb9a97f0556452cab1a6e812ac1ae8ac690a0c472b75a4a3bc48c01ae
- request
- 4d910357f8a219a9f285db4896b09c5628ba18a92cc0a0b40b5c919db7faebee
- transaction
- e11149db3cd62c27dc051c96f704ad67e21e3265cb1e11a3887eb56cfc888a64computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32994
the chainentry 32994
- sealed to the entry before
- 90959318f781ca9b3347fb42de3bbdf76fcd8ca40de4afd4656737f93be34cc9
- this leaf
- fb62bc49ea08cb99f8a6cf86fd1316aa1d2d1786eec40f2ca2393cc56f741b2c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- D2EGismo0DSCsmLk+hG/jO6vrScRP1kyTV6tNhu0iu75y+EEUfkEIbnkqg47wKMcr3HhIKz9pLvlop0sI6HeAQ==