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
- 21a6478e6d5e823f6b26a216ada7d7d7bc6f61b3f8bddeceb4286f1a2da42cb5
- request
- f99e77fe774230ecd9d40b09f355ecdd89803ae9c66865f50c255e2d85eb7b4d
- transaction
- 66a65e48ebb0b09ffbdbaa2a43c0fa3a12c110d8acd56c44511fcf5ada1d7626computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41866
the chainentry 41866
- sealed to the entry before
- 0ebc099909f39124da1d43ff7879bf03054cde0096f2b7ab17fe83cbfc941c13
- this leaf
- 0a137b879281f264dafe2ac6ea6a6d1413cf5eca70a9a7ab7158271a54f57de9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- xt1xagFb+CNM8QxQPp4AhhLFr11IOgzEr1XPzF1w81QP9bPJs7/tOgIhXEggMVQvPnjvvc+dh08qWzmjNGFEAw==