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
- 368aeb24a16be942eac1eb3163e7631bec969f2889c7292da4cb2884a7fdeff2
- request
- 20e0e5035a1096fd0a51a04d17f4eb7a80ac20b739fb9fbc0d10ede7793f4520
- transaction
- 22322adfcd4ef6c286cdf78f1fe13159049aeda89e1f3eea71ab5788d6ee53d7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 46577
the chainentry 46577
- sealed to the entry before
- fdf34d74b0f4efea8ff3afe16b58054ba17ba25d6165d1b28df1e986e73c7f04
- this leaf
- 5ee020379003657c0637b5a4ca3913f10b5d6863b71dda17737add6a07f14b92
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4DjF+hI9tQas9rcTWRBYaQ3KldmqxLmdmO6foDT0KegniZaM5lDofHLgzkG8FAgUZ7zCOc02I5wM1+g+OeOWAw==