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
- 2960fa0a12896ae76a7e814ceedf2b7cd1ec0e76ea8b28d01e499c10617662f0
- request
- da54be6736763cee43a7821e1e8673c8060de3a2b795979967c55d48820167ef
- transaction
- ca4ae430c5fc9943e09dbc45bf77433f5e98ebdf9bfc398df201f6dd3d53aefecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11828
the chainentry 11828
- sealed to the entry before
- f37642909c326a2211b4aa1458abd3637025167401d6826d159a3bc15fb56374
- this leaf
- 0f46ea4ddac8665c0058d856a97befd62136fffc30a19540d2a54d206f04a748
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- iIFN/kQqGNJ4t5khPhCZdSW0DwLsaHA5QHTmR6GsRVE86gtlTh3fJTC5x3gJz4nE8qnqnQOQvZrNE9m8tQ8ZBw==