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
- 8abf7fee91b0ba9d9fd4adf7a2c3d66d40cb9d73e1338566cbd7f6e808c46362
- request
- d4741aad6d2c93b84440b038d6e8da036b0bea9e0604bfbdfeb216222f1a6be8
- transaction
- 143bd9a0440d203532a81bf1344ccf261da77ea569351c6c90c61ce35396f315computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 49026
the chainentry 49026
- sealed to the entry before
- a1f6d72d9ec54366fe11ea874eff0e96092b876ddca6d9d179255b5be7cd265d
- this leaf
- db47e4454b6ce5b921c8f5c8a0b81d4fba40bedb2f2426df3683f1cf768e0f38
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3k2mqpWc4cyTwDGmsdULpzy4K/NN73g9tGjw9LtnbQtrln4eYcWYdAuIO7SeuoIWJJFWzbxUbu5PG9nPNE5aDg==