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
- 8259a441de38c0836fe0ea46e4172b8b1d9978940a28fac323d0b040ac07721e
- request
- ae26eaf0b450cbcc47eefd458d6a7c2760249ed25c89b0bb08ce205ec867a181
- transaction
- aa45dc2c62da26522ba12136ab249a2ec116b8db73cc09a7dba0d1ef9a422a69computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 9919
the chainentry 9919
- sealed to the entry before
- 3aca1db61c8c4e999e541ceb1ac9979d9f916e0d4ae27f71bea4825ba0e83179
- this leaf
- 48e7bf76133486c635dfc402dbb025378ab8619378e78ae7565ab7fd5bf5ddc9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lTRULz1mgCKedecAhNplC9S89/wHp5MICrZOAlTyEvh6lTP9SB8kVM7Xs2qt7gMb+uo7b06JR9XXbzO9Vf4jAw==