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
- b72b31aaa5815e139f28d73aaa56b21652b1242b47989d495fdd66ba3a8d69f4
- request
- e63675d9df5cbb45d991c193f72a9e0c8dfd8fc4619c1e5323a7a689eb03fab1
- transaction
- 7d1dec8ed732919fa2e88f499cfb841ccfc6eb305902fdc010ac7607e9cac1f0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60776
the chainentry 60776
- sealed to the entry before
- dd4270bef9971bb715dda4334d0fa7b0d2724558529c5a61db3eef87e9f139fc
- this leaf
- e2f1854c427400c05f0bd8bfb3a58da143ed52ad385cc17b51c119f2f80de953
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- rveknMXjfYwsWEkBVU3iLKJsR9okNvlxUsq9v8snLjUNDCSijsTK5fvdGB1rG7WylWQh9xILdLRU6CcBErI0Bw==