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
- 6da54fd9f80d61c010d08fa76e345522cd872070ebc5325e4c819e6ff03d2839
- request
- 796710955874d3c27e20f188e86608aabddbb0ad2fb2ad214e172823873a362a
- transaction
- 2a816ce2138cd2fa3f949681e37aaeab24aec0731a6af0adbd70c73c1d330012computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30963
the chainentry 30963
- sealed to the entry before
- e20656775dae79acd29cdecb0b2b9ec7c43f34e61458123e270604be3fd9bacb
- this leaf
- ab30e615b679bcb029bea7ca1522eb3d602247239cbe1678ee684860e82ea886
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- AgpymyX0L7VIMUnY0RfDrvUEyPB2v8KmGWLUJ2ll+u30/2A8m8rG5U3jfOWQYXhWy3Y5SNbOhN/qRIbi0i1yDg==