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
- 71b7286cd5ac29cb1d9f3f3fb5ded188e0d82fa4dde76faabc131c3da0a978bf
- request
- 0fa182e1da06ec9f108b2f234fa92690a2f9797ecfc20cea26ddbd7bdf3b211d
- transaction
- a788e3c0004ac0134c6a68e44d5f27e6da0904ea89add3240697bde05d6f3536computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2625
the chainentry 2625
- sealed to the entry before
- 8530df64e06ed390077a371f9921fdb201ed8021c84c12786544d86d2d0e388f
- this leaf
- 706929d0a45c498818455c04a1ad3d043c6943b81fbab02c77f27683eaf493da
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- IJtRgzHNhUqh7p0r1G4rekRLui/gKD5oYsWMy2DTLSeJqVz3sIpqaCrATTUt+Jt/80SHEruWKboV9FaolLOaCg==