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
- 0f005dba5332f85aa84e71204cc37831e185ac698f11e3b776593a4827b26bc7
- request
- 19a6babdf537cedc477633169ff5d3385639ecbfc4cc9c1e09a8dca99f5a0399
- transaction
- cb7e8595c101a8f71bba49e92b4b2a98a04a1c76fa1ad8820c47f9f73d10f22ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11523
the chainentry 11523
- sealed to the entry before
- ad47e5d7de922aee42cf42bdd146b8042867cd67dacebc58098c6a91092552a5
- this leaf
- 1b5ea57d3df21cd9d07f7e7312eab2a1fd97106174ad35f1f3886f3c5f613c7f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9zNWWoJXrW+EX2L8fHiXvbMXOjI/MmSaPzGv8Brxbaqf8ocI8K3PMqW1P8jOQxcCiNf+r+kzijC7SuHImwqbAA==