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
- 6fc5e8bcd0b3fea3b9d20d41a6736013c97349d4136add5e4bc8fb65a1feb25a
- request
- 263bf48410048f8dd26e3e7515302029e5dcbdbce793b2846c15465938a2a9be
- transaction
- b602b88e7b9dd00d2733816a1357ff4f2b19782e10db39305fa5575b3ba2be68computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 23743
the chainentry 23743
- sealed to the entry before
- cfe428700ba55c7279499c2a2ead01e6ed983cddf14f89ff8efa4937d1f43e9d
- this leaf
- 40aef3e9fa924d380b52f2c7267226e3fd048c6bf600db9e0b68bd5f3c9a99ab
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JlRFkKkG9WXOVMSNAY0pdI/NeftmkD6gNacWA+6u4dkccVZXIK6wzabuYb/i/emvqAvnioxoMLaZX7cQs0DIBw==