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
- e09de3221d68460419adb6e20a5e692461cc122e2e9e9066809fe7c04010a26b
- request
- ba38c62e2870192f1cb3d5cbae8145963c7a1a8bdee25057c067485d9d6a533f
- transaction
- 93d5502575cf9874acd0fdc1ca2c0c301df797748e10f5619bff834681a2184dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69462
the chainentry 69462
- sealed to the entry before
- 3d51037264ba06456fb530ba0441f70884b7b87c31e27f7588b15d9cd295ed2e
- this leaf
- 587411d1e8e576097934a493b3150136199ed1dd973354f925fe3684a02b791a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Cgqka+3PaOSgEgnKy4GOCLCYtz6R4r5lpVum/QgDfhs5mo8W113+EiHIFn8dpMFHPSH2Hf1PXmwrYo5+bWg3Ag==