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
- 942668769cd5c5d79a26ac611ff4e0881a394cd159f7641b66c32a63ea436480
- request
- 58af7128a6763f772e75868650f48d7c3b0589f9ed60e32e9bc52d7f8dae9b33
- transaction
- 38eb5cabeebb5a5c961e019c1ec1e514907f497988a016fa87aaa0030f38a40ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73785
the chainentry 73785
- sealed to the entry before
- fee60dbd179e18a3639a827e4baa0f5c7910fb126bdb7ef47fbec7ece1bd80c9
- this leaf
- 17a2a46aadf77bb30f754c57eaf33d268f0f871a9f193d301ab7c2068775e49d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- sEFIHelE1I29h2CserREEV535g1FGbP6ZpJNQPlk13YdkyrVCiOz5jnleWOWWM8NE0ZTX4oadDIerC3aSZFHBg==