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
- 6a96f2b6b2b773b22db379e7c23d71510a364c9db4c3f05e1da7abbfcf866e1f
- request
- 38f60f46cdb4a0418caf1eb001faaa7b46351a43d4f9c82f4e0465243fb7b5b5
- transaction
- 2f2501a11acb66e3e40a13d1083d4944999ae08c315b81f349a86463a98a3b7ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 25605
the chainentry 25605
- sealed to the entry before
- d18c0c9cf9fd3f865b63f0cecb0c35f01ab4b19eba3e5a0388b55c94b08395d0
- this leaf
- 69a67fd6f6a21b378e16d283f72b6296e487c45ffb1665bc03a2a319d7f2c6da
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- r69WGQvqdt46PZPEvzRjBZIxVx+gvM3o03XMXFRuNXJnmE35oHkaY18GBwRGZIKzK/4Uff394dNljxsGosYuDg==