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
- 0f80a3ea78d23cfa2a9b901bfd86b19a94a5d99133c36ad5c7e4e90b270cea1e
- request
- 44a8f132dc1fa24c5efb6b87324bb2e8918ce45676a6f7f3085064068b083930
- transaction
- 42818f12d5ff9d260c9db2451b51c6b736044394368a03f25267fb9e55ebbf71computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68690
the chainentry 68690
- sealed to the entry before
- a27290f48139e38b9d47c9d2c3e3eded538261a348f63aff60c075fb169e3586
- this leaf
- c6ef9bc24667a3164713bf779399452da25a176f8dd0bba85786dea0f080396d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- y0ZIuSPW0fXpnkX99Ti9kbZ5b1YmyekLVPSt26Y54y4dtcNZ4vCiqFWX28atvT3Y3m5yZEKj5aNFfRaisL28CA==