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
- 4896cc64515b19e430d904e5b468e33cc70a71f7fda4dcd12cf281ce36c0bec4
- request
- 63768be81de2eb284aefabddde604e6a09b3930e2dd6cde4de37e583a722d4e1
- transaction
- 70e0c2a004aeb6796b21a940956aa7a59703dd79082f26d3b418242f3af9ed49computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 58242
the chainentry 58242
- sealed to the entry before
- 60fcbf50bc33ee04af816f77c9d8713d7e7365b8ca50e01baa3a719734511ce6
- this leaf
- 19eb746be0c58ef269ef04632a487b5f1d39fc2f2e2fd4561fdb5743f46a75c7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- NCS0oc17GF9yT0FvVY37QxpcP3/32njr6A6qVKMaGkoAFyRTOn44aHJrd+3LLm/UKn9jAsuaZiopgW1j4FTECA==