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
- 36656de4d040af194e885df20c5044ae18e70d578bd97fe6f19402995f810570
- request
- 9bda816294223dc33a90e617a17eed11e62d29227a06813ab7432ffc2f7478bb
- transaction
- 5320dc02c7b1fb8fc66ed560f5911593b8b799efb08b902f86c0c50e5365c066computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61773
the chainentry 61773
- sealed to the entry before
- 6c454479a6d1bd93ff0ebf8c7d0d9638db63dcfbd3d2dd40d26eada7c4ca86e2
- this leaf
- 354c8b6c4dabac66e87c08bc7366a8e97a6896001f4fa9b6556eb1f42e5eb163
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- TTJ1DzLPZ4OVVMIAt0T+uJRc6c9sop5hJu1oX+EDZl8nLCtH1ARDE8b31woZw6FLo04PgdMQ+zi0A7VJ6CUFCQ==