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
- ca72e03a873c95809babd9ca68b1cc437118ef2e8ab7b57872ba0d75ddbe101b
- request
- d611d21c314b0c34d705b7b165db16f9b9e0c11165550aba874796780231687b
- transaction
- cd485b63987ee48049b565a819f679093606e91c71021db703e16a9cbb06a34bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65064
the chainentry 65064
- sealed to the entry before
- 84bb83478f2815ac83f01000f1dec4e15de6a90908cced748b3616c8cd37a3dc
- this leaf
- 62d762d03e4c0d6cf81da3b7de98afbda3dd36b340db0653037fd78cd3e557c1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- pBSj9dEPihln83B7RC9qayPghUExJVYO6gN0UAVjnDdWx4dkEUQgd4hlq5t49OSFfSwY/+8g1dihouipVOktDQ==