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
- 1e9a8adde83f46f04b9e650183951314b4795c739a5c64f8c320a7e714feca14
- request
- e1438c52b8ab0beaaf6e42e26625408d8139c53570c43b00262ca544878d70b8
- transaction
- 2eb409d9b92258b915382522a926503ab835f92b37448fb27e488699cc70ee6acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 57363
the chainentry 57363
- sealed to the entry before
- 7c3500122031d468f43c0a4055d3675f6d053f5c4ad664d8d95dc66974d8a61f
- this leaf
- a860cf3798f3500d701517f1e267ec8ad05842e3a58b9261db07c5dcabf081b7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 8+VzWE5udjDS+MxsK/ZlL+EVhnC8NlJSzsxX5HLAxHFduIzXAGnv+LK2rimzbb7jP5BC9jlDJ4T69G4b5EWyAQ==