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
- f379ca77d3b9427be83f8962afa56046784e7cd137e41330e1918faeed854d01
- request
- 757718f40b2f6e1006fe7785f734963dbf7140ddef1fd225b74b028c00463c2b
- transaction
- d5f938ec4e890c00e9fc0bb51709afc7c3f4da8a610de9bca250af305ae1824fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10008
the chainentry 10008
- sealed to the entry before
- f3f80604e2b429fbe39a4cbc3fa3b8eff5686b95f49af96e1720bba3afaf2f83
- this leaf
- 112c9d9d8ce35fa36dfad6694eadb34e25b73752266408e9b693495a55e3355a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- jgtNnMwJQRYTCC1e5HFJDHnqh7hmbiD46nD1rOtVsFsLQIcaUM5nPTY1nEsOdrL1D5a4qbI+3xibjs1apjPeDg==