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
- 91fbbebba9ac9690b3d3a1a979454b2af7a95a78a8bb0f800a7fbbc16b4179db
- request
- 353bf0ab36868d971e9b3634dc0d69f25497fb2fb1bf902ef6f7f1e52919b099
- transaction
- 55b33fbf542b620a9b6b3d69912265f35bd93c276f84876d0fceacc425c4bc7bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64810
the chainentry 64810
- sealed to the entry before
- 20704d3e62109f2fcc0d2b39585d8645e130de55836774b9a32653a12e297985
- this leaf
- f546bb8b78288fdb151596f4b591d73eedd0ec0cef4cbe232cfab0869c69e587
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- uSWT0EWXPwkxuHDGPN03lQkNd/DkIQFs0tv44GuD3zl1vmUMhxm0kmwc8gDb+RkauYzEgcqR+ttmnAW6BI27BA==