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
- 3ff7029b47cedb037f96f7c2e532d09329f7ebf49c343bc02558948a08104e0e
- request
- 5ef7424a2fc1112f833eba1fd415524004afdd6b8dbb06b137a51674864c34eb
- transaction
- 3579fff97a238a0ac561e978f47398e1b30663725739b8f8770db700a3c8baa4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30411
the chainentry 30411
- sealed to the entry before
- 2b5d3a027eefb14ebb032e2e635b3a3b6423bb54a66bf405ba25aa2d2ca99b41
- this leaf
- e94832e6e36563c690e8518ab52e05f74fd2ee2719b741a96234acaac052a5c9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- tdt2p9IrlXf7lpealUOV1i9J4bfYca1R6poypEoXz2ROazeZsYr/DZS9R6N0L2idhLwXYNRmoEO+dMkrgUQlBQ==