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
- 3b842afc06ce62c6a4af4c2d9545d3a377d18e8fc3726ca5389d53aac3b76ac8
- request
- 8e71b88ef506f0608f49b400430813b2ae686040240bb04a693984ad6a75b530
- transaction
- 38dcc88cc88f57c6d7310b751159286cf72204042ba2a4d5bc03437bcf3243c9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 8607
the chainentry 8607
- sealed to the entry before
- 94effd84cd41df8608ead442ee5e7fa214b8c82f39927a8b1fcf525efc623dae
- this leaf
- ee22cfe55a4212a50d453022a8cd143057b84eec1cd54e3d000ad0b715945822
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- MKymxjG0TakMS58KD53laT9b7F2KVNUAZq+4oLPjAh9GQZhMGyHJGHRTEkcpxD7sX5nsCmb8UE7kyjg5AwZYBg==