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
- c4cc24d4d43d5edd0120a6642c07d4e8d6a0f2154c3a84ec07b779d1d648fb4d
- request
- a6097425e79065842eb4aa599ba737f7378bc8d71e0206ed16624da6757e4f40
- transaction
- ad0fbea7f1a238d6d6cddf9345e2b1f186c342135cd2372aef34a600ba44c74bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56061
the chainentry 56061
- sealed to the entry before
- c8e1b74f9080211bf1f0877f7d2d8fd269fa1d7489226579dcab65d5a1c5cd1c
- this leaf
- 5d9aca6e4fd3f4f292bcbd561362b519f6a0127a345867ba193bef60764e731a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- f+tazdfZBE2bLIQJa4kPCZvWvY7lbI9ON7Yodhv2OG3MmOuZYd450123g/Qq+42JWYA23fjHUChrIkH1kc4HCA==