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
- bef00ed3783d04dc86fd2fe7114077e50238fb8705378e0b66baa7a9d62a86e7
- request
- 1c3e500e74777d7ab62414e62052b6337f48bac528da71fb6683176493fb2746
- transaction
- 0c23b6f951a7365d718f65d204aadd57a483410b63b2c2183ce8d1f07773ecddcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40701
the chainentry 40701
- sealed to the entry before
- 58614d14b87bbe65221fead2bfae9559229d7a234eaea140e0ae783d274ff78b
- this leaf
- 5f8d493707d5ddc58c982e7deb74fd45805bd2ee2f854aafaaa91fa178fafaa8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- bgKYXoROE1DQsysvzzRNZq8jDWA2GP/u50hgNKpnr38gvhFYrK7950Xgoy0Z0XYGrLVEVLpVslHvIMsdaS53AQ==