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
- c955494bd6b85713bac5876dcaa5ff4808fff0511f2d132b0f84a4ce343a15dd
- request
- 042e4a9ecc4d8170260a998a96a9cd3bf51d74fdd51ccde104f01779a79f5af7
- transaction
- 1e0030994884cedcd30b74e78e77a919f40e94cf3c895c4578c9a5ca5bcb7f77computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68598
the chainentry 68598
- sealed to the entry before
- 043cc054338371f5907d876ccbb8538940cd0b9f12cd3a9c14e5768932d5038f
- this leaf
- ba98b6cafcf5e701ff0b0ab0b585a51775becf23956066c1430e8f64a2c00a5b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- sI8bEhMgrTcRAjaSr9mpbn2k7MfxIxRH8+OUAt5OO+Gqg3j1A0gldxp3iWyoub07kk938z4DnqoFRURAPIGPBw==