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
- 5957744c3764017d746748ba9bdb159462da108c736240176bc2b9f162967329
- request
- 42e01b7b7b4d33372685a485102bba5d9f38475d1c02e03ee1d3137dd7b78030
- transaction
- 6c509dbf508d80a0c3675f7572cb0a9c921e94e9e2139aff4579ceccbcaccbdfcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 396
the chainentry 396
- sealed to the entry before
- b9502149c58f866bb810e36e4a113733c5beedc02f048c731d2588a0bbe76816
- this leaf
- ac6660db10b17a0f187a4d59f74fa1107052f65a9950e9994909b691510fc933
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- s9+nnpfJaHLJmwGObBtUG0qS5LTh6EbEGT+WtKa44TOwl/VWuF4xEahv4d9ZH1zhfS5KvZFJHaHld9kMKr5xAQ==