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
- 9ffa984c9a6e82e6e8380a41ea20d7082b1b02383a00ba87dc4c35916979b478
- request
- 834a567ca7dbd53769eb8acc08305e1cd56785936dbc5ad4895c9fdf09ecea0e
- transaction
- d8b162b673ea3fe5954f7452278142df3d5dd3e2cace0741478e7e6222e0c93ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1200
the chainentry 1200
- sealed to the entry before
- 910cb2669171d162566aabb98175ebc0fe63c993d42f6a3e4b34a984700d7137
- this leaf
- a58e0d09890059a6dd8c164fc9187d750c26366b2c7f636328d1803786c3d348
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- b+80ADL19c2bRRjx1fQuEAAzGLBTO+NOxPNdD1aErzzJYuGVsHl0IE2HBZwRFUiFTu4aS9fGXTlpq4inKqdvAQ==