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
- 06d1a9a2e229f96165618aad618de6bc7268f88782203a03734ebb5ec74436be
- request
- b460546d1c8273ad3d1f352832d82a1763e9bcabd1d70dc2c1870bd62aa746f4
- transaction
- 3af51f39ec3086e46da198ad8e00c70ed9fec0dc0a5d26be6974989dbcb870dfcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34131
the chainentry 34131
- sealed to the entry before
- b364fdfbfde1a12b8cac3baa59ee6ce1892e456fcdcbc50437c0b01bdfdf5e6e
- this leaf
- 52e7b90d9e09f989270a97d360aeb6a54e31d35eae0afab81986c607cf9a8487
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 87EDHSVc6Q4/JmxKKSylmP1gmDQbpCTuiKSYdaD48mt53ddRcKDhu+d0Ux+Wy2VSP3ds5kMNLgTSrGp0F9c1Bg==