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
- 826736f093c32d8fb3dcdf3ede0f4192d8810018b93ffbabcf35f4d8115961f0
- request
- 08f4e597ff14e6bfedb12c7e40231806365722a5d6ef660dcb424f827677cc19
- transaction
- dec4d06cc955e48dc5930b6d98f0bcaaa02c42e9ba5ca13d54042804789385f2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 4852
the chainentry 4852
- sealed to the entry before
- 44a913625b73e65a5d1c6f39b4d5e48ee0d4cacef0a30c8de2585e3792ae53f4
- this leaf
- f9fd21b1f9889cc31fdd7f2532735633fb45e9a518f525e86cffc1ca7409b553
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9KrNAN4x3+Cwvx0l13xDWf0PW1Ji+TPEmoh33V+oksV1HOWcdUkgb6Ae6R0rBGPLeAAx6iErjGGKisXoGzlkCg==