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
- 239bec610bce6b57cce31d5b82509785ddfe6980ac7c691f56205f7500ffb8cd
- request
- f03f021d39d087aeae23679482ba97da3beee55b85054571b62a5b9ee09d4114
- transaction
- 0bb7a29ddb66da4ad39ae34d2d03f82e2d90de35dfa508e1048012a31401a679computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68779
the chainentry 68779
- sealed to the entry before
- ee454d5700b504a04308bd610c790870fb773a3a5391ddaa2e3cbfa92b7e6123
- this leaf
- 142081c91fa93a6aaf63206a7b5dbcfa5aaa7853b171fc5b81d2015685c2d997
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ZVPRYlqAvAP3YkJ8SIw0cOhOnVMgduBcj+Ijtv9GuscM2voD28+BeyI0Prbb7AFu2Kx9SoaZP7HQODXMbk/DAQ==