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
- 772cd6c79660536a716f2d0708f4f76cc24ddd278d8e4dedfc899407fd11d266
- request
- c1e6424e36d6a3e666b8ca8c8aad159dc5de9dbbee461abe5d240583ded94460
- transaction
- 1be7278ab0bf38abed0944a9038f803f21069004df17ebed653e026044206613computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 24161
the chainentry 24161
- sealed to the entry before
- 3aefd45e3da7838eb0d8e5d82a94129f9668b2c14ceb80ca5acb864eef27be02
- this leaf
- 29a434c513de7d853759b7df09ca962750683ac2f1155b56c41c06b00f379292
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 11/TSc8XQGzQPYVvwPL1F6jHYO7HJuoB3H8hyCobWQRvphkYApr8O/ppbMjaw0R3F9qX3Sg6pXwzQgRot+BtBg==