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
- 2ef0bb11d1c3870e30d2d4cf321a52dee4a9e32564f5ce5ad03ab86029ade24b
- request
- ef856639fb3db70de4d80f33277ef63d15e432f796e2ab19bb1d3aba1c281d02
- transaction
- e8f06effe081858ff829dafc32fd6590a8cc3f2addf1cc2fb4b8d225e2522a01computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40878
the chainentry 40878
- sealed to the entry before
- 723c993233afc8d540159b2b0ee825bb05810f0e0b3a0eab45d38ccd616ae8ce
- this leaf
- 7fbc48e2c78209ac8028cdb17fff6e327910dbdda9d7dca26353d97c4970d167
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2gLppS1lkPZWLXjjV/okPT5BE8LF5sWQ3L/JfUfaGQEGhZplXWTt5+pvMQS0uKKvefRMHUCdwIubVRBjZwBSCA==