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
- ceffd1e2c8acd0f10cb4801500c1190e3029d1c8867ea9a5ca4fda2f0d03ba99
- request
- f480a07396eaada0c6f6c3c50a6cf4597672c4666d686d2f00809dc70f53c89f
- transaction
- 38bd6935d3b3f0142277637a1c42f3cf9ce17b49c359ab105a29623136258334computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11697
the chainentry 11697
- sealed to the entry before
- 2bd41414fd64a5b5b0ec103a38078d7d17d656d56d8820bf07f075cabafa56b2
- this leaf
- 7ae18a17a15f76e983d954f7959b8491f7db473cf4a66c6f3ce1c1e0f4e07e87
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /Zf/CD/fOoTtg0OL9EFMHhckxPpmXFEmuGenCfccO9INKldQ45nV0j+NWuMQYzIcF4UZ9L5/Jw8a9JeyN5TfDQ==