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
- f282cc787061d76ba9fade30d9f8a18aea2c2886b29b1e1814d1b2499b1e05be
- request
- 01af14a451dfa43eeb020a5e0fd0657b07a7145c12d2c55d36372e75b0b8be8a
- transaction
- 8208b324fe7438603a296166ed5727e36b91bdefd54e9f4b77206ac9590fbeb4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 76063
the chainentry 76063
- sealed to the entry before
- 5da01667a3fba5a7119af6effea0d5e6a610ae0e32f5a7aacf4ebac741d63a17
- this leaf
- 8b1ccc07457ddb2f252e669f99f728aa5bca2847f4b6d30dae1a135cca9899d2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Xqhd7qS9Nmag37Mb1wKsY/uz2OPOeQniO77viFrCf502QKJtQSD3KcR3bs+8l5648wc8OiQMzL+lx4Qc2cYBBA==