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
- 22e0f1caa781bd770b5be97fc0285c15c78cb4539dfdfe521977a48667ac7ff9
- request
- e53c5a9afc225843506726f696276c6aa5581b7be3a33668a7c962e73a2fd685
- transaction
- 7a0c1bd37dcf2675ec563cf4de3b2883aa89da5319ee184ba01f4e98b28f7951computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44018
the chainentry 44018
- sealed to the entry before
- 3ec5e7b344cc3ac7c58213ab9a9f7706002ae59c0f4bea9fd45e4f56eafacb47
- this leaf
- b7f54bcde0bd688801543954ac949fd160e3492481c51445df268021202780f6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- OA7KnDO20Q3gGJMrpvL1AjLhAOCHJIwcBb3uchCzpZ9AH9odaZ1BVZ4j4ttxT33cHThmRVhXSV3z8dwywAizAA==