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
- 6c6660d95213a2100e335d78a7fcb41697e128e752b0d8427159ca56c7e8df4b
- request
- 23927e1add0c80709301b5af07222693746a8fda3bbcfbc1a17b1782029ea159
- transaction
- fe7528567b59b747ab1d58ca599763130875c0e9e242f3a47edb24770aba0858computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 53552
the chainentry 53552
- sealed to the entry before
- a83b1506e02a395db1ed2bb72deb040f20b588acdc787542a634aea3536fba8d
- this leaf
- 18497f45a618e526fbc9f4a7b524a20750fc3b8ad3caeb189ff3943c0ba8d676
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1l3jf/sFyE5PzuXyF3/CCf98ntpYMjpYUMULua0RoOQB4PuduaZQg2176QgUHpfBxieTqoadvMGA/wQ7sqQmBA==