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
- ad1fc07d2c83885b561c263167738c49586b34911a49db0dac1f782cfa5eae84
- request
- 6139ce7271148978ba6703226690e61dfc0f6127af2e778b1993c126924469c4
- transaction
- 2a96da1581d2988bc97f2639dab8b8d92c4b3f583d7cfe95cb27de8c9bf44636computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65724
the chainentry 65724
- sealed to the entry before
- 47901d204193e8b202bca9dda875f421bebc8aba7472ed8ac4360a8fa1d916f1
- this leaf
- 179091a871aa950f5a7939b93e9eb7152ebfd62be2cbfb8a5aaaa7bb0191b2b4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /9kAPjfUatH4lhFlMYLS8V4mhQ5dPzEdAHJJsFkgbxQTc4RH44TuKElgsSNoLG30W2SzmuoZUyJqALNF/6NfAA==