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
- b15f2418b743637918857f5965087989084d9861c89a15c0932d49527b9326c9
- request
- 4372bc78068919c6035cf651022c9153592a48aa82bbca6793b600e0a780dd6d
- transaction
- 2ba82b53660130ee240ce6492a3289e77e9331d5cb1d966f237125ada9d3c1dacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42667
the chainentry 42667
- sealed to the entry before
- 0377bf992fb31ecb27eb82200162a2dbaaa23bfb26f794cc3395e1b8bc9521a5
- this leaf
- 7f96206e733b6da1a9e7e93787b518f6ad64c96fea2df78a5eb21165093fe5a7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- P6GTrkq4uLFtAK0LjCNS70htxO8usFsCCodonDb+V/VD2Tm3JHQKXjNkBeEYliqDMYsiCF19sFcR0AI9u9FJDA==