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
- f8ff1bb939f7a4cfd1a6b0e8701aaa8deee38bcfed07e0f51fea9ef77da379e8
- request
- f76ae8432e6639efedd73fcbf701e9214241782793d102c364021ee9048fe4db
- transaction
- 8ba287f8d70c5fd294adad9eb05e1cf431cd54817613e0f41ebef693196fe044computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 9133
the chainentry 9133
- sealed to the entry before
- 2366e9343554bc05ae3a58b1362b4846723473975285fe705d3fec17a588b677
- this leaf
- a2e85badeb709e1a0913ef9fb6392f3af3c0931d079da8bea6ceb3e81ec13f0d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- CyxXILc/DHC+R16rKkmXNY+B+ApL7kKwbzmkmHA5CAIPfsj9/dZ96kTwNWm9qryNEBdBvFBdPWWVTcPRIh9XAg==