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
- 1a19175dffd97cec480b3f6b3097385eceaeb01eb8e4c5d2308db86adb84ca04
- request
- e0e357a947958ed4eabcbd74a630e99e1879f461f1fc5521459ada91018d0590
- transaction
- e568a1a2b5eb091497bfe4cc3bc733bee5d328e3c4006cc9a4605b485db4f749computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 14039
the chainentry 14039
- sealed to the entry before
- cd7f93ec00683193f4c895b5d36326950bf77df4c2ac00cc7121a8b1c8de6edc
- this leaf
- b786684a676fe06e9a32cd4d85b344629ddd5cf7d4cab98bdb2ad1b1d7603863
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LCo+k7i1DnP6FxiOVk0xU/5mqH9VWbuILdwvJGrE8/WI78nWTyXG8gVvIbNY6T0+AKUFeJl/CaIlSPNuwtQ3Bw==