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
- b23c7f5183f3a232d8a83680d33c54a9b7a27930ed88d4871fa1adccd5141e4a
- request
- 6e33623a706c05ca09098eb9ad1322a8284f214bac71c5da42764065c4301b2e
- transaction
- 50724355321faa354ef135fbd09c58fc3e82116a9185f4a1980b32539cb8e515computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 67093
the chainentry 67093
- sealed to the entry before
- 4dfbd5ca75bf1f4b81fb66749c875fabd30c1a3ebea1d75c9428d7f49a3eb993
- this leaf
- a8fd9df7b9218628cc1ed95516303e21bbaf5d2b9b4cbe9a55c5ec6ba8019b46
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- CumOd4KLFYcxHzePQ16BzboKHbpyolnJiK7m7XbkVit93NG46nOnTEy6a09UL737umOkYWUVS3kaRhLBAjjWAg==