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
- 151800136be1129128a32eb09bfb3da5a7ae75e9c4e3b443a7c8cc24c1e2d24b
- request
- e3bc75ff0ddd887620c627c8be94ec8697f70c79deec997515d13043301ad8a1
- transaction
- c74ec6ffb3c2727545f788fc04a867869cd86152385842a136b2701fa4deebf0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2500
the chainentry 2500
- sealed to the entry before
- bfa07c30b747929496bbc560da2eae32846fe8607b0684a17ef5a9b72b22ba35
- this leaf
- 8a86e34783cad00c95099bf259a527b9bb393a10cda50b0c4b7a6ca0828ff1ff
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Tty5Uja4te9fBccE57m5+Yu+Ifzrg+vjGqOj2mNnlMY1gA/XaYMstQ7diBjEsnS59+VoZroGaWxCfprWrqX4Aw==