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
- 5b3e1f709cf81023e37a56523c432e659d7d08e30600fd38021f72b2348e5df6
- request
- c6bfdb218ae82bea0d7d95a6685d3be90b5bb734c36b097981e19dbac7c1b764
- transaction
- b28856c744183efc63062e76b34af9b9c82067084d70f859f03b7531a09c5dc2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70212
the chainentry 70212
- sealed to the entry before
- 350d9b8c74c39095c44384dcda121ae927d1fda8fe4c8e26ce39ef289e078bb4
- this leaf
- 22dc0ccadc69aa84c4fcb6de653986881e750f6615211896da822d7c1bfe8cd2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- vmac/ReEAa45Wg8ZQZcj0Pro8ODBte42+0xk9nVTHBRsCPnZcCO7jYH7lF/8uXXMlL1KoYi+f6RdObmfVj3XCg==