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
- 3dc8065ff99986c25c111443b6a794220a5c6c30f2f40a0f873a6878ff411993
- request
- fbd3130c5f6eb60b15be4f345e7179025ca809b6e710e8aa25d7dbe5c113c751
- transaction
- 110671ec69844e134205cf22c4887494e7ed07bd9a2cae6eef59d848704e0b62computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48093
the chainentry 48093
- sealed to the entry before
- eb3dc5be6bcbf95fec819157c529f50d4a9de74a8d56bb95aae4013fbef5ef30
- this leaf
- e78d54eb3f9a6f190eb68b9f835fb7005d1aea945b50f0e91fa476416346b119
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- l2PhOu2ugSfdcyWoVTeliz4qcCuvurYYfaBfW+rQa/L0hUm0WLriLP1rYc36BUK/XatN9keadaj17swyGsEzDA==