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
- b55a06963cc1af6120deb3fc9074e41056830bded820590cad2c79cec8930d68
- request
- dd6631b38f6557243e27632f44cf888c2626ed912338f1f76fc37a923556527e
- transaction
- b8af11ad74cae679167bd73c7262b425581d31067a4decbad6bb8a86cbff2c42computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44027
the chainentry 44027
- sealed to the entry before
- 070bb6adf3988b56774511cee08d8198948a26b7b78496700ba59ebb8363718b
- this leaf
- 0e552a53ef3e866064603cedd95b8859e81118e9446033aa0a6071f50ffcab59
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3xkq3tQN3lGLdl2q86tYvg/4TdbJ9eHLU5g8DrlmJOwoRHbYiWSG6lVr5vFZwi8i4+pf+x4Aveb+RHHAv5Z2BA==