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
- c50cdc330a40f1aef77db47d8859c9b0ad908669fbca665df1d5af4520d6a041
- request
- 0fd17f1a52ee5d79511da424e9d95949b3badd98f97a3581f573c5408e5eeb1c
- transaction
- 8366512f6a111f7fd25229ade9bd494e1d7931207ad9aa6b0fc3afa0a0a47250computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64287
the chainentry 64287
- sealed to the entry before
- 9336a77d15ce02bc7d36599ebc5c3acbe77f84ffdaf94f6d51212b2cde24198b
- this leaf
- 6a35a0cc889ab1c446c5f17cd60fb0d9fef4b4af41d03b2ae7d3facfb0cfbafd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 8nQkqhiEt9og9MkmsmvFblsH5h727w80xIAlCvT0PU5OR4x6fYjVeZ+BWMXVY9Z+tkv6OZ6Gt+Ilz/tJXDr+DA==