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
- e6537e86c892d03e5f7803121fd72a259ca7cf07e01620fa91db42da0a024483
- request
- d81ecaaec1178ed1627f49cde4aa569bca3ec6fadb8e0f673ae2b87686a82861
- transaction
- ed44fdfa8c32469d7ac89cb79564d6cdf00cc26de517756b4c1872a9de9f3a3fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 23739
the chainentry 23739
- sealed to the entry before
- 4be6379d0a0c5237e49bb122ddf2c4fe14319769cdd272e7e8453d8328448af4
- this leaf
- 68525d1096dae7b309750ec797fde22f97949cadf21a3e726d4ee48be885fc7b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- tYEMrDwOiGA/xVrZwuRX4surz9Eqnnt28NpekH7XEVdKsmSB2OpTud6VLBWTwA9s25n+zxmSSuvSBprUGOS3Bw==