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
- 4626ec2fb9b35c9b04461536549db9c60d4748b3d671b3b3788f4cabb2493638
- request
- 1110e0cf7ed918678f0b6feccd5c5fe01c06160fefe06f42842f73af06c2eb1d
- transaction
- 41b23243339fd2cdee833d98cbf158ca912cc671032efe8426630d7b57e3c33bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28369
the chainentry 28369
- sealed to the entry before
- 7b83fbba6454da10f608d742ca3f491dabcd941700a62392f1af16eb8c4e48df
- this leaf
- d4de8a8cdb98d73a937b7a869775ff78b749c51ee47729c949346e2330e129c5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- cgQ4UFkrBMzO8B5SU1dbRcqXD2dgv4O2V5ARnbPo92UwtbQgrSnPmkoQ1grmGur8l6ybcRgv7EWk+wznIZg8Cg==