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
- ee6542bd63ccdcf31eedb321ffbbf26210eb1813840046c8aa8ac9bfd31f3f7d
- request
- 386675eec1af8076bb4a857233970a1c478d07fb163e24a22dc0438dbbe912fd
- transaction
- 008f5acfb76deeb4444ebe78a2f357e3c4eee1500fb87ed3919d6eb9da7c5512computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 24626
the chainentry 24626
- sealed to the entry before
- 2160f2bda2fce4c1d4bc1a5ee6fa4be97ea2efbe80ec65f7c9dfe5623cd59729
- this leaf
- 46255c1720f7bd40770684f67a3353760860f1913146335533a6d32f93b1ab71
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6lxyNI0LjLLGt/2Qb9Kr1Bf2ana2oeG3p2g23v3DGQ8eSEeJWaL4dd1UWje8D+KIuJxUbl1OUm5u4Dm8smnMDw==