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
- 8b86cab2399edc8a77033cd829e51ac8f8a814f6514d0f66118c6036bfd561b1
- request
- b33420a3db76def85c0ad7fc4d27768774bd3188821c26f298e1e5f8a303f9ef
- transaction
- c0471a721777323aa96aade8b4726ca094af386a91407f1d3e2639615258a2e6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30648
the chainentry 30648
- sealed to the entry before
- f7c709f9855fd928e036714e9de173e5e35effe33f02f453bffbcef433fea7d9
- this leaf
- 6f7260bcd7ef88fd2f7057e902002c238a9b310bf005fc901f374f5f5e04a858
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 64iDTQA/Jw60Q5ERpogxlyowweR9iS0DhH0cZELGYINULQJzw5VyJHGoG+5/7u6QkmHJvWEFIeUMPmlWeZSYCQ==