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
- a720b66a17f16fc3d4da034a25cbba00f49b11383adf9b5cea9d9462945b4829
- request
- 1c5f3a16741d55bcd0bfe9a79a1ce00fdc869fdbd9e49d56960ba0df6a6fc53b
- transaction
- 5d54138e8b57ca85f6d24cbe53f2db93df6cff603f147d6e4be72a65dd38a3eecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27605
the chainentry 27605
- sealed to the entry before
- 509e4f78fe80334f4d2bf3b400b7ba813575b71cdc8aa3681f2589a840fe9865
- this leaf
- 61a535eaac7e39b028aeb53b8523ca7f01b7dc597566b657e88d6d79e0719e80
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- pWJH64FiGWU3bav2Oeipbn7KqdgVylpv8t4tobwSMyPGIa9lVtqB4pgRn+MfeWm4GbpEKu3ev945wfoXwrLyBw==