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
- f349fd2ffb50d1ad57f4e1f56205159630bbd31de4d224326302fd904c7c94a5
- request
- e9a8ce08a1a59bb16748b7f073072636b96161ba042e03b12903bda6fdc39434
- transaction
- be7f278604f0475786401efbca36a77143bcf065a6401339fc2511abee1a657fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62661
the chainentry 62661
- sealed to the entry before
- 2ee98c0eb71cd0ef3eba49afff9325c7455259fc470fb35eff9ac18289b3bb1c
- this leaf
- f77a41f80950718015487529294ef7f9e9d5858532ee59acde12542258b4df40
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Krpb84eMNTD+Q3jpi3mC40t8p14rY4ePUzLHjjQkdInwmnmPTBITTAO5QvYHnbPrI/5PcwP1Xe5ymHwuFVr7BQ==