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
- acc222f4e60b2603838ab4e04a58a3416b540261b673d2c57037d7b76f1f5ffa
- request
- e970a08f0d4cf73422baafaa70360104e99d6f1c9bd111f7ef3e94a49224287b
- transaction
- f17563cfe0a6fa5ca1495909ea9adf3932c3fdc2dd44847bb0cadf49c407d751computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 26408
the chainentry 26408
- sealed to the entry before
- 81415d709a61ab57cc35f4b44c4c8c0b483e7d87e8004a346c3423c4b89b09b3
- this leaf
- aa01b652e99e6d80e9b24a3eb3e5d72908e2758986e7ac95d76b4ed31f2833f3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- F6Rx3i93MzOMoHtBy6n3VLUqiCKIIJm4TyGc4A+1pw5TYcpB+zVut1ydMKOX73GIPR3Cq+y3kHZYRCxxXfOwDw==