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
- 62ebec29025e6e629057cc12ee3c97888d583aa290328c19c7c0b8ca30d4026c
- request
- f206b729c696ee1eb82d60f00f2bea82318d91ac408e879bc5ea1a8944335457
- transaction
- 70cb199454b9d576eefa68b0848d04c2fe7999fa22bcc5288ab0f51e327274ddcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2430
the chainentry 2430
- sealed to the entry before
- 1cf0eac5a0dbdadf749f457a508b76b274e8e50a04c57a1b2ee770611af0c289
- this leaf
- e11b24e3c45444ca6e6b0da072d31655d08af104430ea44ecac35fe96058d4db
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- jLuWPrwtMCeXz0FklkQ1wOABxNoSkYhZwlCp5WFEY/ZpbyjmTUrrha/3kSuzbSneFYN3E/gnaM+8t8GlbOl2Dg==