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
- 25beccba683b6659bfb94ef476d32d2e27cf22839cf6f5a40f821134a703ec20
- request
- 78f19f4c07e5ce7bdff4f4cc5f58218c8d2b9829ce3a095028e298de7b663491
- transaction
- 39545ed1620ca742776df7f40777c89876d05284bedcb98603cc29edce87d03bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65963
the chainentry 65963
- sealed to the entry before
- 97b78f8e4ad386c9f99a012f7f8bd67f3963f10172a7aaf3b136406c632ed3a9
- this leaf
- 7581e434f551b8fb8ab0755c78310a4996b8d3b67f9d595d169960d6bc229667
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- SQddX9vMHrhEI+G4PCuyZCymze/A2rw7ZsGaDZ+OTQz6raiQqQ6e56Y4zp7asODX1X3jhYJDqmjqgJt5V4PiDA==