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
- a5f3315cd89307582ebfe8105307eee9f705973f5c81e9d2af44d907bd620224
- request
- db01548ee3b7a5c1edd0e5de604fb5f986fa87f04102817bce6ddb126f92c8af
- transaction
- 9c46686a74e9dad0089efa6802137c4e640c25f3b5ded7ab456c37e3277616e6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 406
the chainentry 406
- sealed to the entry before
- b4253d87d96aaf1cf88d9e801bbf40f8a95d35233aa2b9182f70f615d4de3343
- this leaf
- a934701dc2adf4021e7ec87cb5f0648c054b5153d9015a7227ed249a49abcfc4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- xIN9zwJbABQLCYdInO2zzHn758dbrMZgdyHHG1nVlolNbA0XyOVF6WLKeOBQoCZpzg6IF5+IoRF6fDg7ee5TBA==