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
- ecdff751968f565a78f36a57cf78003faa5b074b9fbb130982513b5fe77c0b7b
- request
- 41e1adc142504f3c42d548a2b87db6ace7efef705433ff19ff7c59d4989b8715
- transaction
- a855fd9d9c986ead21145c4aee595e9c7368e87d51554db3ade5df9ed8e77139computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 14804
the chainentry 14804
- sealed to the entry before
- d5baf2b42bc7647f7a7d8a8661abef8aa07afa7d58dcbd561ef6c2aad46b99fb
- this leaf
- 57dfefd459b48d4f4d6393ec3b4c3590a3d2274f88229be4cebba3b81a67b519
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dz5qyAUC982kxHO9qAE3sQSMbyWl3SjKoSACqSVZmLrirAWL9UMQ7NZ2zh+Ea7QRxETFEDBk7+79sLlApbeuDg==