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
- 86d41188ee335916a787e29bce2fd2ffc47ef1d948c099b0158200a3f2d4d37b
- request
- 6428558c840c3147241ba954e1a457132c822facaee4fc4bb9813ea80c278134
- transaction
- 16bbe1e5a0df7c33afc808833ea778ea8ce33fef74c2562d505ecc3b4fb05c5ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 38185
the chainentry 38185
- sealed to the entry before
- 42c77e355a18c30695832534c86813d4f0b72dbbfae0c81f63ac29a0ba6f11be
- this leaf
- 5dd3a8f05cb3a28eaaa1ecc74eb9f05fad26a7d8fb2fedd974f09c44dc11c271
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- InQIdLkMzEzVYEGssPpS/aqZAKvIlBsAj6On/XovkDJWE5S6C6HOQskwg2gj8XvMB+6MLuj1Ve7J+IcACCVRAQ==