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
- ab33a629c77268de8fbfce3cbd3570085d773017d03ba84be045f75390c7b79a
- request
- e50e51f0a647403f6bc19dc40c2a7146697e159d4b444d8cd0eba737015c415d
- transaction
- f757d2f70ebea85fb340f27ee5135344ab1abf051b3243ef568d9b9b81cbb226computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51581
the chainentry 51581
- sealed to the entry before
- a8b2376c9ce31e5427520b4d3fc423b4abc7314fb27a4fb6ea79512e8a073b56
- this leaf
- 67a66df1d9162a3121d9dd32525dca651f7f02ca9ccad6bf731fc6b16d34d7c6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- uWANls4GYlenbs9srNGeeiJpSp9oDbjIj/MwpPce9LYM3a/LXTPIIrhDlpjUxe2sbHCFpOsNjtwmW2R0ULpcBQ==