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
- bcde4dcb813f4dc22ee78d8d27b5bf59dff75a12db08be5bf39083fa0fc3b3d0
- request
- 25ff7378179a4777925892488557b405ddbd86347e77c2149d81903c39f7885b
- transaction
- 38d5f423d6f640e93903b4dafe3ea4eb2cfe86e857ad041ee0dd4df8455ec0c6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17400
the chainentry 17400
- sealed to the entry before
- aeb9dbe1a915f84841675bd49bdfb0a6017e83540209267446e1cc145b1fcbb6
- this leaf
- 6c4316319d2a00866d38bc6181176b97bdbfe4be1636d9f83cef92c9efe41eb2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4Ntae25OwwuQ6zpCc9eRjqokHfVCt+IBry969F5URM13q9hioXGH0pX97pdNzjfFOZ4WiRmp7f5u8OuMkDJiCA==