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
- e2644e344ee45adee6d4fa0705c74f1a9510c60a54561a2013e5acbaad878776
- request
- dc140e05c4a13f7ea5bf2631884c4c2f4a49d04915694a9355c8a30ba951e262
- transaction
- a185e25c7b9b341ca1219268c9ba6783dd95634c94e485128f8b3a308d0d09facomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20782
the chainentry 20782
- sealed to the entry before
- 134572a4621a7701c89b56f9fcecfbd28548dc212f8e4ca3e391d53e5ea42fbb
- this leaf
- b8214044a40045344e0a9fa62b03a6fa3dcc9f2662799895e3ba5437551bcee8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- z+uuY+brEvuA6MOqlbweUKkasaF+9kOtoRcmcvJnkZ+0muDTWtfYlGNgMIaomEMr8lMYykYoUhylEj5RrYhHDA==