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
- 54fb01b0a9283fc875ea63d23914f761a3affc41a096651f2d7519b0981094fc
- request
- 415cdb0e2fb5b8e48549af8ed10881381ffcdfeba2cbbb8faf5941844b30487e
- transaction
- 1054d52aad8de0ea3a9fdf03ee0006f5ff38fd6ddb05efacafbc944708fd452dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 24524
the chainentry 24524
- sealed to the entry before
- 0883dca3da93245d60db4d729979c07463d2c0586c4f2047ac31e79cc56f8054
- this leaf
- ec52b0917fcdcad85bacbd06fb6017ce5e55b2b29372494ff7d054e540019b0f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 8YA3qEQteiyEPja7QIb9ChKH6xtAgI5SCqkY5nrcN/haqRvzmVBU+ch90v3IfWN7L6AiDB7vefqnhpIVJFGkCQ==