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
- f19a4a60539dc657b933f6fb8faf654b4077a7891b45008f235d5d5ce51625b2
- request
- 7d343c407d07f2399bbf236c4829f37acd80945d86cc509b0495630258d04a05
- transaction
- 7d033d2fad025256a3b8a025b3a88881ec46fe20496f5621c27acbda3aa3e0decomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65203
the chainentry 65203
- sealed to the entry before
- f10e6538422de47853700e30127b27efe2065e2e7376eb4816159abdbb6bc571
- this leaf
- 26a27a5e09248847cb2b4c0f166ebc7a2c88784b15b9d6dab67ac0c195bac4ea
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- c/u/izhJZ2YP5NeEwcsifaVJ6Rb7hfzP17t1NtEVqJo09V5LY1coVUWXDDY3xybkoUjOnw8ui97DY74d4mOAAQ==