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
- 112cd9190cd3826e5cf0c667f81447708b0f09b9e916f83e23d661ba881d647c
- request
- 8ba02f93d3144e40ad58de7f88f17f2f16b868ee1066f22c62165e1e10d9e292
- transaction
- 52af5480f70b22e544eca949ebdef348f253be340b7508e594d2861039a5b5bccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 53153
the chainentry 53153
- sealed to the entry before
- dbf94a4b64f5dd9f26d29746647f7cfc1eb487c8812732e147a3a1b156de940b
- this leaf
- ca624769446321081ece6c861b5b122e5fe7ce18bd4fd4a3aa2725a28d040a5e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- NgzZZJMjl3hisHmLLjOfqN2jhgH2zfs+j+DskIhlUeZ8u26WGrrBxkRNkxYL75HCvI+OQvmd9gaWER50MbkXCA==