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
- 112c12399a5c1e94db29cdd9114dacf934cb0484fe3a85b00e2aa7b344c879ee
- request
- a3ca9a2e69b28a190bb397dd7a61be398bab5a1e1829ab4f394bf867711bcc1c
- transaction
- 0a9d33cf1856ae007335b4bda2c073b6740f69f115d41261d3e19368a4d36a70computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 54826
the chainentry 54826
- sealed to the entry before
- d25ce23c15da3ca9cece83ac2cd0d5f9a6877371d7a33b26b14ab8cddbbf61bf
- this leaf
- 0230d1d25a368ab7c4c3bab535978db4a22af897eaaf73d7607864c0a435ee18
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +jPx8ju2XSUxd3yaYHIF+cQHqx/EXloPI0Y/qfemTj9SVBW4033bxkxSBf8A5XgXjvzyrE67GUcMV//fNc+FAQ==