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
- 2374d3966facd977477db46432d47af5e90a2d2185a2be05d8252ee53933f2b1
- request
- f96ec030ec030f9dde141ac069789bbf485e3cb026f1a8dc9ae20d4d6228ac6e
- transaction
- 58b6f2b13010d3fdb15e93f65054e517782199a6f227deb8eaf76a344d5b230bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30946
the chainentry 30946
- sealed to the entry before
- fbf76129f3379bebf3441b311bac6820e32f9e5eb3d79bf6f00f20744f98e102
- this leaf
- b3a814ac359860b48ac4fc12f6aa033e0fff72342e70d04bc14be138a05dbe2e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- pjF0Q5fwdVDTJXy7++S4VEGsFWnxD5jvgR12gQC8z/dcShUOSuXQipc1HJh1eSZMOLF/xZxr+cAIfegcBzCXCA==