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
- c739472c4e75296d3e95197f7510cef2f6a2cdb2c87085d4c0f9c0f8c7666732
- request
- 4e1615cf0d5563e06493942db7969ae5517f4b45de8ebd2702f97e47a3001e5d
- transaction
- 78e29265c9a124f8647a4953f05bf3ecc52b60eec46ff6532f4523b3946410d2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 9755
the chainentry 9755
- sealed to the entry before
- 7b5f7ac63e65d90bd426929ebf8c5f826bf2f604bd2bd16e5b070c451e042968
- this leaf
- 2b09f1513e40b17c8be27a62496c25f4f0720153bee00172ffe9b5dfb8216cc3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- FawQM/7oUVC1On5o+ZKc36QhVCJE8sGpOUJfBF4oP07tALV2JG7uj5UDRyFOk15i8JRQ7TSlZZttaKhAOkfbBg==