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
- e016418e6781c8943e030c449d25ded6f050eb4d15b7942fba82f69eeee15176
- request
- 4dec0e26114a884225a9ba66378145c9d149533a97311454f11da14cefdc987a
- transaction
- d34a72dfbce24a286eb98340e6b09e7011bacddc08b4309556b463541b61bd7dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72661
the chainentry 72661
- sealed to the entry before
- fd183bc5da463515fd1428532e12e630e0f23be1a52d84e7bc7edfb1037b61a3
- this leaf
- 890b67fa11b49976c8f62653d5b949c6b5331a9d7018c36b4fa002fd0f6b671b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1gAubaBHnJ4QQNDMEfOtayILBAwb8Gpooyet7mIdKXrCJ8aXS/5IxDoChb/0wJSUgOEL8lPPTKPT09dPrfe6Cg==