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
- 654a20c7429c6348d73b78e15b078de998be7aed2ddf2ac69ae428e779a1e411
- request
- d254a2351f1ed1b1643618d31250ee3570aa4346d2062ba491a43a7bd5914083
- transaction
- 5c3cabd8b712a90e1c2131b53abbd00563858624052a7ec01230ae7aba061223computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 54318
the chainentry 54318
- sealed to the entry before
- 7c5592d1a38a37fc9b375640ffaf5769c0966ece62ccee0055ae2278c9a0b27a
- this leaf
- e7f45b538900b7a3584ea00edc17ee9be3f8ccc40a85cbaefee3ed7736c78925
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- NJVBFjGeDE02fZsKJxW1LgMyqq/okxgXByBYROLYk2AB6kES03WqNsrsm0SgXwxwTEz36ZDsr5QsfvPsa0JhDA==