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
- 156a89441d5e7eb05995131e143785dde2828c77222ab4e418889c3aca996eb9
- request
- 0a4a5664f6a084de61a80104ad017ea6b253e00dc0ccba25f3cb9732532573c6
- transaction
- 14600aa249ee703e21a8225d90761df9516d707e0d4d649c550054f90fedeb02computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60411
the chainentry 60411
- sealed to the entry before
- 1ca3854b560e33db640e7b49936d0dd6c79fb68f5d6d083e93f84273d9620804
- this leaf
- 20fcdb4b36e62647844cfed0a1473bb51262d878d1196d7405d164235ba13753
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- aWSIO4htdwOZPn9OiCHPU5BWzZubIKnvhqrkapl2yL/Kd9+9zMTTRNGoXu82oWL82ZMbF+Rmqo4RaXohlTcBBQ==