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
- 434fc6bfcd5be641b973d90adbf0c27bd4e85b8fd6fa217c9d8f5647899519c3
- request
- f8a56a352d2e48ffa79ac605a92271199cdd3e7b12bba84d4309ec09f63d63ad
- transaction
- d13cbce5c5e35cbcb0551c1756496c5e3f3d280b14d067a43194b2d276fed842computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 58908
the chainentry 58908
- sealed to the entry before
- d073d145d55ca049a3351dfa3c2ca627382528c659e1cd2e41a05ebf26ed1b05
- this leaf
- fb4a6711a43216780a501c2f0d070fc0fce74ed191fe27b59ebc2230b0343e5f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Xdpyzx6NNH/F4smGqpGR7Dcs4Zb4uHZt7cbwVJd6lx1vqfBwEShTFX7fWc4DrE7Rn5nXVCNj7sjACyitL0LQAQ==