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
- 719168dae4eb9c85733e10598e8f33197e0273cf91f18debd513e7c99b45d568
- request
- 2a337d7ebc506b4f7a0187075d9b9e3c2afa4db379a8cf73d331bb205cbb5a18
- transaction
- 5e2233a01c742b42206ddc39f5a83acd1b52ff8899ddb98fa50d656467f7f1a1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30059
the chainentry 30059
- sealed to the entry before
- 6b627936285d2256c4f732d797fcd25456be38ed7ce15341a2ce5e2208a655a1
- this leaf
- 871bfc0055b06920a57cc6a26827637f825b4f032231bf808b3a0e842cd3787f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /OjMNNElEoO4RbQADL5wuXiqs3APv+lZKHvnd/BpDEC+TyZ06OgsDbcYbsm78408QuveQzyUYg3TUDAJoDm+Bw==