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
- 9df32d7e7d5b1eeef531d947a015ea471722a74ad065b42b3907c4214b0edca3
- request
- 101f31182fc07a21d911e12c8dc20330ad9f6abb42e38914972751357106f59a
- transaction
- e4e15f46007b7655558298f0591fcc50f39272105f12494ee4797893987509d6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 71072
the chainentry 71072
- sealed to the entry before
- adf8d693f15d7d2bb98d844361694728423463fa4f8bac1d9733cf55204a5f2e
- this leaf
- 26898add786458d0fc2934b58ea1bc4adecc5dc42268ab1ea7f4fcd0789ce019
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0wG9yr6lB9a0bWuIPms4uOL8EbDcWPlarEXLskcnsMcOK3v1BYvHZU4tqEd/5Ea05FXA+BCfdACi+B8OqGinBQ==