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
- 38b1916d37fd18da01f400bf23e584d54843927bfc426b3fd38f97b587285048
- request
- d1584bca79b805c437300265380b333454567a6053954cad8cdb83f3574a506e
- transaction
- 113b86e68053a816fab37e19d5a2ec6913606a54613c496ada4cc4e3ad942575computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34520
the chainentry 34520
- sealed to the entry before
- 1fc3ea1881c01d473b8bd25a69ee11a4bed2c0ffac6e5e262f3f6e68e34968eb
- this leaf
- dfaf2d79d932251fb2fcba9024812a661c3b3a3c3abe3c6cc771e188de4d1ade
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- qreDIr33yH4qHxnQjU9acYnKfOslcTKCYneumb3dVRhx2nh7w2UHhSGsmOudatzui211h0ueikU/21HQHAJLAA==