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
- 848a0f1bf7032d7d1a36fca75b196ab24e3e68d549a4bdfbe699714f9f6399ec
- request
- 96bd035eb3187fbcd7525c20054594ef683465eb3e77795e7c7038c6d522298f
- transaction
- 7abd92d0f299bf621038379dba2681f05e20fdef1316020103596510f7c53f08computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 58071
the chainentry 58071
- sealed to the entry before
- 490d97882f358a30643df2cb9920533b93f9ce145fc080fe147b906b5ccbb202
- this leaf
- 845ac249394580d7e86989a73b170eaa2402f9c524322f663ea5d52db2c38a38
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4tkz3THSwX2FSMSXstpbKcnoIWLBY8NgUjwI0Yn+4NMVHiAJpU8CX3qMM4nvC7zg41+U5doROsx9tTXKXLCjCA==