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
- eb32c2b8bb4b5204bac43be5795e72f64acd29ab74246a991a3a2b71cea4f026
- request
- 09bb44374b91c1456864e57dd03a7e3f31bd4a46d6a8546b932e236dd848add1
- transaction
- b0fa2c17f440d3dd26695dae288cff37b0b20b30e3d92d7d8452c4759b579693computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69220
the chainentry 69220
- sealed to the entry before
- 01779969f81fcac239ba71f840c48f65576717de19f2f95975c3ebc895e2a256
- this leaf
- e1ccd1685653b29fee0a5581add05ab5979e877776fd9d3a4f1ffb8c488216ff
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lPgkerINZZhlzeH9Kj76p/BYG8XMTCZ6fabOPHKGaqiX3D5ItuNEgEHd5Pp2GtjSHrU4Z5EfRGnw96WV8nTmAQ==