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
- efdeb3011b0c23ce1cd98f361a531237ba41ad22dca18ca907535df504ca240b
- request
- d85f6ef9fe448d2998a439e69bc3c88a44ea3123e987c6a1290b58430a787e76
- transaction
- eea9091ae47172a6fc7401e0c31fb9856469f952ae60ff4e0429a1df7a63f580computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62480
the chainentry 62480
- sealed to the entry before
- 91f13479c638d7c325db084cf2e24732ba0cedc4c8656883094eccebc9f40879
- this leaf
- b9fd68a1d0320531c5ecf052e65d05215518151e571ca949c4a5a048ca3f3917
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- UiZRYlUGS11UkmRMr0DFo0CscvYuK0gzFUPSG/CsAhRR3yl/XaL7s3KaUJDuWC8IxOzH9WpQneAw0OjbWvDhAA==