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
- 02853c53ce1f567f64c43ead9fc63eacf41bc7de67ec0913095d3e49ab5a6235
- request
- b29c0e09ff240bf229c35f1db55fba6cb3bc0d9cd28d55bdf9a21341cb6f739f
- transaction
- 829bbb30f3c8c5db1b2dd521ced4b73ef4687ebb89941c058e9156b768e1f810computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 67210
the chainentry 67210
- sealed to the entry before
- 350257e824da36ac75585a9ac8453fbb2761a325b42dfe4731a9200057e2eeea
- this leaf
- 1dadadd975b4a1dd6e793e7b178ff2b1ffeac7bcd7f06156efaf21bbd4a217a7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mL8J7M4uRqWhxlGlZSxz2A4L0mIwaXW6BIWPEHEIpzCkOBVCbbfSpcAt7O79WzeI0jnifrqXgS0EAY1rq5KnBw==