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
- f99dafc0d9f062cc9ee032109253cd421a38653ecaee2706f5ee92fefe5380d9
- request
- adec9657c3e8abf10b12fce5255ca308a3199eda2c853a6f554004e00cc4457a
- transaction
- ca3470d5f136a18c5850f4a43c758a5f6df13ef5e575fd09e878cfbdf5e41ebccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66452
the chainentry 66452
- sealed to the entry before
- a55c44c60a31e391827660e70645626597b1913844fc62e3594c765e5e8059fd
- this leaf
- f1bf703ce4b44cdb8b7663d4e6a1df12b1406345d693233bedef7bfd9acf28bd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- kdYSUvCeKfTz/8QJJOiIphPa5QtY3MCLC3bKEXvljdyFizta9uMiUN/Tjl9HbMC7E7Qib3/fkf7sCkTsapiHBQ==