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
- 7e2c450500c3885cf848f45cc89c88a5c570cee9cf240bdf8b5a4c5a8eba458d
- request
- ed618056423a36f485f71516f3ece5642baf66610073c4a4a267e930194d7aa1
- transaction
- 25c3aded4fed2e9ad585ab530afff449717b07733bc45360fbd689190d72ef70computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 3784
the chainentry 3784
- sealed to the entry before
- 9c9d7aeaf245a80202075a27c4cf0566bad0c10be7e331b94fe652cf3b98d712
- this leaf
- b2c45369651f35fefd746c486e352315119a2867f2d75997b8dfc54b4d9ee7e3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Pe+Z76SX9k21AZdX0SXXHUgmNqoWQ2j5q+jOz3527wPOGLbFMtMVkBAkntxYYexE44K1XCmCF3WvuJbviCL/Bg==