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
- a4059be298e2b36bee02cdc065ee103ab52ddfeb2034a5fd6e13b0b7efee1571
- request
- 5f676d369bd7b13b5ef221cdd60ad3902bee5d55fda5a3d50a0fefc1a8927b01
- transaction
- c474f2c4ffd40aea3f903eb118c2ee5141fee07f3d062217c39429309ef35b5dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29328
the chainentry 29328
- sealed to the entry before
- 8e02454c5f13a18f2a374f5635bd0a6b1110df75075d06258e914fc3072b4c1f
- this leaf
- da286bc22c6b21e203315a73f4acaa2ebec387b8296e37a5341a1c08c4015551
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- umNb9fAUBWAD0DnfYoUqX6O3sSvMiIPX3flM9g9cguW868e+A6UeZ8WJykc0WbeMtfKyDPfOl8WcAq5izVkdBw==