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
- 13e0ff4236b0ef48762ba9906217eae5bc1cdf20734c542c420ec650790d2226
- request
- d1a73b62774450ac20545b2ffdd3e5e0506faf66daf996b12b0bc3c20b0d1dfb
- transaction
- b7a20539c0744741419d6f699983f022eefaf460a951c5dd6a7a7577e0cc1e7ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32502
the chainentry 32502
- sealed to the entry before
- 1ecd47a8b7c6d8bbce384e9decc5db31e66c9dc7474cf78fc81ca30e0115d815
- this leaf
- a1815c79ae6cb2272ff7f41fc9ec586bdf69782692e67b05e39a6ce9470da566
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- BMklR/QwwrXYm8NJVTkNF6ighP81CJmDq45FI8upeBN0sYGHOmk8+cng5t8+5cgYlTOyxTQpm/TPeazJx4Y+DQ==