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
- 7bd7e54712580b5ae484a95aae2dd7acd517da54988ec0032d370bfa70c42054
- request
- a53654238426e267085d0ccab7210840bdac5f83c4e33d617f41eab8cfad6be8
- transaction
- 12e399597d4c11ded64539ec6204200dd728fe7ead91580851007f9b1f0c6fb8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11204
the chainentry 11204
- sealed to the entry before
- 5cac88d3651faeb567008390f78e4a611f8e46ca28db5292e9fa4892e3685d9e
- this leaf
- e4d5b8c0cdb217a93c5f6a893dd08a9b75d554f69686ce8040403815445f0107
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1Ls1NhU7EUsgKgQbsob40aaSIAOZNxdAAZoX3IghA0qEhWPqlymgE8SanAgbU2mZx+hrmgKc2EfsKsqD0Af9AQ==