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
- 7e32d2cfd72f759fd59f9b6724dae5a6cca5822b4424eef10376ad6a7dc59506
- request
- b85acdcb0fe806500d2cacbd8ee2163042ab7e6bdd37f2e8f25304a976d2e625
- transaction
- c451f3bf86e125ed42da552e8a9aa0eba6c128fdf5a8765669279b9f2b19bac1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10338
the chainentry 10338
- sealed to the entry before
- 3f1b31ea7b03a23d9214ea1a4c0d6ac0491ff0083006d6e38dda44346d939793
- this leaf
- 791cf3d71d2e81e1edc2e02006f496cfcc8b956f11b0006a180c69a8debd7fdb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- q0jreMF23vhFhw/VZ664K6Rl45lQAPVbiDsen/672pcEAy7sfoja5XPhiB0cjJtqP/j6hIlhjwK6J7Ii/PKaDw==