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
- beefa1b4cd5200dbcbc13d94a97a398f872fa97e91a215bad26a2253f0af7220
- request
- 41e61ef6c1b661237f2444c95c72852a798829117f67c3ce31a839db5aa7016f
- transaction
- 3751cd9bea636e74026487976bca030602bf90d8f572ad752cac43f3de834a1bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28347
the chainentry 28347
- sealed to the entry before
- fdd9f8da73e2e9d558d0b470d78c54eac40c63a0939e5cfa240c75cbfcaf2075
- this leaf
- 4f0aa42796db0850d2018810a2b32f5134040b7b34ef7a88c2bef1bb254525c4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3lMHpL0rzsXXOY2IHhqOg5VcDx24C3DLuMJD5b9+wI2250TppCPH3G/7IPTmh1fJDSzqsNPEZvx1mnCy2rVhDw==