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
- 547e5fc715c2437094ddfd084ec5664ad5ecf0bc7f1620ec25ad7ff0264e83d6
- request
- 3a9d006a625594d569c50ef2c9ed3b4cbfb6e9992880a8251ce48bb71697241f
- transaction
- e861c3fc1b9447a749349965a51d52032e46d4dc7712a677f64fd7069cbe678ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41478
the chainentry 41478
- sealed to the entry before
- 238586617bd46651eb26f152d7bc447b8578961d687137ff59e8462cb9cb56f2
- this leaf
- d8df8e9b516378f89e22c6d12b77cbe58581e4bfb28d87bf8f31632de73216f8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- m8BY31ZJKBPxIJSyfOZO/ALPq2+UxYDAijJN/UVw1QcvoseT+owwbEn9FvHMpDVuj87bAOQuGyx45t7/qGdiDg==