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
- 9194c14c820104a755d5850e7b4ab1ff970a07b6a3eb999e54bcfdb1ecd60110
- request
- 9b41787284a3316b10dd63220fc2a7db84f308a7c482a624babc683eeec1683d
- transaction
- 63466efcd69c26748169f59716ea500481aad106f24fa47b3499bc35e255d6a1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 18992
the chainentry 18992
- sealed to the entry before
- 4e5850a46b731ef2024a436861228b03968bd133fa200ce7417883f25fec4286
- this leaf
- cee13f4e4c1ea77fe34a6c33412f209005e8ed95935d586ac69c369eab3484b6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5d9+DANAOM2AZnr9z7iDa0QWgdnpW3fP+W1opXhA3hFcFuHvZPWIf3j4mRZEvJHNFMBY/gxDMapWa4nPQGG2Cg==