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
- 13b164d66da627b7bd93fee89c888fec1f89c6a6d90e18f8a9f1d459f9d396bd
- request
- ec77e5207614bc55a74b701a5c7e2e175bade0c173a6709060890c020f726509
- transaction
- 3bc442fdb98cc06efa600ac598c569f6a84a9d6af0097c3b2cf7b1f9a9d3d162computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 24500
the chainentry 24500
- sealed to the entry before
- 045c097ba3188c32c3c015400b17d77e9f36954fc06a0e31370143b0cd739928
- this leaf
- 2dd373aa1177d50e0c3e2db99d70eda97fb5db8f60efe4930fbc8c225b2c35a3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- OGv7zm0Xi/CBn/Km59ilsZnCmoz9qiuswSxg0f+N3rNseYme/siOrI3B1SgW3PzSvYZbLD36MT4KkNXamiy8BA==