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
- 5abb1f3ec55694aee5162287f4a104ce995f3fb526a684f1f29a582ba659f90d
- request
- 95d842e778f863ab347a2d510aad116e2a717ce2167b7791c2a527e2498554ce
- transaction
- 2bc708500bc1c46965b2209b4b0c8c05826909cbe053056b9d21f2a2a3b141c6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69614
the chainentry 69614
- sealed to the entry before
- 40c7d46ca0bf43b40eb02111882a1e90d01e3b1631200d3899c886256bbf339d
- this leaf
- 7e5a4392c5017bd59a8d3d748e036384a5cc083a26d11493063f92845aa4af28
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- qkyyFEXd27le/Jm0Qb0SAkgEQMzWr0+5EzZlmitas1NaNiaeyJdkfaqVDJYVEBrwmPdFpemb+nRCzMwuIIKPAw==