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
- f483b99d465600e05ec13b6838d14e4df2e3c6e852e8561d57c6323c90b74f5d
- request
- ea54563e12790a9806ca4e22be72f55207b01ecbf226e86794d1c4ee8819afc7
- transaction
- 6fe9e886f6f75a74223ea1ed577c8309e7e0ecc16465be596f9757dc9bde334fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45609
the chainentry 45609
- sealed to the entry before
- f47a5abf86f8f6a5e14a19dcd190af56988bc1b4c80ffee495846b5ae65f5b16
- this leaf
- b0ddee50588602d7b6dba54053005d557457782580be5e2ecfbd6b7b2326c251
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- w8sdFkrdymc/Fa3UZsl6GDDi4678Y1FLHxZJG3RgSnqNYT0mJhAJm3REbWsqSm+y+qPfewx74BaNiC/lCSJiDQ==