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
- 90ce164ef6eafe163b7277d1e3fa9fdbfcd07813ee6f0b6894ce4922237a5cbd
- request
- 2903380e50785aa8cc09329174d277fed14919c7afee37f99f29c0b9bf558035
- transaction
- 23da092d1d565f7c8e091cbc9693e4587c8bfeb9d89fa3067afdd0df9d1909b4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 15405
the chainentry 15405
- sealed to the entry before
- b0f326b62724bac053469bea39a9717cf32772bf4e6132f311cf09e2db97458f
- this leaf
- f8e56e32182b171338b22ba1ce75bc3d19b734ceb536a5f8d384ffd6c9822535
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- gIBg579u1wP4N9nfdJ5Wo6Z3jgkS94/+XVvCWy2g3lm7qJ/3YWCsKDox9iUlgoIxE+GHE6Jxgxqs5i2uEO5jDw==