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
- 8f3b43ccca7520acb29df7ba1c9a54b5463a3e3679d2c0ace972851abd0d207f
- request
- 51629f66d215263dd537b6cd0ce353208090021fc41c7f5f0ae623cab23e34b1
- transaction
- 537f13baed0a9c32d49047785eb10e680ee6f2bc648eca92a5737069e366ce5ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 6821
the chainentry 6821
- sealed to the entry before
- a19b8ca415e75523e6a30014bf31ea3362b47c80bd08a3fa0c9735b26b797d56
- this leaf
- f9dfc2c2b92d56093e10e9b063ee856b348545af0e60a7d254b427ff8c691ed1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- L6T8/uvbO/enMqECv1kI3gkKW8aiKvQcXGxTYBozZn3M/2aM54CbL+gxi6KYmBhd3DmAtB1nwFbx94iywCXfAQ==