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
- 7363301dd581cfc03ee21eb67353486af2f53d679e90838e1dd3b23cb7624390
- request
- 32f69d63ad3f4d4a71450229f497d6f55c04b62e64fcfc2a2cbae5a468e1d12b
- transaction
- b91c4fb12d7fb69cf7b0889e7d53fc4f3507e43efac8c6b8e2ae1d22115c8b53computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 57759
the chainentry 57759
- sealed to the entry before
- 18c0fa7fe23f5c02a4435b25f8e42711b1cdb950e6e416707c314d4b448840ec
- this leaf
- 4b8f890e15c449299e4b7eb450015fa1a9d6b3f9c69325c3f61a55072cd03599
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- h08eDaEgONCTiJD6X+anxhi90DzURSB9tdfOJCsPVaPEMN4E9xo4bYjjZasMMyYFfzUNdb5Mqnoua7zcAz00DQ==