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
- 0d01bb7ade802d0088b733ed584815d3688dc540402ac13ba72272b68a828a44
- request
- 52dbac3cdfbd943a27a7c78c30859f16da87d99c7d2aa56648b12e07d8924438
- transaction
- 27da121f34201ffbd6c4776b249e87fdc2891da0b386f8ee778e8061810f8bd4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 13444
the chainentry 13444
- sealed to the entry before
- 3309155fd48b651fa83d37e0ac5c29cd10b90a75305012148bb74f760d7a1a44
- this leaf
- 8d775e5e59b1b6181d94caf447526ab304444441a9f61e447e1dc0973b3e6392
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- kfhVA+WIhYoQVADdZRe9OpFY6wLJ20UNEFQZ2PemkuW5fO7Yxj0H+SX0wR0+b72Q9YJE4DW70om0FIctnw4qBQ==