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
- c1607aeacb38de192121f1a9bcf1a33b55303dc20408c9ae983ef4f90963b71e
- request
- 0d3fdf7bdd6dad1b96151e2e4a418409c6460b06c40f511fdbdb4a3f94364070
- transaction
- 489c90680111ae53cc4fb50659645f962966f6bf35b9d5bdacd07b077e298561computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 49746
the chainentry 49746
- sealed to the entry before
- 54c514662293d1d6b01f1af1246bc3b2a96b0832312b6b00c0a23b0be09d212b
- this leaf
- 0a5e01a4b082319fbfc65ddff94ea612b6b5031b6af252e0d416e309481f6702
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mwOwCkoodep34EfwO04kHgEYv1slcRcG3R7GgtVLyd3w1RG0Vo62vMoYo6qPNT3vVg9UfCL/yb8KPpIqIVLhBg==