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
- 198b65159175ae006c3bf612d02351e7fbaec621678812c285ffa7cc87ebdf7b
- request
- 3eb099c8093c003b6e18e666eafc0b6604e6fe0322733accf47d16a21023a9e3
- transaction
- 74e4192098c6a3a795f5182c86a41a0863d9192c2449cb1a1fd2861fc3f27ceecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 53754
the chainentry 53754
- sealed to the entry before
- 1234033bb200036c5ae12e5f2fe31363a734983d837412df9391ec8ceca144f6
- this leaf
- 3a0b63dc5b1b9217f1c9a5d475a3f58a4e79048598d78fd28f38a103fa8d6fc5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- WmS8ZLzt4c4gJBwBaX46lAQkgQWmF1S6TJ3yY6a6I/+WGHCXq9TXYnddwu28HkEWehzsBk0uPcRYkm8V5UpjBA==