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
- 7a229e26cf6b59c6b88a2035b6957ff1da88331d3f155072d79783646e52eb61
- request
- 786eb130f9e89a359c6934e4185fe75172e7bfe5e34adb1330b5ed6849dff26f
- transaction
- 7da795d795dfe6af92373ce4900e683169ec29b347f945b5ba89930529e5d024computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32321
the chainentry 32321
- sealed to the entry before
- 6c1c165b79853078fde9f5302d270f96b2f7fca6b409a6524f37a4d3bab7ef13
- this leaf
- aa82725a50ffe650783bb7d9900eeb7e9c18649f951d2004a0c9e4be910f9bf7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mOAMBtb3danUWZ0avOMGnmPRAWKadyW/YsBIdERaciSYi4WUgE4TSb8X6v0Gu/fpB2nSkVj+mTd4BGHpzjhJCw==