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
- d2e8eea7be4469f336ccffa8f5e68ac3e46de3bcd7b58f3093d93de8faa8798c
- request
- f9f621b986bc5e7a6f9fb575f5013e6dc38d35a98609d40ef78056857f234832
- transaction
- 0dd6a81e472b8a162cd7b97dbba1dfbbe3f5925c4c6d14a2b0527c748b7095d9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35044
the chainentry 35044
- sealed to the entry before
- 5e1a470bc928857e2b21e40664e6420b334d6a08730043328c9f3d7bea34569a
- this leaf
- 4f645c588c288511f7aecb94e7d133f08f5ea5954be710a5faf2bc7a8ddeddd1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- jd7MiVOUgnE/FZ1L+168ADMVM1bJoX83+0Q103rWX/fxWlwkSzgYlizZSOU/eUTFlujbBMrFAXPzvzCDj7pkDQ==