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
- 624aa1cec66b5353320bc51db3bc9d944e01027a9e1ba5edb2356eafc3d350f7
- request
- 3a927989f4a66318a3a57964f395f88a51c2e7d17b1c51f04c91269ecf161be5
- transaction
- 72ddc15ac373f4ba5c13cac38baaf5f543dc6479a43a8e5071057ba8c221ff04computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 71187
the chainentry 71187
- sealed to the entry before
- ec4081fc39e70a7b647c923f798f9934b9f54b3f362181c67db22f853ad997b5
- this leaf
- c855d8fb3807f47f722c9805da520f28bac96be4b1767cf280168678292ac470
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Ry6QE7bIHEHUzpAWyuZFT1x0T64KxFSVVPkngZVD7yYuf48L3Y2vufMDE4Paerl9iP2jpgF3YjLecsOaPg0BDQ==