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
- ee86ab4b352e7d1bdf9f3b4f53fb38b3f016e25f13291f2fa0c2e8ad0b382efb
- request
- 953218517b0178c8de1a6ba5a85bf1bb520eb9d3dbe8b9d679a96fb029cc76bf
- transaction
- 385b7783ab8f87a80e48da36e48a72218ed159e9b3c6e4d9ee62e39f53b4a9eacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40776
the chainentry 40776
- sealed to the entry before
- daae151fc7abdeeee2f3f1761ac0c952ae9259403429d76d6261d5771b899cac
- this leaf
- 7567ef4fffcadbb086c03f6aed539adb4ccb0ab104007ca9880b1429b195a5df
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Td5bpvvfvZHyD4btLI1FH7R3MaC55aoJu39CaQiMkOTe41D7k7rD0agZKnDzojGfjKQhP0Qq33vKmj21YyoyAA==