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
- a541ab450ece342b74472ef30386f0c71e663b26c83fbe94b32702ec1a002043
- request
- 56e580e761e78eb67e5c329dc588e9ea61b0b3b843a9955ec7180ded7332192c
- transaction
- 97ea2f3b615afd5ba99b7bbaa0294e2394ff3336e0675b6da79ce15a3af6afffcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 67049
the chainentry 67049
- sealed to the entry before
- 792f90d2ef4e547361511c78a8c62a9e29e88619f66569ce74064146489b1946
- this leaf
- 2456996cd32e392c39d97b3ef1c83826b0d4173e4bf8cb83b7ca968d0c64d7c9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- UwNJoD3r9vFXjeB23nRbUjfP42to4ADoJF8ZGGmtlJHGAUl07R5uisVs6nT0LlvgxB4nSOS2dzqfkuHABoLMDw==