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
- 20bae06540a81c3de41334486528f8fedbad47816470d497902feb78d000ead3
- request
- c7bbf9484011fef5e3d865665796c5ac4506b9ccbd816a86ec868410901bd29c
- transaction
- a912f6c56b98bb1b5accab7e4c63a8ddcac10004ad57fba52f1536bedf774e21computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 77016
the chainentry 77016
- sealed to the entry before
- 44c33dd66aa73513f259507c63913fb3903405319bdd60b41c3a6282b2af7702
- this leaf
- f4ac4cc383870bc1fc2ed19261021a5f84349b92d7e9d159a0ce0611311c0d4f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- kn3Rc7mOuzt7PE4K6mhLoBwax+PAYUe6Pvnh9xcW+ods8VcS+sshUMZnFEWKj8D4AF1H6fRsD+tkNRfNGEafDQ==