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
- 20d1f2fab7c71a2e74342b07d1100d1181e773a2a52157a0bfdfcfb386fb43bd
- request
- 29bb43f1c0ed1b54c18f019b7b131b214fc9190e40eff95bc470548f69adda31
- transaction
- 9ec1581cfdfc0d77bfbd9614a57b9b5efbbb62e7c60244e237ffab3a77a844ffcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41082
the chainentry 41082
- sealed to the entry before
- 97363a639a2de283c6e68c98691a160b1e1301f25fa4ab27f91cfff379ecd66a
- this leaf
- 30988f9a439bbcfec733732a0f49d901f4695a163b69f0416dea8b371a2a48bb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- y2JLwaF53J7lGMrGi+027OvXEL4gmznYhncoYcuAi3oQ1QSwDl1jRdJv7rbMVRjs8A/lFKtUyutU18VNISLpBA==