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
- 5fe54ddf190d74ac5fcf203241e1c8cb61febc86cbf9c3ebb291d0de71052842
- request
- f2f0dceb16e47282862ff14c4ec53e3b0a9a3525d6513d650de20194b3537baa
- transaction
- ee12d2819debd1010b63fc647484c6b1eac2834c03a7f139e14d5c7eb925cc3dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52567
the chainentry 52567
- sealed to the entry before
- 0be1c194d8df7df8417488d16a3ac7ce70bdbaed0be5fedefb9e95a4e583e47d
- this leaf
- 651ac0714967c5d8690cfa7a13df56c981071ae8193ffc81605c50c4f4ccc463
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- aZYvCQ6wX94e9TNytxIhUYN18vy+QmzcFh8Rkyr1gnjwF/XXdDFN4+bH1vAIjCFpTstb6DDb+vFEp1SNZAQQBQ==