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
- 2f5f7c60ea571ff17046b908e78961a07cd867630f147d31b3dd703963544cc9
- request
- 91b16cac78d3cc72c14432b09a2b24b058ae0f25bde947685b35b2f07064db79
- transaction
- 4844f590514e9914ad8966c79ad81b8ffe04e9c160f4561ef0959094746e231bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2275
the chainentry 2275
- sealed to the entry before
- f5fd9bd0e42052d924e8b8fff27acdb1d0ea7e214bce458bc2186c49fb31a05b
- this leaf
- d60bb3ae3872023768534d8d581c5d472116ef1154ec7211aa19dbb5c4cadea1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- kipRrJ9IIEcyKu3cprj4l92Z+XW0NGEuNape75kzKA0CgSzKW8AQl2QD+lMIRJ5PvNwmy1vdk6YXR0ut5DEmAw==