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
- 6b0c6c455aeba27c19f8771f5929a84a8c1749a3d358e5540913fb26bd4b0626
- request
- d8e79d7fe38c4df292f1d1f818ff4a98874a9c29648fa907d951d79c065d0516
- transaction
- a5fc59befc1d4edd475de12840c8de894b3398836155347d2291d3cb74ae36a4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 521
the chainentry 521
- sealed to the entry before
- 5f696cdd77ddbfef000096cfdb2d3a4292c7c687f6fb8a32a994f1ec8953f6ba
- this leaf
- 9e40376f75d6689abcfee1407c08a296abb49403cd7f3461b1b8990049839e3a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- jUC7OJSuM2+KQHNUUu/ZU/kwEO2RwLyj7Y+N6siXDpH0X3xdT05YBCFN8NINDwhqYy/LQlJ91nJEAWMXdCzbDw==