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
- fc2a5a18d07b07489f87949836d9a69e0c1636ff2d1378d788831922f604f75f
- request
- 0a0c2973577c8d91cb1c39a476d7287ef413fce4e56fdff48eb7428c7a5032dd
- transaction
- 3a9bd07fe56a702ccc59fb9669055b8e4d1854a2c5df24c874378decf7bdd0c9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39591
the chainentry 39591
- sealed to the entry before
- 883cbc43020dd4e11b3e36639a7f8223884383d7372ad0e793020975c045fdc1
- this leaf
- 6dedaebcb92f0e48bc750589d3cc83b963367fba3578cad2e6fb90532ab76082
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6uzkFQy2C/VrktlAbljKKeD0AevVp12m3xOP69dhVyCK6d8Oa8g9JiLielaa22B9zZ39J56N4yTdTrBv2zkCCw==