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
- dab6feb6904786992dd5fe6bd748a03e26ed38c5629d28ef1dc515cd3b0abcdc
- request
- 12453208b88231bfda446d233ce94625b579ddf55d231897c50d6c126a6cc37d
- transaction
- 502e1790bca7ec1d2d6ed105c26cc3523cf89859cd46bf5ffe8e9691a8cebd3dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64621
the chainentry 64621
- sealed to the entry before
- 5e491d4ae28561974b2082dae1f8263a06c3e051ced3549292d858bda0fab5bb
- this leaf
- a1c240f8dcf7d31ef8122056fae08d936475bf5643fa302bb49e1191b7c4042f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- B4NPf0wqIP+tIDbWMk9sa/+QB6aoSESLOifh8Lcr1Gs+EL2PC05Bq32QYSIQa3NK4aa33pqDHVcuNgtvGMTMAw==