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
- af2b2a1b7e9dce3deacca36493a93f79ada29b5206d4db1a8640e0d96eb051e0
- request
- 3a6051d9c968a1bc6bbd4fda7d70ba2548c1278152829b5367bf97c0fb6037ee
- transaction
- af022f6c5bd8bd94d6e9d128cb6f5f523b5772454af7645ff37f79d4767633b9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 46092
the chainentry 46092
- sealed to the entry before
- 68bb56f580d079a6cfcfbaa869e46a3885522f3891cd8ee0f085bbed7e991443
- this leaf
- 0d609baf8bb9a613ec91afb91fac9d2eb19b94d06b5c01c66409e74a3f13a29c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DuYFA8oBUe7VRE34Vi0r9glajKqRQb1nYOahXd8RoOGm7x01Mq4zeQfhbPlsJBj5zYr1UGsPSWVejvQgsqEgBA==