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
- 3ca49ccf8013d17ff1090b4ba44922a84f477af7d0fdaa1b9ef9c7a29eb4e185
- request
- bb395be882c8aaf869484f77e4127da5425050626ebba113d2f9eeca5b4712c5
- transaction
- 92b1cc3872090fc00f52f87f7abe5443ab98f34b3d3118d37ce0f1518b512c65computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 9225
the chainentry 9225
- sealed to the entry before
- 9ef89aa19d7e2c67b0b9302aacb24e33014d7b0b38679a5694f45882d03e6c02
- this leaf
- 2e8422f180fd08c95aaeedd12e5e8f672444acbea551af743c194a49c4f82174
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- rF/OZU5hZCHjH+N5YQ5OOckeTO+NbIbOfuA7HaQo65I4ut57FzhomO5IWRX0CLzEnpzcnis7qR2pZ1uXloxCBQ==