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
- fe6fdee2e48ca4fb930c0ad0a2c1c65eef9013d1f6e6cc8320ba796bb7cacd0e
- request
- cfe43f8546bc8079bd96e4498cc8c31b979a5324986ae88b0cf0e74d299efc4a
- transaction
- d660f78442f87dc8ff02f2dfd5d5d02ea9f30419861823db2c1981a45c6a43accomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 57253
the chainentry 57253
- sealed to the entry before
- 41902a0785b9d7d03314e8b2311c84f329f02d3823b54eed944c495028428e55
- this leaf
- 0bb7a11becdef46bd614d64c7d71abc0f39d52c130b86ae2ff463448fb6af0e4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JgJkYp3+T70MvWibDEoqa4mqYC4nKhWhG+rMCocogBwIckar+NzYAeLwwU45R+EuV26JZhoVqhb7ZhcljXWjBQ==