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
- 33fbfb1bd6369875f88d5a2b382fd3d7ea7f6017b478da2a95ca31379d135a41
- request
- 812cfefc5850ffd0a96f4415a7d4ae69eaef0ebc59ea721ece1cd9b6c6d2df2e
- transaction
- 2d41f7771c51dd86453719f24495faa6b2f853f57e3e20ded87549ef107dd698computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 53515
the chainentry 53515
- sealed to the entry before
- 5cc5d82536fb4af2062af75dce35fa402f04b17210e405cbaeec4db1cd691537
- this leaf
- 0b4614f1691baded6cb64abf15c70aa24c88e372df54734c071dd2d13bec4485
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- WXJsoEauSrJ3q67odWhe7z5P78x6wGyJFBzvP8T6/NWub+MsvnuSI8DqorlomOOgZPnfcCXPAS7Ct4Qs0sXMDA==