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
- 1f22d69407eec62d9642b4877707494f01b678871da74b6cb53c057a21219911
- request
- 3498f2df985ff5eef20986aaf8ab483af59a20ef2d659fdb7a4addcc26aac908
- transaction
- 6f3ad46c1997f52ca1a4c306aa05be59b8d516df503b9ab48570a34fba7ec6e9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 361
the chainentry 361
- sealed to the entry before
- 0ef4928823a0f5bcf52004511f52c625a09ebbf0f45189c458228d698abd4b82
- this leaf
- 9de64bf32728eeab6b24842594e1dcdaca1759e34f528f9ad8162f045556312e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- zejXcabgexFr+b2YSswx0xmaf8yeg5S19HqGwNLuzSxggZ1Ln+/Nii7rsaPU+GQGPRT367RmOVZ2iCgUB6C0CQ==