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
- 425dfcdda0a63aa38c99829d39e6846ef8282c03fae911d550c6f97c9244b068
- request
- 898b1a74520305e3047dbb5e22af38d303094ce436d0084b128518d773862b4b
- transaction
- bd3c6e96502171fc247cbfb2a45429ff728e918e86de2cab92783e031e07cae9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45337
the chainentry 45337
- sealed to the entry before
- eff118474b83592fc9afad440f0313750b247a1467d8d6b56615dfcc6c2b1891
- this leaf
- 0d7508a945eef2dc009206467fbe5930fddc64794f7331aeea16bf316f9e274c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- SvhqU/lARQavnqY2ATMCv8kXiTzG7GS5Q3WB+RFKGzKo5vddcnYBPi92EHNIOlN3AJaq8jHSd5bkzGGLnz4XCg==