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
- 56b5ebb98bd70a27a6f9a2b3af5161aabae47f1cd8bd384bb03d0163efbc2ff2
- request
- 71452c7330df77147905d179ed6d057490fb397f072edd308e12d181352e82c7
- transaction
- 3fc5adc8b47aaa94883f3d4914c2e8b3e7e280249b655db8ffdfd5bc0725866acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20569
the chainentry 20569
- sealed to the entry before
- 6fb267ddc104bc09723bd4430825479d9b207b8126f46c2073cc2783eb8bd7e1
- this leaf
- 2bc0a621fe13ec140312016a80c1bbd7a54c9e2733e1c4400af7b3f558dfbfa7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mrurU8KVVg+MBz9Jgs0O6H7P7zQ6XNEaOB7K/YypnDIQ9VYLkbQSy/Mm69DwssO80xnFJ8pcGBgvVZOvLVYQDA==