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
- f81cfcf8620d2f66b629c869913049c97b7046b05d5e3888aa2c97202d0c464d
- request
- 8c6b49f70030ee2cd231c88ba6f2db62913bceba6b058d4116d9456673d68e7b
- transaction
- 90ea6c4c0dd1257307a95c0231589588261124bf987279e5508b46db553052d5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68364
the chainentry 68364
- sealed to the entry before
- a912a2178fad619689602176655cac9216c055a126757fd49660027287e5bf89
- this leaf
- 7697874f00c4c6e61742b802e71a33557fef2f6b6838c8b11ce7d559a9a7d552
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- IsQ71K4IOFp1WbeL0nWB+KK2Rsdmtzn5a0ZxtMTKz/nIhKP6NJkqKGiwpBVODcU+8MahQK6gwdZU1uwO0Vc6Bw==