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
- 5c4fddf283955a49ef9dbd2f0cd055b914f327b06b497ffceb6d5d93d5a6152e
- request
- e519eb2992b5a2f92260f8e8c9bf818099b06d646559079111ea1404af6b2e32
- transaction
- a2eba3f17eeca5d6db309c427ba2b1a785f9a965b13e29258818a95bdf5368bacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60072
the chainentry 60072
- sealed to the entry before
- ca94d3893d19197f312c0ef6e47efb37445a5229e69184863fd3a7e6c75e566a
- this leaf
- 84ab9d45f754dfa9281f388561153ceb9065e558c3a10110fe5685664140ad9f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- KAlUhxL1Qu4XP7iatVZ1KKKdkYy2CWsvpfzKviYBpIfyKzfXCWPZwKjAzJz4fDG/0f/WGcgnThz5F8JJiPLGCA==