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
- 441d6d662eef5a09a4e854668c0cb77106b4fa40eacfd1195260f18efbb0daeb
- request
- 5adb54c317de382765309dd82230cea55c7e0df2505efcdaa043951c37057a65
- transaction
- b769ed2ff2e64c1f412509f6113e51b2344851010baf6f4fa224b1ba1455aa9ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36574
the chainentry 36574
- sealed to the entry before
- 0a3c7aba6ecca50f275dd698dfa1239be96fbdb29ce369bf847c25461d09491a
- this leaf
- 7f4f5be74ebc7f611e78b2cf81c89f9bb2f0dcd3bf91a43db73202ea4fee668a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Al7Xy8QOTkPPmbGLpXdZn2Vjb2/1cY/3m3PHuiyfcEygHdg9DDqbVISji71xDfX+W7V2FYfn8MSeGCqvADkbDg==