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
- 9369fe20aa1a410713c12334e4d1954c9a543907038e8a33e6ad63b577c05c59
- request
- 9e50fcbc276339ac850449a470966fc440d584828afba2423fdf4f06034eb7c7
- transaction
- ace0e096f2219b813e3987a5b5fb52f139588b5277f7680d538a6c42128b2f3fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32811
the chainentry 32811
- sealed to the entry before
- 0289c41072b86d4ede1efca4cd7c79f53b5af4e3079fb420b7fb29698a529438
- this leaf
- aa3edd0019c72678ea7f969145c7b29445f3428de79d047991b4fa61b9b67719
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- pCYdrh4ZlhSjwUn135mVFjrteEA9OHaRwdrynGSNGV20BvKqg0Z7rM1e5lWFiLs0rEv/uuqiPiPif+h7x8CMDw==