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
- 19b4b2faecd8366fa54b596ec41eafaded7ef6277777cb53b0dc6f8db18b54ce
- request
- c4a1bb67eb36dc9bc4f30ec8a6ac481b0287bf8f68b2ba7c642c0bd935c898b5
- transaction
- 8bf32a2989abdcf3d76e5522d649fb486b5e97bba52c672108cf14e8b2858b36computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40745
the chainentry 40745
- sealed to the entry before
- 377b3cf507c6597b7d1974d67503bd1d6bdca8f4ccbe5932cb6311610ac4496c
- this leaf
- 0a6e29fe83958d259ebaf4290c2f016e11adc9853d7d222dbb03c453af4ce534
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- rnz/4vVRHxvf/L0/t5mrN/P8RlrB4BVUl+GgktafDOFbTas6NhcNB+lOmlU+gwv9Rf4Ljt2knEJLn+A0geYCDA==