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
- ceb0e088c717ed7297ec8759ce41582e6108fd1d27d498edbb8fb90faa6b79b1
- request
- 0ba55bf0003071ead304627108cbc2799074f7396b89f4eac52a515be25ce5da
- transaction
- 5ec0da88f432473fd2d4372dc742ad3c9d588643fb4b401574af7a16195d6daccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 54260
the chainentry 54260
- sealed to the entry before
- 578e277c8e235bf16e9bc6fdee1e8681ba259bb0d23e29fc0b49d592baadab68
- this leaf
- 7455e50f9b7790fb9fde770a059d6999d3bc392ac54632003fb4f64b8a83d9f7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- IQzm7TBhuce848bolbD4OaEW6itbKpzTLHF5CaFP73NTZhLBQQ8aNRQE+lV1kYi55kCJmoReG3NrTMlZsgBKBQ==