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
- a40d8abe3386a35755efaa48361344bb65351a3768a8536a535bc55d4837c11e
- request
- 76133528f88a934e0ce9bfefb4a5a466c66761cca99df3397eed043e84c303b8
- transaction
- c58b86c65d84c4008df5370876ad09747898c9dc374c267095cdd657a79dc665computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 551
the chainentry 551
- sealed to the entry before
- 531f927574e9ce25319dca6c9269a6d08bd8db761c86499813fd23934783917d
- this leaf
- 886ef0d94cae5d3163761ca3aeb4d0ff48c8f0d25d3ca4b79c4f1db7285007bc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- V3/Aje6+orHK6zCIzvez67FXYKueA6cisWjc6HzkwpURWQjnvZApqZiOc58oxM5pTHYA7pJoCi0e6+wmt1IFCw==