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
- dab530f12b122bcf21a9913f3b496517c1dd54ec9be5e05c14a38517dddbe6f2
- request
- 22653740b2aaaafef09a27cbf8fe6c8c73f72bc460b20c506e08416b2259e41e
- transaction
- a5fa5452f21b54a742db2e1c942e7f7d91735c4fd40fffa9b29d3fafe082b702computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 71176
the chainentry 71176
- sealed to the entry before
- f7e64c01ce0f2bcf98e112d50a6aba856fa8d2fa644d99a1e6fee78c5ed1aaba
- this leaf
- 4b5e2e2ad89b6f696064f4f9c46c9afa984a27c5428ba1d2741464c9b3fe3eec
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- J5FwjChYxOO4b04B3xjjlE5cAzSRQIAjT/DE2Y4TyFEdDeOBBxxadiDboYUY/T0hIBQPhgJyR61bQIKsjPsKDg==