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
- 1d148b544212febb22a4631efc58e92f71d47a6b2fe05218a3a3e3a6be525623
- request
- 6c6837a69f0e918d3f0d10ad25fbc56d54020eed48db7b7635a066d60c8a233b
- transaction
- dbde677fcb8a4ddf447ad76086a4a7d1bef0be109b9b8ad3ff3e7fc8442ff552computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64081
the chainentry 64081
- sealed to the entry before
- 3fbaa475eceb0e63c1cc31b1d776b829bdacde9c146d5119db57158424a6e3aa
- this leaf
- e4a108708285d054b8282c5b6214fa7d5b8763c6ea96fb1baac3a7f72bc949c9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- N8zI+3MFlch6QekfmRzRIMf6NjgReXRbfGJ4ouSLA4Bon5cePWGHnsOuJNwCkNC38Unl6z2AVrl/pyDRKrmFAw==