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
- 8d2ce1e7166696953a40f4900b645c9cde2e0806b7b80d987cabb739cf0c7123
- request
- 0bdb105a13c59595fc31733919bbcab56985c6a6f3a6df92ad2ea20245d5c6f6
- transaction
- 1b9e87897626028ff6b33df8dabbb6bf5d87601e52a08f68e6f107cdb09c0af0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62340
the chainentry 62340
- sealed to the entry before
- 62077107139c961ebac899edbc1ffc33f5647714a1ad81e90eeb0167a10cb60a
- this leaf
- d74063f6286fd4ff0e7b296584d1aba20f2a30eb12be7e0005d3ddf2327c1b77
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5PZvQZDHLMAcXzLZLHEE0BVS5Jm1Lj4WrUXX3GB8mbIA/vMZ8T/zAXqK11tZimQBnDLCJJUDw3MfQxd09OgLCQ==