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
- e10393a69f5d629f65c95ada03111a715b555189e9a3febb311f16461672c7aa
- request
- 4147b13ccb5bf08bda6f5a78b9ff289799f43fbb2970caddbe0c000845009171
- transaction
- b87539970ad18b03dd4ea901218019cc7b9b20f19b02fa81382bbe54e1fa95aecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45460
the chainentry 45460
- sealed to the entry before
- 55a4962c844102788ae24eab68ab2cf843e8a391ce41e8e52e099b57b851e3f2
- this leaf
- f09ce054a2e1c74f92ad818b54a2f3465c5d738a78b2f3652f3e94c4e9763d6c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- t2tVC30h4aOzUja481+BW0iAjcckrjDKOuSP8hPyoJcQUXQHkiAcQAxZgkR82p84a8YRbVsHxnRo4CGGh+mpCA==