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
- abdeca2b8523b981f6822e420ecb4d20a58f9431615e1eee0a542c98d8ac3d14
- request
- 09a08a377ad5ed2e3ca26b3bf237487e6ba85fcc3253290197879f5ef47cdd7d
- transaction
- 3d1e7668efd12f758d90cbf4f4aa528201f51f35fed0775edf69c426e1a9bd39computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66789
the chainentry 66789
- sealed to the entry before
- e084ca60b5c4eeeeb2eed3b9f76e0d86114cd700e8366f9b689d091008008f48
- this leaf
- 0a6cf8394d3baedf4a75fed15977d37d7be1e34e2b651297c673518d758ffdd0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- EL97nDDjA3Mk2s9pSr4Rb1i+k5IjbX6LwTZsSOrEgVpOEU+s013SERlgQcTIA6KRabkZ9VXNcUEhUPPc4HMnBw==