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
- b03031efc84442cf7ab8c733681e0123fcbe31591956e1f5ed9b11a17722619b
- request
- cd3c59633b8a18448fcc4cac471aff3b78c02e1159aaa99584ec3c8e55e67da6
- transaction
- 026c0c1fc3f08b7cd2c117348fb6393e3b87b57f11b39667069697e1431c6743computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 8530
the chainentry 8530
- sealed to the entry before
- 8f6035b0dd8c479b94c2a2a9921a065e6faedb7217c7758207bf032edd68aa9e
- this leaf
- aa775d5f0a0ba3aef7d3eed1fd6788a313178badf1f55a043a9ed5ae52230e93
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6AjL5w71iYjYkCZxGmHefvlANaPnyHL0MjICLza9IPG8Lh5z8Xm9qaTgRRf6J3HZ+x5kL3LszKHM/hZMVK+bDA==