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
- dd89c146e74649b955912e44d0c468730b5fc5e48c3e1c76744441658aec9e88
- request
- 9003a4fa27569908efea685b6af661df1efe38e4a98e45b77713f6dede33e022
- transaction
- 845f1b4f61704d410fde21c3b4759218dcde40779f71984f325de74cf2edd811computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1820
the chainentry 1820
- sealed to the entry before
- 5f6d580af9bf82bbee6afc20acc76e49208c17f2a60b1614a9ded736e8ed1902
- this leaf
- 9efae6668448a3c2230df82d6c0c1b949c41a1b5d06f063ea1fb912a86b1a498
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- E1tlZhZVhp0sdca4ONU26c75Qbo3VPwObNmtkB1kO/d46X06m7DkaoS7bHil/pOph4j/sSFgTXZiOyuVAh0dDQ==