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
- f3ce647ad328a6f9ca1d6c84aa15c3cd560351646aba17946de4e088c22880c5
- request
- 6a4d79f9c32c26057adc976407cb1dc4a514341379bcf1ed8cef7cd8a6ff512c
- transaction
- 15b08e679860cb6ce05ca7d75a8a13436bcb14ef43d6e274ee78663da8f7f03dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35050
the chainentry 35050
- sealed to the entry before
- b96fb0f124b94348dcc7d58abd26693a9c5c5519858b6ded34b01b8ffae22ac0
- this leaf
- 7ef412f18a777b7acf0ed7c8d1dcf8031b739c9a87e9e2dfacd04dbd3e6155bb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- GB+yKzm1ozIMfJEt8JvEzJ6KkKN0+oOSfewiPHuF6L0sFh0ZEDQPf7pQjIiR7XigcYCkn7tNR4gTBophFzzTAw==