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
- c9f9751db62a0c1a6f6a1f7591ff63cacc1cfa45f6c86965f207b4c419a021a2
- request
- 7ebac063d4f76c7749dd4afbf7f3e22dcbba4083a3f067165374067babcb2a52
- transaction
- 7cc1201514049d74a71ce88ebbd567d67d7cb49411da986838140d5bd7268142computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75142
the chainentry 75142
- sealed to the entry before
- 1da8617d15830fc72daf212c9b109bb020d23c3cd01d42a772a47d8f15f0f909
- this leaf
- 8bf3d194255770091f71cd1bd17a774dd2a2e2f32e55162f3c84f3da0ed033f6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Hd+kuLrWhI1bQdZFTvu8S7kn4Ra/teeUxaoGCZQ6XQKcKvKEAW3PFMh8oeKWofnulRe3o+M8TdkO7ih5AXDuAg==