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
- 6cd497c345242bb83daad2162cf50a0e2158ff5ddab9e5355f9c7274771750ff
- request
- f25a20d7dcd568254e30036f565d6fd678bc81ed0c9fdf7080d0b439ac7e4481
- transaction
- 625bc951074b62298fa2a67616325dd43eadb9597b5cdc867f9c62130c2705a2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28456
the chainentry 28456
- sealed to the entry before
- f5744380e9720554873d8e00cf3d845ba4a5b2a6679d41470eab41a12675033e
- this leaf
- 2968d8ae556c7face79160a70f70c67f601e47f9ef712b4d4c8c4864d86681f3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- IvX2HC2xDAntPnyf9B3vbJleyXsTCYJjssA42uRbe/pQC9/Fg2HTZ7ONuI40W24Y2xHqVNezjDUtQ2BlJc/nDw==