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
- bbccf866068602449596dc03a995ad089938fc2579b092801d746de75f9ec475
- request
- 30c8b7b00a90672be743320ffa6b6390048d01ee5ba878b1c2dea3b822d7ea0a
- transaction
- 8c658c7034da72d0133e7716225b2a0c2603d373dc136dbca2d9586b34695697computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72338
the chainentry 72338
- sealed to the entry before
- 8827315d6e51da2131fb360e5a8eca9bd7859e98b962e71f274adee607ef405a
- this leaf
- 4800ed12d6b84ed49fc03514273541cb82e9433935e331191e7ffd230b2abff5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- tTKzRXlzl20v84MPVuA8YMlM73lqzXHjoKuXFyVtdDtJmz87nbw8s/P6VjxOwLuhFtiOQNSor4aoc3NvZrmtCg==