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
- e06279b5e9f8287dbdf1b9bda0649e2a21f30b7826eeb55dfc34e0c224829d17
- request
- cd8d730db938c123ed2ce1705ce8923994163a8d2dbb364b690ad3efe5279b42
- transaction
- 584737d09b31c290248027d7b218c3bbe73db6776681817cf65fc486d97ff809computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 47425
the chainentry 47425
- sealed to the entry before
- 03386955be3a0ce21d2a3908148b2cbc00edfa23f554f103e1ad68c341dac85e
- this leaf
- 0acb7c90c9874a97e0a3f445bc6e046af32c440cc56dd933edb31b6334e5c787
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- VDmXAwmqVUu8/5UqALJB6Ev0sJvnAcW2nG/J127y9uiEwXUkHeQnAVgpTQe1yGAVvdFqIWGpVUha5Gpc12PwAg==