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
- 1ad546e382b5eea944ba8720aeb384b9dcf8c7ec3a7b05fd8e2fd0e3eda1a70d
- request
- d489cd4267b2b16d65467bac0ced6826f6363de0b2ffeb99f9e99101075266d1
- transaction
- 9d57fe344b2cc08d35a9de0058571c1a9d855079ce4fba665671541921b95561computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32886
the chainentry 32886
- sealed to the entry before
- b82a657277c90a0a766f71d4578d87366dbe728ab76d6bb58afb1fcc029fee4b
- this leaf
- f39c4046169a7c71e4a0685f1660b679a0b71aaa2422259ffe2f8032ba29494c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- N9izyC7O3D0gojfdgW3NaEX6KkctZL93qDS3QHwHpMXs3NFittu4haWPB9NOhsdhXSJs12t0dl2uAS9GAej+DA==