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
- 843839eadefd353cb5a69e7704ace097cb59c207838318d856127f3ea3556841
- request
- 56bf4614efa06429fa53102a7ccf0874e32bbfc1259128a6f7ca814630d8a7c9
- transaction
- b5387bad6c7035a24b1caa0ec8fe973aac1ed366968786ddaa174b96727e74cecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 76722
the chainentry 76722
- sealed to the entry before
- 22cded2fd863b7ba57b17b5d2274a92b96d629a9631fc5422a40202d0fdf5638
- this leaf
- afdfc8a677aa6f072dd246e78d42dab275fd21243959a0107043ae52f579d3f6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DSyruPasFMck8jyw3+SHm3jYiezMu7bN86gXEvAg+ERpCCKDK0ZXbeeYcmgAnGzGP3RCvzkdEDX8MUYdnQ7gDQ==