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
- 8f373996569defab2c97fb469d068bbb39d1821b3d5bee7d869d461c4c43d3be
- request
- e51fc308657ea74e8ff50480592a99b7e2006761911e3ca59990aabe601398c1
- transaction
- 96b841c72cd1f7ac48cf4b3567f8d87ffe75da642562eaf2b2344e24a97e42d5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1735
the chainentry 1735
- sealed to the entry before
- 40e893328cdc8d48df9699a3506b3bf52caba693045989fbd8d52aaab5114741
- this leaf
- 98beb52d3d4b0d9dd45b5f548a70f0af93d3b21a47bcaf63f661b6c52d240564
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /2UmEYOV8GgYF9iG11e97lgiBbE5HjfiZ7uKJ2tM0wkDlgcf4r7fAKFoBEnYHOhNbTlK+ksh3ebAiFtfnHkTDg==