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
- 58c107848ed3960c4484c54c056408ad727aeec3629dbf66197810d79d0f6d47
- request
- a51aa6071acc3178fcf121c8f1f7d437bbaed29a39dae35c99b20cbc5ce0495e
- transaction
- c0cc97febfbe92fb91bf2b6237d9e95c3292c9d36fb76e87d89c960966569b7fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 12467
the chainentry 12467
- sealed to the entry before
- a9ace7d183aa97ca30676f83834b3bb754b75488ef5bec10fd4bce247bf7543d
- this leaf
- 5678ec1ac7d0bf8547bfd52ee87d855992e3678495cc11170a1f0fcb09206a87
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- WHNvTcLGYOB8UwKdW/ttxKF0wBM0PKQ6Ll8TRepj5ezp0+S77iRkboqfPCQeN1YmXdVnY1hqx+30rSamkKciCg==