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
- 101fbba5ab405576931b169237eca432c0de074b64129e32ecec49d9cf1734dc
- request
- 022bc2dcd0a8979642e854aa20207e8322e8f874878de7496adc37ba802152f9
- transaction
- b4cd34d2ee7dfe92e3a0245b72e5383799d7a43d64d02e2cf7e3644bf3454bd0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 6419
the chainentry 6419
- sealed to the entry before
- b7098ed18a52193a214d70120b7db663a7aab3f6e3b601e2c44c812254f67a57
- this leaf
- 2c88ac47a2d9ce3661d72c07d93a92cd86a77254f78ef9fa7035fbdc2d35e017
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- RZLOq2TzdwD6lsuucUbyP2qRzEkgOdaFioITLm5b4zDXX4+IPbU0Sd7d3y7+FUEpHl9fMccCYjMjAA616DaHBQ==