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
- 691d54eedc348fd84d243a8c54d30a91037383bcccf868c61acbfa0de704689b
- request
- fe378929001a599b3962f5a24f74ac493da58f246ca69f746022a8e11fa644ee
- transaction
- fcc679255ca234888c72a61466b2042cc9d0f2265fe3cc3b429c2dad7aeb1b17computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2415
the chainentry 2415
- sealed to the entry before
- d096d533507f0ecde53fbc25dc8294a4e42ea84d9424b738688559c6784779c4
- this leaf
- 3bc6a40167293ef62dc11b9c2d83c3d828e9dec7ad884ff0425b00fe57d3c2e6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- E0KGb7AW+mUORYAj1MdgcmNqVz6R120c5BcrwGkvH7KIJep4YJVIGt5NhGUQ3rnzALeqwppV1OLWHearen5UDg==