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
- f5b601241afb59ed8fbdd47a744fa03881cba00e62906ea9905af406f78c3154
- request
- 201300f884f4bd63bbdd80eb34a21af77abf36f0ec0d59f0b86d51f9f5f6722b
- transaction
- 4604a4fcfa2cb2dec843c1073c6a12dd2755d280e6f749b577f3d86d64589d31computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 15172
the chainentry 15172
- sealed to the entry before
- cdf7491c2980f21f5eb3599dfcee10f2057c9065c5d0e6019bf3529017f6e5a4
- this leaf
- c2eb854fea592277bdfd0e6ab2082f7e3575a905bb7e19304729e7fae71bb192
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- zfHJa/eixfWt2bd5qeyPCBO/oA2mj36pQKIdLV+Ylqt6hDWknykIZ1BGCCMWp8HkB/p7/b7JuJDAw27JZ6KGDA==