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
- 02f8d022d6e9643a4c2be05b456d7036a38025d62d8a16f3d59797ba75fd8fe7
- request
- 6ce7acec07c910c6ac04613211ecd8d26856b062eab111e3a3eaa75e7d968932
- transaction
- 6d12fe111e0d191a874822791eec14cef24c27a4ac612b7f77dd2e2a4f636effcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 4525
the chainentry 4525
- sealed to the entry before
- f0d7e0af43566ac2fd5544101e9ecb700d80c98a4fc794ddd90993031abae820
- this leaf
- dfdc70366d622dd49ff0b2bb4531fa9921c56af04d8e832b7b12f53e7e0e2f1c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- zdPVwk7jZSj6LABA4q/D3YeDrnFUR/64YzixIIwszBXWAajd6aow/nQQtN+XuLCUqF03orr/LOzL9VksD8CvAg==