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
- ca1b5d1c0547c73bb338844ee30001a8865590d336bde5c6bde37eb99483e24d
- request
- a378b50541b3cbc6e8a34c5f03f758228968b12094cad257d68bb200eafdb3d6
- transaction
- d8849a1268cc82575de6c3117364a22d83c7ec43c470722ce2906f2048799fa5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64025
the chainentry 64025
- sealed to the entry before
- df12e22ed035fcda8cdbe239a09b84339868301a4f67e985ee3983a655069154
- this leaf
- 1755cad11c0aa5b792e561509064b55b4c78e00f94d360339a5b44d8d5d42d9d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- sPMEmIOqfTT+h+n5Yhw/m4gnZQDFhqFBXIb0gYvFlPBTYQ6uyaf1J3wx7hvcGQyJZnOV2YaTZA/4da88an6bCw==