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
- f2ca6db81d9461b645f7972901e818b39c134aa38553a45fa1b36ba2b42f1302
- request
- b2f7b764fcf069c18f67653f9fa60793613d27defadbbddbe7d16f9bbabf12ae
- transaction
- a2d2cb1e716fbe51020eb89b30af18dbebb01c5358e979e173e139bdc37f0ccecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62757
the chainentry 62757
- sealed to the entry before
- 3f8a21277a78ab0df9eae7e6c9e793deb04943b577ea59cb5fb2a298de239484
- this leaf
- f58f59b1813aac84ae837481afa8fdba7509a43d40433dc0ae00674b4cf803c6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- juB0oNWX6N7dKm1B3HCHdX6JCdaJrF2ji5QkD3OBbI16Eu4vhjW9fG+tVYgBJ3bVY8w7gKkJ+fn8/7FPKKRmAg==