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
- 8991ebc26e91eaef6e4a735a1a246ed1b691b0ee7858755752373e2934064cef
- request
- 546d3c410902937ceb831bcb875f2689d1afd91056ff649eb5b74e154c7d1f43
- transaction
- 897a950f0fec4392ae12de93799a887f673a0b1bc9500f05b2bd25619665af43computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 23872
the chainentry 23872
- sealed to the entry before
- de331eef0b105020cf84406f0668a1102f9b62aecb5136e8880e5359e39e769a
- this leaf
- 5aefb445db6c0ca190086cdbc53da777f31d3b30ced8ddfc41f662822d2830fb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- NUTeUe6tDcYY7iHiFPttPnD2s9O7YbWaG9TaRAopO4f7vul40Si/i2JtiSR+nf8X3vk2A65IqvnE6UjyXkhmAw==