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
- e82638025af5157bd11f0b4bc33f1ee847b937eb972f0015dcbf4ac0e0a6491b
- request
- 18ee57de70fa3637d4febc3993d1294557d1a61d0a978f33377eac78ebaec8f9
- transaction
- 4fb9c2148b9c94d6b09efec9c1b11ab286027b8532e9650fce2ecee13df8a79ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 49290
the chainentry 49290
- sealed to the entry before
- ad1f47ea416b7a042aa3e6cf7235e6046fc68b845e92ecec0a9dcaa527ef8292
- this leaf
- 71ecd73173851f5b31371c36b01f1d86faf70f4e7893d4bdf6a9ec2ef788416f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- rE27kK4jO1vUwLATFcK71v7CeZWSIyp2Tgbgm+73ZCNxVx6oBmKTiXNkBVZSU2Tvng4+qHLtNRwv6xTf6CxwDg==